Simon Pieters

Yeah but appearance: none does the same (setting border or background implicitly sets appearance: none).

See https://github.com/whatwg/html/commit/c1e1f6f9e7d83af5affca071775a98f4b6abc29d for a proposal for this.

Discussion on twitter here https://twitter.com/benoitrouleau/status/1088883974296997890?s=20 Made me think that maybe display: inline isn't a good hook for this. It's good if you want an inline, but what about if you...

That `button` is implemented in terms of Flexbox by default in Chromium is considered a bug per https://github.com/whatwg/html/issues/4081#issuecomment-429989272 The magic defined in https://github.com/whatwg/html/pull/4143 is more likely to match what we...

Is there interest in standardizing this pseudo-class (and make it also available to author CSS)? cc @mfreed7 Via git blame of WebKit's html.css I found https://bugs.webkit.org/show_bug.cgi?id=220376 -- I think a...

[HTML's wording](https://html.spec.whatwg.org/multipage/rendering.html#the-select-element-2) is "list box" for `` and "drop-down box" for ``. However those terms are not web-exposed anywhere (prior to this pseudo-class), so they can be changed.

How about "list box" and "drop-down list box"? (Not sure about "list box" vs "listbox".)

It's not necessarily multi-select, though. ```html this is still single-select list box foo bar ```

We could define only a pseudo-class for the drop-down, and rely on the `:not()` function to match the not-drop-down state. ```css select:drop-down-list-box {} select:not(:drop-down-list-box) {} ```

> Also, would a native date picker or color picker be considered a drop-down, like `input[type=date]:has-drop-down`? Good question. I would say no. The date widgets are not guaranteed to have...