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
{{ message }}
This repository has been archived by the owner on Jun 30, 2023. It is now read-only.
As such, UA can automatically translate existing prefetch keyword to above policy. Given that this is pure syntax sugar, I don't think this is a high value feature. Closing for now, we can revisit in the future if there is high demand.
Isn't <a rel="next prefetch" href="page-2.html">Next page</a> much easier to write manually or implement in CMS than a separate link element? Or people may forget to delete <link rel="dns-prefetch" href="..."> after they removed related a element (which may be hundreds of lines away)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
(Moved from igrigorik/resource-hints#10)
Consider whether it makes sense to expose this for RH, on which elements, and what the motivating use cases are.
[1] http://www.w3.org/TR/html5/links.html#link-type-prefetch
The text was updated successfully, but these errors were encountered: