W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2021

Re: [csswg-drafts] [css-cascade] Cascade layers need an import syntax (#5681)

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Sat, 09 Jan 2021 22:52:36 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-757379581-1610232755-sysbot+gh@w3.org>
Having reviewed the @layer syntax in the draft, I think I prefer that option to something built on @import. We have both a block syntax and an import syntax, which have different rules about where they're allowed to occur in the stylesheet. But there's also an empty layer declaration syntax `@layer name;` which if we use a different syntax for layer imports has to have its own special placement rules (so that it can be allowed before @import) rather than just being a degenerate form of the block and import versions. I also think having the indication of the import being a layered import up front, rather than at the end of the rule syntactically, is helpful.

However, whatever import syntax we use, it should have fully identical syntax and capabilities after the @keyword. @import for example accepts media queries and supports queries; @layer imports should match it exactly.

@una @import differs from @layer because it does not wrap its contents in a layer, merely pulls them into whatever is the base layer of the current style sheet, exactly as if those rules were copy-pasted into the style sheet in place of the @import rule.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 9 January 2021 22:52:38 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:38 UTC