[forms] Remove anonymous button content-box, and use CSS rather than magic for input / button block axis centering. - #12781
Conversation
Since adding a pseudo-class for listbox vs dropdown select elements didn't work out, we just reference the drop-down box definition explicitly with prose like this example in the rendering section:
|
I did this but trimmed out the appearance thing since I think this should apply regardless of appearance probably, see w3c/csswg-drafts#14319. If you object to that I'm happy to reintroduce it tho. |
…magic for input / button / select block axis centering. This defines the (previously undefined, afaict) unsafe center alignment of text inputs and textarea, and makes the changes discussed by the CSS Working Group in w3c/csswg-drafts#14190.
aeae1a5 to
ed3addd
Compare
|
Ah, actually for base appearance it would be a no-op (by default) because that's a flex container with flex-wrap: nowrap. So probably worth keeping consistency with input / button and specifying it. |
|
The title says "Remove anonymous button content-box" and I'm trying to figure out if that means we would have to change the structure of the shadowroot of the select element or other elements. Otherwise it just sounds like its just replacing style/layout magic with UA stylesheet rules, right? |
No, there's no change to the shadow root. Blink and Gecko no longer have an anonymous box for performing the centering. This was originally the way we implemented the vertical centering (before
Yes, that's correct. |
This defines the (previously undefined, afaict) unsafe center alignment of text inputs and textarea, and makes the changes discussed by the CSS Working Group in w3c/csswg-drafts#14190.
(See WHATWG Working Mode: Changes for more details.)
/rendering.html ( diff )