- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Jan 2022 18:39:07 +0000
- To: public-css-archive@w3.org
> To answer those questions here's my counter-proposal: Using a selector() is a last-resort kind of thing, when there's no way to scope the element you're associating with. Requiring an ID is onerous, and still doesn't actually give you uniqueness; allowing more general selectors gives you the same non-uniqueness issues you're trying to avoid. Here, it's straightforward - you want a descendant of the scroll container. Having the target self-select is a pretty straightforward and normal way to handle this. When there's more than one element advertising itself as the target, you just take the first in tree order or something. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6986#issuecomment-1024503667 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 January 2022 18:39:08 UTC