- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Oct 2021 20:54:52 +0000
- To: public-css-archive@w3.org
FWIW now that I saw an example of this in practice, I am under the impression that this reversal of order doesn't serve the use cases that layers were supposed to serve. The main use case I can see for layers are resets, frameworks, and framework themes. Having these styles above the site's styles just doesn't work. See the example at the start of this thread, it just doesn't make any sense to me: https://twitter.com/fremycompany/status/1445126893037031425?s=21 I think it would be worth having a redo of this conversation in the light of this example to confirm this is still a decision the group is confortable about. In my opinion, if you start using layers, the only type of polyfill that will work to support older browsers will be to just wrap every rule in :where() to nuke its priority and rewrite the files so that rule order match the priority order after layers have been taken into consideration. I don't think one can simply decide some styles just don't get received by a supported browser, whether that style is a reset or a specific style shouldn't matter much, it is necessary all the same. So the reasoning at the start of the thread doesn't speak to me. But this is just my opinion of course, I just want to make sure this gets a review before implementations ship. -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6284#issuecomment-933847302 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 October 2021 20:54:54 UTC