New issue
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
Uncertainty around support and validity of imagesrcset and imagesizes on link element #5604
Comments
Thanks for highlighting this. These are intended for use with Concretely, this would mean:
|
@domenic Thank you for the feedback. That sounds pretty neat. So, does that mean something like this would be valid:
Also, am I correct is saying that there is no browser support for this yet? |
Yep, I think that's the idea.
This has been supported in Chrome for about 15 months. |
I will give that a try 👍 |
Closes #5604. This also fixes nearby double-negatives for other link attributes.
Closes #5604. This also fixes nearby double-negatives for other link attributes.
Closes whatwg#5604. This also fixes nearby double-negatives for other link attributes.
From the HTML specification below, it seems that one can specify different images to be used based on viewport size or screen depth(using
imagesrcset
andimagesizes
) as is common with theimg
element.https://html.spec.whatwg.org/commit-snapshots/cb4f5ff75de5f4cbd7013c4abad02f21c77d4d1c/#the-link-element
As there is no example usage my assumption was that this is related to
rel=icon
i.e. specify different favicons for different viewports. Searching on caniuse there are currently no entries for eitherimagesrcet
orimagesizes
. The same goes for MDN Web Docs.I tried the following code but, no favicon is displayed for any viewport size:
Running the code through https://validator.nu/ produces an error related to the two attributes and the resulting error description seem to suggest that those attributes are not valid(are not defined for the
link
element).The text was updated successfully, but these errors were encountered: