You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like that there are pseudos for styling the step-up and step-down buttons. I'm wondering if those need to be replaceable, e.g. with custom element buttons?
Also, even absent that, I think the stylesheet needs to include display:flex for both the <input> itself (which contains the ::field-text and the ::step-control, and should have flex-direction: row) and the ::step-control (which contains the buttons, and should have flex-direction:column).
Actually a number of controls that have defined internal structure like this should likely also have display:flex?
The text was updated successfully, but these errors were encountered:
Slight nit but I think it should be display: inline-flex I think, controls are currently inline rather than block layout by default and customisable select seems to have stuck with that.
Slight nit but I think it should be display: inline-flex I think, controls are currently inline rather than block layout by default and customisable select seems to have stuck with that.
Nit regarding the nit 😄: The value shoud then be the double-keyword value inline flex.
I like that there are pseudos for styling the step-up and step-down buttons. I'm wondering if those need to be replaceable, e.g. with custom element buttons?
Also, even absent that, I think the stylesheet needs to include
display:flex
for both the<input>
itself (which contains the::field-text
and the::step-control
, and should haveflex-direction: row
) and the::step-control
(which contains the buttons, and should haveflex-direction:column
).Actually a number of controls that have defined internal structure like this should likely also have
display:flex
?The text was updated successfully, but these errors were encountered: