Re: [csswg-drafts] [selectors] Add pseudo-classes for `<select>` being a drop-down box vs a list box (#7422)

To sum up my position from the call, while it seems like useful functionality, the way it is currently discussed has several warts. Using a plain `:has-picker` would imply that this works for other controls with pickers (date inputs, color pickers etc — those targeted by `input.showPicker()`), but `:has-picker(select)` is _incredibly_ weird and unprecedented.

But most importantly, if `:has-picker` only works for `appearance: base` as was discussed, that introduces a circularity:

```css
select {
 appearance: base-select;
}

select:has-picker {
 appearance: auto; /* now it no longer matches */
}
```

We have historically avoided making selector matching depend on CSS properties for this reason.

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7422#issuecomment-3113897813 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 24 July 2025 15:22:15 UTC