> What milestones are you requesting for the Origin Trial?
M125 to M131

On Thu, Mar 21, 2024 at 2:44 PM Mike Taylor <miketa...@chromium.org> wrote:

> Hi Alex,
>
> What milestones are you requesting for the Origin Trial?
>
> thanks,
> Mike
> On 3/21/24 3:18 PM, Alex N. Jose wrote:
>
> Contact emails ale...@chromium.org
>
> Explainer
> https://docs.google.com/document/d/1wiaTL5TeONTZamycMVMjo76nMcbhHNYznQy7I_zCVRY/edit?usp=sharing
>
> Specification None
>
> Summary
>
> 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.
>
>
> Blink component Blink>Loader
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELoader>
>
> TAG review None
>
> TAG review status Pending
>
> Risks
>
>
> Interoperability and Compatibility
>
> None
>
>
> *Gecko*: 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?
>
> None
>
>
> Goals for experimentation
>
> Ongoing technical constraints
>
> None
>
>
> Debuggability
>
> None
>
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, ChromeOS, Android, and Android WebView)? No
>
> Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
> ? No
>
> 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.
>
>
> Flag name on chrome://flags None
>
> Finch feature name None
>
> Non-finch justification None
>
> Requires code in //chrome? False
>
> Estimated milestones
>
> No milestones specified
>
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5190976638550016
>
> This intent message was generated by Chrome Platform Status
> <https://chromestatus.com/>.
> --
> 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+unsubscr...@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
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC6ceCFrGCOFXgV9OuevjgA%2BZgXa-dE%2Bdd8f%2BZ8QC2w-ecAxCw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC6ceCETtJBfzZROvHo23KqJTrMKtmb6rA6duOpiDTKSussz8A%40mail.gmail.com.

Reply via email to