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

• From: Simon Pieters via GitHub <sysbot+gh@w3.org>
• Date: Mon, 08 Aug 2022 14:31:31 +0000
• To: public-css-archive@w3.org
• Message-ID: <issue_comment.created-1208208703-1659969089-sysbot+gh@w3.org>

A few names to consider

-  `:has-dropdown`
-  `:select-with-dropdown`
-  As above but with a dash in `drop-down`

Example usage:

```
select:has-dropdown { ... }
select:not(:has-dropdown) { ... }

select:select-with-dropdown { ... }
select:not(:select-with-dropdown) { ... }
```

or without type selector (when not using `:not()`)


```
:has-dropdown { ... }
select:not(:has-dropdown) { ... }

:select-with-dropdown { ... }
select:not(:select-with-dropdown) { ... }
```

It is probably better in terms of ergonomics to have two pseudo-classes for the two states, e.g.:

- `:has-dropdown` and `:no-dropdown`
- `:select-with-dropdown` and `:select-without-dropdown`

Since it will only match `select` elements it seems reasonable to include it in the name, as people may expect `:has-dropdown` to apply to other things with dropdowns and `:no-dropdown` to apply to almost all elements.

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


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

Received on Monday, 8 August 2022 14:31:33 UTC