- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Oct 2021 17:25:56 +0000
- To: public-css-archive@w3.org
Ah, if we're doing readonly, then my objections to arrays mostly go away. Having *mutable* arrays requires a lot more logic that isn't really justified here. So we can just do a `readonly FrozenArray<CSSOMString>` for the type on the CSSLayerStatementRule and be good.
I still suspect having the layer names themselves be a single string with the possibly-dot-separated name in it is best here; most of the time you want to treat the name as a unit anyway, and when you *do* want to break it down, a simple `name.split(".")` is reliably correct unless someone put an escaped period in their layer name like `foo\.bar` (which, uh, stop hitting yourself).
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6576#issuecomment-944471452 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 October 2021 17:25:57 UTC