Contact emailsad...@chromium.org, kenjibah...@chromium.org, pmee...@chromium.org
Explainerhttps://github.com/WICG/priority-hints/blob/main/EXPLAINER.md Specificationhttps://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/ Blink componentBlink>Loader <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELoader> Search tagspriority-hints <https://chromestatus.com/features#tags:priority-hints>, priority hints <https://chromestatus.com/features#tags:priority%20hints> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/704 TAG review statusIssues addressed Link to origin trial feedback summary 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/webkit-dev@lists.webkit.org/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 bughttps://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 Links to previous Intent discussionsIntent to Experiment: 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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPq58w7BJPCtS0d1Xp6_asU1C4sNo-uZT3a_JYqfJTZm%3DrRqwQ%40mail.gmail.com.
