- From: Joey Arhar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 May 2024 17:24:13 +0000
- To: public-css-archive@w3.org
josepharhar has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-ui] New value(s) for the appearance property to support `<select>` stylability == In this issue, we have been discussing adding one or more new values to the appearance property to make an interoperable and stylable rendering of `<select>`, and potentially other elements in the future: https://github.com/w3c/csswg-drafts/issues/5998 Some possibilities: 1. Add `appearance:base-select` (or another name) for this, and add additional values as needed for other elements. - We could also add more modes for `<select>`, [such as `appearance:base-select-excluding-picker`](https://github.com/w3c/csswg-drafts/issues/5998#issuecomment-2107056489). - If we get to making a stylable interoperable version of `<select multiple>`, it could also use `base-select` or another new name. 2. Add `appearance:base` and make the interoperable and stylable mode for all form control elements use this. - This has potential forward compat issues when people apply it to elements which aren't supported yet. - This doesn't seem to support the `appearance:base-select-excluding-picker` use case. I don't think it's possible to make all form control elements have an interoperable and stylable `appearance:base` mode before we ship anything because it could take decades to do this for each element. We can also add `appearance:base` later if we make all form control elements have a `base-something` mode, but I'm not sure if this really makes sense given the `appearance:base-select-excluding-picker` use case. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10333 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 May 2024 17:24:14 UTC