A visit beginning, as an enter sees it: the frame's own bookkeeping — its
identity, which visit of the frame it is and when it started — passed in and
never kept by the screen. The first visit is index 1. id names the
frame's whole life — one opened screen — so what a visit's events share
across the visits of the same frame (a recording repeats one profile session
id across the seven visits of one opened profile) has one identity; a value
the whole process shares, such as the profile telemetry's ranking token, is
process state, never the visit's.
It carries no chain: the visit's own navigation is emitted inside the burst,
so the chain the visit is shown with is final only once the burst ended. A
screen that logs where it is shown reads the chain in front at the point it
logs (NavigationWire), not a snapshot taken before its burst.
Which visit of the frame it is: 1 on the first show, one more on every
resume. The engine's bookkeeping and the tests read it; no preset and no
recording field renders it.
A visit beginning, as an
entersees it: the frame's own bookkeeping — its identity, which visit of the frame it is and when it started — passed in and never kept by the screen. The first visit isindex1.idnames the frame's whole life — one opened screen — so what a visit's events share across the visits of the same frame (a recording repeats one profile session id across the seven visits of one opened profile) has one identity; a value the whole process shares, such as the profile telemetry's ranking token, is process state, never the visit's.It carries no chain: the visit's own navigation is emitted inside the burst, so the chain the visit is shown with is final only once the burst ended. A screen that logs where it is shown reads the chain in front at the point it logs (
NavigationWire), not a snapshot taken before its burst.