Skip to content
This repository has been archived by the owner on May 5, 2022. It is now read-only.

Add a note regarding media attribute mismatch #117

Merged
merged 1 commit into from Jan 9, 2018

Conversation

yoavweiss
Copy link
Contributor

@yoavweiss yoavweiss commented Jan 9, 2018

At https://bugs.chromium.org/p/chromium/issues/detail?id=792038, the conclusion was that a note regarding the behavior in case media doesn't match the environment is required.
This adds such a note.


Preview | Diff

@igrigorik
Copy link
Member

This is a bit odd to me, as there is nothing preload specific here and this is precisely how media is specced and intended to be used. That said, OK, I guess.

@yoavweiss
Copy link
Contributor Author

I don't disagree, but people did get confused by this, and adding notes is easy :) I believe the reason for confusion is that for rel=stylesheet, links do fetch resources, even if in lower priority.

@yoavweiss yoavweiss merged commit 09af38e into w3c:gh-pages Jan 9, 2018
@yoavweiss yoavweiss deleted the media_note branch January 9, 2018 19:45
@scottjehl
Copy link

Agreed, @yoavweiss. It'd be interesting if link[rel=stylesheet] didn't fetch until its media matches, but I don't know of any browsers that do that. Thanks!

@yoavweiss
Copy link
Contributor Author

Agreed, @yoavweiss. It'd be interesting if link[rel=stylesheet] didn't fetch until its media matches, but I don't know of any browsers that do that. Thanks!

I believe that's not web-compatible, as too many sites break as a result (at least that was the case last time it was tried, by Opera IIRC).

Maybe @zcorpan would know more of the history there.

@zcorpan
Copy link
Member

zcorpan commented Jan 10, 2018

Probably there were sites accessing the cssom or so, don't recall exactly

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants