- From: SHAYDED via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Nov 2023 22:14:27 +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`. Is this _really_ such a problem though? The only people would would run into this problem, are the ones who choose to use the feature. In my case we only need to support chrome, so at least for us this is a non-issue, but I suspect that it wouldn't be an issue for many other people who would only benefit from having the feature available even with the gotcha. It would ease a lot of pain for us dealing with third party CSS in an environment where we have limited control. I understand it is a problem that does need to be solved, but I don't see a reason it should completely hold up this feature. Please let me know if there's something I'm missing and thank you for the work y'all do. I know there's a lot of complex politics involved and whatnot. -- GitHub Notification of comment by shayded-exe Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5853#issuecomment-1793163703 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 November 2023 22:14:29 UTC