- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Sep 2021 20:26:03 +0000
- To: public-css-archive@w3.org
The need for a `selector()` function at all stands out to me as an issue — even if it had the ability to select multiple elements. We already have a syntax for attaching properties to selectors (it's the core of the language), so why not use it here? Both scroll-containers and scrolled elements can be selected already, and could establish their timelines in the cascade, using normal CSS syntax. (This is the same reason I pushed against container-queries using a selector syntax, even one without the ID limitation). -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6674#issuecomment-926899822 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 September 2021 20:26:05 UTC