- From: Joey Arhar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jul 2024 18:13:37 +0000
- To: public-css-archive@w3.org
> It doesn't seem like there is a benefit to developers (or a difference) between select { appearance:base; } and select::picker(select) { appearance:base; }. Why force developers to remember both selectors that they will need to target, degrading the developer experience?
I agree with Una that this adds extra overhead for developers. Under the premise that we ship appearance:base for all in-page form controls at once before doing select and other ones with pickers it makes sense as an incremental opt-in for compatibility, but I don't think that chromium is going to ship appearance:base for other form controls before select.
Maybe a middle ground would be to make `select::picker(select) { appearance:base; }` imply `select { appearance:base; }` so you only have to write one of them instead of both?
--
GitHub Notification of comment by josepharhar
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10440#issuecomment-2245934280 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 July 2024 18:13:38 UTC