- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Dec 2024 16:40:36 +0000
- To: public-css-archive@w3.org
> But it doesn't seem like a major inconvenience now to just write `::picker(select)` instead of `select::picker` But this is a deviation from what we currently write. For example, it’s `p::before` and not `::before(p)`. > Eventually when we support all pickers, you'd be able to write `select::picker` too. Is there a reason why we can’t do that now? I understand that `::picker` itself would target all pickers which could work against authors in the future because they target too many pickers. However, part of the guidelines that DevRel can give here – and which could also be a note in the spec – is to warn authors to always prepend the targeted element before `::picker`, e.g. `select::picker`. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11394#issuecomment-2555004556 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 December 2024 16:40:37 UTC