Contact emails
g...@google.comExplainer
https://github.com/explainers-by-googlers/prefetch-activation-beaconSpecification
https://github.com/explainers-by-googlers/prefetch-activation-beaconSummary
The on-prefetch-activation HTTP response header enables servers to specify a telemetry endpoint that the browser notifies when a prefetched resource is used for navigation. Developers gain a reliable signal to measure the precision and performance impact of their prefetch strategies.Blink component
Blink>Loader>PreloadWeb Feature ID
Missing featureTAG review
No information providedTAG review status
PendingGoals for experimentation
We are going to start origin trial for the prefetch activation beacon to evaluate whether it can reliably report all the user navigation when the page is prefetched. We will compare the DAU and the query count with a group not using the API and reports activation via javascript.Origin Trial documentation link
https://github.com/explainers-by-googlers/prefetch-activation-beaconRisks
Interoperability and Compatibility
No information providedGecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
NoOngoing technical constraints
NoneDebuggability
Basic support, the activation beacon request will be shown in the devtools network panel.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
YesYesFlag name on about://flags
prefetch-activation-beacon