W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2020

Re: [csswg-drafts] [css-cascade] Custom Cascade Layers (formerly "custom origins") (#4470)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 26 Aug 2020 16:13:28 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-680978418-1598458405-sysbot+gh@w3.org>
Yes, it's very important that the final page author have the ultimate control over how things are layered. A third-party library gives its layers a default ordering according to the order they appear in that library, but the page author can choose to reorder those (or rather, insert their own layers between the third-party's layers) if they have a need for that.

The importing syntax used is just about whether you wrap the entire third-party sheet in another layer or not; doing so lets you (a) put CSS that's not layer-aware into a layer, so it works better with the rest of the layer-aware page, and (b) easily put a whole stylesheet into a particular spot in the layer ordering, without having to carefully control the location it shows up in the document or care about what layer names the stylesheet might itself use.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4470#issuecomment-680978418 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 August 2020 16:13:29 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:13 UTC