*Contact emails* [email protected] *Explainer* https://github.com/explainers-by-googlers/prefetch-activation-beacon
*Specification* *No information provided* *Summary* 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>Preload <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ELoader%3EPreload%22> *Web Feature ID* Missing feature *Motivation* The API is proposed for a reliable measurement of whether a prefetch page is activated. This allows precise visit statistics for the prefetched page without cache interference. *Initial public proposal* https://github.com/WICG/proposals/issues/284 *Goals for experimentation* None *Requires code in //chrome?* False *Tracking bug* https://b.corp.google.com/issues/499814382 *Launch bug* https://launch.corp.google.com/launch/4468679 *Estimated milestones* M150 *Link to entry on the Chrome Platform Status* https://chromestatus.com/feature/5118934710878208?gate=5175566203486208 -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJQw1NzrnJBU7pmpz7bfxK2G7cWUcJsaU9ekFHh3XKFUyzzrwg%40mail.gmail.com.
