You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's an important property for our site. The default priority for fonts is highest, but we use font-display: optional; for the custom fonts, so we don't need/want the font files getting downloaded before JS and other more important assets. So we use fetchpriority: low
At a minimum, I think the documentation should be updated to detail the constraints/choices. Ideally, it would support all the valid aspects from the spec.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If a
links
function usesfetchpriority: 'low'
, it doesn't show up in theLink
header when usingpreloadRouteAssets
.i.e. it returns
and not
However,
fetchpriority
is a supported attribute in the Link header; See this example for a stylesheet from the MDN docsLink: </style.css>; rel=preload; as=style; fetchpriority="high"
It's an important property for our site. The default priority for fonts is
highest
, but we usefont-display: optional;
for the custom fonts, so we don't need/want the font files getting downloaded before JS and other more important assets. So we usefetchpriority: low
Looking at the code, it appears it doesn't support pagination via
rel
either, likeLink: <https://api.example.com/issues?page=2>; rel="prev", <https://api.example.com/issues?page=4>; rel="next", <https://api.example.com/issues?page=10>; rel="last", <https://api.example.com/issues?page=1>; rel="first"
At a minimum, I think the documentation should be updated to detail the constraints/choices. Ideally, it would support all the valid aspects from the spec.
Beta Was this translation helpful? Give feedback.
All reactions