- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Dec 2024 16:48:03 +0000
- To: public-css-archive@w3.org
> 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`.
The main reason is to avoid compat hazard. If someone writes
```
::picker {
...
}
```
Right now it would only apply to select, but as support for more pickers are added (datepicker etc.), that rule would start applying to more things (potentially against the will of the author, or not as they expect).
Having a mandatory argument during the transitional period, allows pickers to be incrementally rolled out control by control without compat problems.
--
GitHub Notification of comment by nt1m
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11394#issuecomment-2555044130 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:48:04 UTC