Should appearance: base select button have both `all: unset` and `display: contents` ?

[nt1m]

What is the issue with the HTML Standard?

@josepharhar @annevk @fantasai @whatwg/css @whatwg/forms

appearance: base select currently has:

select > button:first-child {
  all: unset;
  display: contents;
}

all: unset doesn't really do much when display: contents is applied rendering-wise. It only start coming into effect when you override display: contents

It's rather an expensive property to apply, though I'm not opposed to keeping it if there's some developer benefit

[emilio]

I assume all: unset is mostly useful so that things like font and color inherit (so, undoing the UA rules that would apply to the button otherwise)

[emilio]

But it'd probably better and more efficient to be explicit about them. Also there's no reason to reset backgrounds or what not

[josepharhar]

I assume all: unset is mostly useful so that things like font and color inherit (so, undoing the UA rules that would apply to the button otherwise)

Yes, this is the reason. Here is where @dbaron first suggested this: https://chromium-review.googlesource.com/c/chromium/src/+/6001193/comment/1dabaa79_26201aeb/

I originally did this instead:

select:not(:-internal-list-box) > button:first-child {
  display: contents;
  font: inherit;
  color: inherit;
  background-color: transparent;
}

Maybe it would make the most sense to just say that the button is rendered with base appearance in this case? That should make all of the inheritable propreties inherit instead of getting special UA values, right?