You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to dev-pl...@mozilla.org
As of Sep 24th 2024 we intend to turn fetch priority on by default. It
has been developed behind the network.fetchpriority.enabled preference.
Status in other browsers is shipped in Chrome and Safari.
It does not seem this feature (or its old name "priority hints") was
previously discussed in an "Intent to prototype" thread, so I'm
providing relevant information below.
The fetch priority attribute enables web developers to optimize resource
loading by specifying the relative priority of resources to be fetched
by the browser. It can be specified on script, link, img elements, on
the RequestInit parameter of the fetch() method and Link in HTTP
response headers. You can find further details at
https://web.dev/articles/fetch-priority ; note however that the details
of how fetchpriority affects internal browsers' priority or other
priority hints defined in HTTP is implementation-specific.
https://phabricator.services.mozilla.com/D222655 will add documentation
for Mozilla's own behavior.
Other browsers:
- Blink: Shipped since Chrome 102.
- WebKit: Shiped since Safari 17.2.
web-platform-tests:
There are a few IDL tests for the fetchpriority attribute:
- fetch/api/request/request-init-priority.any.js
- html/dom/idlharness.https.html
- html/embedded-content/the-img-element/attr-img-fetchpriority.html
- html/scripting/the-script-element/attr-script-fetchpriority.html
- html/semantics/the-link-element/attr-link-fetchpriority.html