Evaluate whether mapping `fetchpriority=auto` to internal priority of "normal" should be changed for early in-body scripts
Categories
(Core :: Networking, task, P2)
Tracking
()
People
(Reporter: mbrodesser, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
"Early in-body" scripts are scripts in <body> which occur before non-preloaded images. E.g.
<body>
<script fetchpriority=auto ...>
<img ...>
</body>
Chromium in that case maps fetchpriority=auto to an internal priority of "high". See https://web.dev/articles/fetch-priority#browser_priority_and_fetchpriority.
However, the effect of that mapping has to be considered together with all other priority assignments. Some of those mappings differ from Chromium's. E.g. Gecko "boosts" priorities of images, which differs from how Chromium changes priorities for images.
It seems reasonable to evaluate this specific mapping once there is basic support for the fetchpriority attribute for all elements which should support it (<script>, <link>, <img>`).
|
Reporter | |
Comment 1•1 year ago
|
||
The difference of the internal priorities for late- and early-in-body scripts is considered important for optimizing the LCP (https://developer.mozilla.org/en-US/docs/Glossary/Largest_contentful_paint).
|
||
Updated•1 year ago
|
Description
•