- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 07 Aug 2025 15:16:10 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-forms-1] Allow styling of input[type=number] number spinner`, and agreed to the following: * `RESOLVED: Accept the 3 pseudos that are currently in the spec` <details><summary>The full IRC log of that discussion</summary> <zcorpan> ntim: Want to sign-off what's in the spec<br> <zcorpan> ntim: Addition of step-up and step-down<br> <zcorpan> ntim: step-control is a wrapper<br> <zcorpan> astearns: Adding those details to the issue, to see if the commenter is satisfied, might be a good idea<br> <emilio> q+<br> <zcorpan> ack emilio<br> <astearns> ack emilio<br> <zcorpan> emilio: There's implicit, two things there. One, appearance: textfield must not generate those<br> <zcorpan> emilio: is that interoperable today?<br> <zcorpan> ntim: It's not the current behavior in webkit<br> <zcorpan> emilio<br> <zcorpan> emilio: OK, we probably need to keep that for compat. We don't expose the pseudos<br> <zcorpan> emilio: The other thing is mobile browsers don't generate these by default<br> <zcorpan> emilio: Should that be encoded in the UA stylesheet? Allowed by teh spec?<br> <zcorpan> ntim: I don't know<br> <zcorpan> ntim: The styles need to be consistent for appearance: base. Haven't thought so much about other appearance<br> <zcorpan> emilio: the spec presumes that order works. Should specify the base styles?<br> <zcorpan> ntim: yes, base appearance should use flexbox<br> <zcorpan> emilio: example uses (MISSED) on the container<br> <astearns> s/(MISSED)/display:contents/<br> <zcorpan> ntim: display: block<br> <zcorpan> emilio: seems weird. Gecko uses flexbox<br> <zcorpan> ntim: could make sense<br> <zcorpan> emilio: should add more details to the spec, how they are styled and what we want to allow. Remove the spinners on mobile<br> <zcorpan> emilio: OK with exposing these three<br> <zcorpan> ntim: Good points. Should do more analysis on the default style<br> <zcorpan> astearns: Are we taking a resolution? Apart from adding more details<br> <zcorpan> ntim: I was hoping we could resolve on having 3 pseudos<br> <zcorpan> astearns: So what's already in the spec<br> <zcorpan> astearns: Any other comments?<br> <zcorpan> Proposed resolution: Accept the 3 pseudos that are currently in the spec<br> <jarhar> +1<br> <zcorpan> RESOLVED: Accept the 3 pseudos that are currently in the spec<br> <jarhar> https://github.com/w3c/csswg-drafts/issues/12510<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8777#issuecomment-3164633431 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 August 2025 15:16:11 UTC