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: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
Date: Wed, 26 Aug 2020 15:53:09 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-680966562-1598457188-sysbot+gh@w3.org>
> the name of the layer depends on its import method, right? Therefore it determines the order of application of style rules due to the ordering of the layers.

The method of import can be used to add (and optionally name) a grouping layer around the file contents, if that's what you mean. 

It sounds like you see that as a downside? I see that as a way to give the _entrypoint file_ final control over how all layers will be used, which will help authors avoid global naming conflicts. This way a third-party tool is able to hide or expose whatever layers they want, and the consuming document can decide to either interact with those individual layers, or encapsulate them inside a namespace to avoid conflicts.

In either case, with or without an layer-import syntax, the importing document would be able to re-order any exposed layers inside the imported file. By providing an explicit syntax, authors have more control over _how_ that interaction should or should not happen.

GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4470#issuecomment-680966562 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 15:53:11 UTC

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