- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jul 2022 23:04:14 +0000
- To: public-css-archive@w3.org
Late regrets that I couldn't make it to the call! > emailio pointed out it's tricky on `@container` rules since they rely on the element being matched as well Unfortunately, my answer to that wasn't discussed on the call. And I think it would really be best if we added this to the `CSSConditionRule` superclass instead. So _all_ classes deriving from it have it available. As [mentioned in my previous comment](https://github.com/w3c/csswg-drafts/issues/4240#issuecomment-1149552733), with the changes to `CSSContainerRule` discussed in #7033 the related element is determined by the other properties of that interface. So `.matches` could be exposed as a simple getter there as well. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4240#issuecomment-1197469510 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 July 2022 23:04:16 UTC