- From: Lea Verou via GitHub <noreply@w3.org>
- Date: Wed, 09 Jul 2025 15:47:17 +0000
- To: public-css-archive@w3.org
LeaVerou has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-forms-1] Should `appearance: base-select` work on listbox selects? (`<select size>`/`<select multiple>`) == `<select>` can be rendered as either a dropdown or a listbox, when either `size` or `multiple` is set. Setting aside the fact that this was a terrible design choice that confounds unrelated concepts (that ship has sailed…), it appears that the newly shipped implementations of `appearance: base-select` do not account for these presentations of `<select>`. For example, [this](https://codepen.io/leaverou/pen/VYvZJex) is a fork of [Chrome’s `base-select` demo](https://codepen.io/web-dot-dev/pen/zxYaXzZ) from [this article](https://developer.chrome.com/blog/a-customizable-select), with `size="3"` added to it. Suddenly, all the new parser goodness is gone. The current draft has precious little on listboxes: - Only a [`::picker-icon`](https://drafts.csswg.org/css-forms-1/#pseudo-elements) pseudo-element defined for `<select>`, with no mention that this doesn't apply to listboxes - The only mention of listboxes seems to be a [reference](https://drafts.csswg.org/css-forms-1/#selects-listboxes) to issue #7422 Given that `base-select` has shipped fairly recently, and is a feature that authors are very excited about, I think this is high priority since otherwise we may be locked in to preserving the current behavior for web compat reasons. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12468 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 July 2025 15:47:18 UTC