Priority Hints provide developers a way to indicate a resource's relative importance to the browser, allowing more control over the order resources are loaded. Many factors influence a resource's priority in browsers. These include type, visibility, and preload status of a resource. Priority Hints introduces a developer-set "importance" attribute allowing developers to influence the computed priority of a resource. Supported importance values are auto, low, and high.
The goal is to re-start the origin trial experiment for Priority Hints with a focus on some specific use cases that have generated significant developer interest:
The previous experiment was run before the recent focus on core web vitals and LCP in particular and did not generate as much developer interest as there is now. There were also prioritization issues with preload that are fixed in 95 that made it difficult to experiment with for the script case. There is pretty significant demand from developers for the knobs that Priority Hints provide, particularly for improving LCP.
None
OriginTrial desktop last | 101 |
OriginTrial desktop first | 96 |
OriginTrial android last | 101 |
OriginTrial android first | 96 |
Ongoing technical constraints
None
Debuggability
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
YesIs this feature fully tested by web-platform-tests?
NoFlag name
PriorityHintsRequires code in //chrome?
FalseTracking bug
https://crbug.com/821464Estimated milestones
OriginTrial desktop last 101 OriginTrial desktop first 96 OriginTrial android last 101 OriginTrial android first 96
Link to entry on the Chrome Platform Status
https://www.chromestatus.com/feature/5273474901737472Links to previous Intent discussions
Intent to Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/jpeSdM897Xw/m/CY6tothSDgAJThis intent message was generated by Chrome Platform Status.
--
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/CAPq58w4GGUARoL%3DKrhCPDG43xWQMk3FuUK-_-zHxM_Tr1tXGKQ%40mail.gmail.com.
Thanks. I emailed experimentation-dev just to be sure because the underlying feature didn't change and I want to avoid confusion about multiple different trials for the same feature name.
On Mon, Sep 13, 2021 at 3:56 PM Patrick Meenan <pme...@chromium.org> wrote:Thanks. I emailed experimentation-dev just to be sure because the underlying feature didn't change and I want to avoid confusion about multiple different trials for the same feature name.To clarify, I didn't mean this needs a new experiment name. I just meant that from an API owners' perspective, the previous experiment should not impact the timeframes of this one, as there's been a 2 years break in between them. Apologies for not being clearer.The main thing that is changing is that the dev ecosystem now has pretty heavy interest in using it to improve LCP so gathering feedback will be a lot easier than the last go-around which was focused on async scripts (which already had a hack people were using).On Mon, Sep 13, 2021 at 9:42 AM Yoav Weiss <yoav...@chromium.org> wrote:Thanks for working on this!!On an administrative note, this should be considered a new OT, as the previous one was run a while ago.On Fri, Sep 10, 2021 at 5:16 PM Patrick Meenan <pme...@chromium.org> wrote:Contact emails
ad...@chromium.org, domfa...@gmail.com, kenji...@chromium.org, pme...@chromium.orgExplainer
https://github.com/WICG/priority-hints/blob/main/EXPLAINER.mdSpecification
https://wicg.github.io/priority-hints/Summary
Priority Hints provide developers a way to indicate a resource's relative importance to the browser, allowing more control over the order resources are loaded. Many factors influence a resource's priority in browsers. These include type, visibility, and preload status of a resource. Priority Hints introduces a developer-set "importance" attribute allowing developers to influence the computed priority of a resource. Supported importance values are auto, low, and high.
Blink component
Blink>LoaderSearch tags
priority-hints, priority hintsTAG review
TAG review status
Pending
Risks
Interoperability and Compatibility
Gecko: No signal
WebKit: No signal
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfWFHaam-cqdNUct-7VYJ5qWXxyJJ1Ax7e3SP5ND3StWQA%40mail.gmail.com.