- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Aug 2022 18:42:55 +0000
- To: public-css-archive@w3.org
Florian's comment was not that we shouldn't do this, but that an attribute alone will cause compatibility issues - which is true. Any browser that doesn't understand the new `layer` attribute (on a `link` or a `style` element) will load those styles un-layered. That's an issue we need to address. And it's true that it is _more of a problem_ for `link` (which doesn't have a manual alternative), and that it would be ideal to solve for both `link` and `style`. This is something that we are actively working on for both `link` and `style` elements in the WHATWG proposal linked above. At this point it has to be solved in HTML, not in CSS. I don't think anyone still needs convincing that this is something we should do, the questions remaining are all about _how exactly_ we do it -- and those conversations are happening in the WHATWG. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5853#issuecomment-1218369375 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 August 2022 18:42:57 UTC