We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Priority Hints introduces the importance attribute, providing developers with the control to indicate a resource's relative importance to the browser.
importance
Google developers blog intro: https://developers.google.com/web/updates/2018/08/web-performance-made-easy#experimental_priority_hints
Chrome status: https://www.chromestatus.com/feature/5273474901737472
The text was updated successfully, but these errors were encountered:
I will vouch for this one also. I was looking for it as well. https://developers.google.com/web/updates/2019/02/priority-hints
Sorry, something went wrong.
Web.dev page about it: https://web.dev/priority-hints/
Via #6214 (comment)
importance was renamed to fetchpriority as part of the standards process.
fetchpriority
I think every part is covered via MDN by now:
fetchpriority (#6213 (comment)) => https://caniuse.com/?search=fetchpriority
"the priority attribute on the RequestInfo of fetch" => https://caniuse.com/mdn-api_request_priority
The data specifically refers that: https://github.com/mdn/browser-compat-data/blob/49d96ed28c8ab1184be01328c3d7c596b1ef365a/api/Request.json#L1107-L1109
Not saying this isn't useful as a combined feature on caniuse, just for the record.
Successfully merging a pull request may close this issue.
Priority Hints introduces the
importance
attribute, providing developers with the control to indicate a resource's relative importance to the browser.https://wicg.github.io/priority-hints/
https://github.com/WICG/priority-hints/blob/master/EXPLAINER.md
https://github.com/WICG/priority-hints/blob/master/EXAMPLES.md
Google developers blog intro:
https://developers.google.com/web/updates/2018/08/web-performance-made-easy#experimental_priority_hints
Chrome status:
https://www.chromestatus.com/feature/5273474901737472
The text was updated successfully, but these errors were encountered: