Skips the PreloadScan step of the browser to explore performance tradeoffs for pages with no sub-resource fetches. PreloadScan step of Chromium is implemented as a blocking step that benefits performance of pages with sub-resource fetches, via implementation of the speculative prefetch. However, for pages that don’t benefit from this step, i.e., for pages with no sub-resources, this is additional processing overhead with little benefit. For advanced web users who would like to benefit by reducing this overhead, this experiment provides a page-level control to disable the PreloadScanner. Data collected from this experiment could evaluate if a modified API or a different implementation of HTMLPreloadScanner would be helpful.
None
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
None
No, since in this iteration we don’t have a web exposed API, and the valid OriginTrial token itself is currently used to trigger the feature. We plan to fully test the API via web-platform-tests once they are proposed.
No milestones specified
Hi Alex,
What milestones are you requesting for the Origin Trial?
thanks,
Mike
--
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.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC6ceCFrGCOFXgV9OuevjgA%2BZgXa-dE%2Bdd8f%2BZ8QC2w-ecAxCw%40mail.gmail.com.
> What milestones are you requesting for the Origin Trial?
On 3/21/24 7:24 PM, Alex N. Jose wrote:
M125 to M131> What milestones are you requesting for the Origin Trial?
Could you also please request review for Privacy, Security, and
Debuggability in your chromestatus entry?