This seems genuinely useful, thanks for working on it.

What's the current thinking on exposing `priority` on Request, i.e. https://github.com/WICG/priority-hints/issues/11#issuecomment-396610469?

On 3/3/22 4:54 PM, Addy Osmani wrote:
> Priority Hints introduces a developer-set "fetchpriority" HTML attribute and "priority" fetch property allowing developers to influence the computed priority of a resource fetch. Supported priority values are auto, low, and high. Non-owner LGTM. Thanks once again for all of your work taking this feature through a reboot, Pat! The adjustment in attribute name adds some needed clarity to the expected behavior for web developers. I would be excited to see this feature ship.

On Thursday, March 3, 2022 at 10:20:40 AM UTC-8 Patrick Meenan wrote:


            Contact emails

    [email protected], [email protected]
    <mailto:[email protected]>, [email protected]
    <mailto:[email protected]>


            Explainer

    https://github.com/WICG/priority-hints/blob/main/EXPLAINER.md
    <https://github.com/WICG/priority-hints/blob/main/EXPLAINER.md>


            Specification

    https://wicg.github.io/priority-hints/
    <https://wicg.github.io/priority-hints/>


            Summary

    Priority Hints provide developers a way to indicate a resource's
    relative fetch priority 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 "fetchpriority" HTML attribute and "priority" fetch
    property allowing developers to influence the computed priority of
    a resource fetch. Supported priority values are auto, low, and high.


    By far, the biggest win during Origin Trials was for sites to be
    able to tag important images as high-priority so they could be
    fetched earlier without having to wait for layout (leading to
    substantial improvements in LCP). Details are in the linked OT
    feedback summary.

    The only change during the spec process was a name change of the
    HTML/fetch attributes from "importance" to "fetchpriority" and
    "priority".

    Web-dev article: https://web.dev/priority-hints/
    <https://web.dev/priority-hints/>


            Blink component

    Blink>Loader
    
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELoader>


            Search tags

    priority-hints
    <https://chromestatus.com/features#tags:priority-hints>, priority
    hints <https://chromestatus.com/features#tags:priority%20hints>


            TAG review

    https://github.com/w3ctag/des ign-reviews/issues/704
    <https://github.com/w3ctag/design-reviews/issues/704>


            TAG review status

    Issues addressed


            Link to origin trial feedback summary

    
https://docs.google.com/document/d/162dym7j0PbpoMvle58gO9DDqpQFOvvmqwu1OIJ1IEzQ/edit?usp=sharing
    
<https://docs.google.com/document/d/162dym7j0PbpoMvle58gO9DDqpQFOvvmqwu1OIJ1IEzQ/edit?usp=sharing>


            Risks


            Interoperability and Compatibility


    Gecko: worth prototyping
    <https://mozilla.github.io/standards-positions/#priority-hints>
    WebKit: No signal
    <https://www.mail-archive.com/[email protected]/msg30357.html>
    Web developers: Strongly positive
    
<https://docs.google.com/document/d/162dym7j0PbpoMvle58gO9DDqpQFOvvmqwu1OIJ1IEzQ/edit?usp=sharing>
    Other signals:


            Debuggability

    Resource fetch priority is exposed in dev tools as part of the
    network panel, in the netlog, in traces and in tools like
    WebPageTest.


            Is this feature fully tested by web-platform-tests
            
<https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>?

    Yes


            Flag name

    Experimental Runtime Feature Flag: PriorityHints
    Origin Trial: PriorityHintsAPI


            Requires code in //chrome?

    False


            Tracking bug

    https://crbug.com/821464


            Estimated milestones

    OriginTrial desktop last    99
    OriginTrial desktop first   96

    OriginTrial android last    99
    OriginTrial android first   96


            Link to entry on the Chrome Platform Status

    https://chromestatus.com/feature/5273474901737472
    <https://chromestatus.com/feature/5273474901737472>


            Links to previous Intent discussions

    Intent to Experiment:
    https://groups.google.com/a/chromium.org/g/blink-dev/c/CkRq2zY-t6c
    <https://groups.google.com/a/chromium.org/g/blink-dev/c/CkRq2zY-t6c>

    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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5817987a-0812-4c5c-b8cb-dce4dbbdd830n%40chromium.org <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5817987a-0812-4c5c-b8cb-dce4dbbdd830n%40chromium.org?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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cc288340-b04b-3e28-2e50-b178351adcd3%40chromium.org.

Reply via email to