- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jul 2023 16:13:28 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-nesting] Why does CSSStyleRule not inherit from CSSGroupingRule?`, and agreed to the following: * `RESOLVED: Change CSSStyleRule to inherit from CSSGroupingRule, modulo any discovered compat impact` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> emilio: Nesting spec extends CSSSTyleRule by copypasting CSSGroupingRule API<br> <TabAtkins> emilio: Think there was a point in the past we discussed enhancing CSSSTyleRule but discarded that<br> <TabAtkins> emilio: So maybe instead we could have CSSStyleRule inherit from CSSGroupingRule? Then enhancements from either come to both.<br> <TabAtkins> emilio: Would make it more likely that changes (like using observablearray) would apply to both<br> <TabAtkins> emilio: This is all assuming there's no compat impact.<br> <TabAtkins> emilio: Assuming that, I think this is the right thing to do.<br> <TabAtkins> No objections from me, modulo possible compat impact we'll find.<br> <TabAtkins> (it would be *relatively* hard to have a compat impact here, I imagine)<br> <TabAtkins> astearns: Objections?<br> <TabAtkins> RESOLVED: Change CSSStyleRule to inherit from CSSGroupingRule, modulo any discovered compat impact<br> <TabAtkins> emilio: I'd also expect compat to be rare<br> <TabAtkins> emilio: Few people use instanceof, they use duck-typing<br> <TabAtkins> emilio: And we shipped .cssRules on CSSStyleRule without issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8940#issuecomment-1632829763 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 July 2023 16:13:30 UTC