- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Oct 2022 14:50:25 +0000
- To: public-css-archive@w3.org
> So essentially the diff is that we'd move rule.cssRules (in the current spec draft) to rule.style.cssRules? It's a bit tricky for us, but it's possible. Yeah. > Does this mean that getComputedStyle() also gets a cssRules? That's perhaps a bit odd. Not necessarily. If we want to keep the object types exactly as current, then sure, they'd have a (null) .cssRules, but possibly we could use subclasses to separate this. > I would be interested to get links to the discussions considering the opposite: moving the CSSStyleDeclaration interface into CSS*Rule (and leave .style as legacy). There are none, as no one has ever suggested doing this. ^_^ -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7850#issuecomment-1292170550 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 October 2022 14:50:27 UTC