- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Jan 2025 09:00:24 +0000
- To: public-css-archive@w3.org
> Unfortunately we cannot rely on DevRel or specification guidance. I tend to disagree :) > Web developers will use all permutations of an API and rely on them. That I do agree on. > We have to design it in a way such that it cannot be misused. Can’t we go another route to enforce this? Something like defining a subclass of pseudo-elements that **must** be preceded by a selector that targets its originating element? This restriction can later on then be relaxed and would circumvent the intermediary frankenstein-esque `select::picker(select)` selector. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11394#issuecomment-2572620452 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 January 2025 09:00:25 UTC