- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Apr 2024 22:17:21 +0000
- To: public-css-archive@w3.org
@LeaVerou Yeah, that's what I meant by "(But this could potentially be an opt-in behavior.)" > Actually, we could just ship the no-op version first, and expand it with keywords later. Exactly. > If we define this as a CSSRule, can we change to CSSGroupingRule later? Yes, that's exactly what we did to CSSStyleRule, and that's vastly more used. This is especially true if we start off with the no-op version; once we make it more useful, it's more likely authors might expect to be able to nest rules in it, like they can with style rules, and then we run the risk of accidentally activating invalid code. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10234#issuecomment-2080184919 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 26 April 2024 22:17:22 UTC