Contact emails
pa...@chromium.org, dro...@chromium.org, matt...@chromium.org
Summary
Disable prerendering in chrome. This will not break any sites, but may cause a performance regression.
Motivation
Prerender is difficult to maintain and wastes resources compared to its performance benefit. More efficient ways to achieve the same performance goal are in development, but as they will behave quite differently from prerender we need to resolve any unknown external dependencies by deprecating prerender cleanly.
Compatibility and Interoperability Risk
As prerender is a best-effort performance feature only, there is no compatibility risk. The most performance sensitive use of prerender we know of (invoking prerender through the CCT mayLaunchURL API) will not be immediately deprecated.
Usage Information
Detailed usage statistic are available only through Google internal UMA counters. In summary, of the times link-rel prerender is triggered, under 15% are used. Approximately 0.2% of all navigations trigger prerender (these counts are from UMA users, a possibly-biased subset of all chrome users). Link-rel prerenders are the non-CCT externally facing prerender API.
Launch Tracking Bug
Requesting approval to remove too?
Yes, although as there is no API change there is no practical difference between deprecation and removing.do we have means to track potential performance regressions?On Fri, Jan 20, 2017 at 2:44 PM Matthew Cary <matt...@google.com> wrote:It will be ignored. We are concurrently starting up an experiment for the prefetching feature mentioned above that will be invoked instead on a <link rel=prerender>. This new feature will essentially perform an extended prefetch by running the preload scanner on the main resource; see the linked doc for all the details.
On Fri, Jan 20, 2017 at 2:41 PM, Jochen Eisinger <joc...@chromium.org> wrote:What will happen if a site includes a <link rel=prerender> or a corresponding header? Will we ignore that, or treat it as preload, or still prerender?On Fri, Jan 20, 2017 at 2:39 PM 'Matthew Cary' via blink-dev <blin...@chromium.org> wrote:Contact emails
pa...@chromium.org, dro...@chromium.org, matt...@chromium.org
Summary
Disable prerendering in chrome. This will not break any sites, but may cause a performance regression.
Motivation
Prerender is difficult to maintain and wastes resources compared to its performance benefit. More efficient ways to achieve the same performance goal are in development, but as they will behave quite differently from prerender we need to resolve any unknown external dependencies by deprecating prerender cleanly.
Compatibility and Interoperability Risk
As prerender is a best-effort performance feature only, there is no compatibility risk. The most performance sensitive use of prerender we know of (invoking prerender through the CCT mayLaunchURL API) will not be immediately deprecated.
Usage Information
Detailed usage statistic are available only through Google internal UMA counters. In summary, of the times link-rel prerender is triggered, under 15% are used. Approximately 0.2% of all navigations trigger prerender (these counts are from UMA users, a possibly-biased subset of all chrome users). Link-rel prerenders are the non-CCT externally facing prerender API.
Launch Tracking Bug
Requesting approval to remove too?
Yes, although as there is no API change there is no practical difference between deprecation and removing.
--
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 blink-dev+...@chromium.org.
Just to verify, <link rel=prerender> will stay supported, just ignored for now and later rerouted to the no-state prefetch backend?
Launch Tracking Bug
The issue seems to be Google only (or restricted to public access in some other way)
Requesting approval to remove too?
Yes, although as there is no API change there is no practical difference between deprecation and removing.
--
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 blink-dev+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
lgtm1
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
--
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 blink-dev+unsubscribe@chromium.org.
AMP viewer prerenders and the PrerenderingOffliner are excluded in this phase
Not a web platform feature? It's in the spec: https://www.w3.org/TR/resource-hints/#prerender