- From: Kevin Babbitt via GitHub <noreply@w3.org>
- Date: Tue, 01 Jul 2025 22:37:34 +0000
- To: public-css-archive@w3.org
`::step-up-button` and `::step-down-button` seem reasonable to me. Then I guess for the date input and input+datalist cases we'd have `::picker-button`? I can understand how having `::picker-icon` for some controls and `::picker-button` for others is a bit of a wart that authors might trip over, but I don't know that said wart outweighs the benefits of consistently naming things based on what purpose they fulfill. What are we thinking in terms of how to specify the glyphs for these buttons? Would it be, say, the `content` property on the `::*-button` pseudo-elements? Or would there be a sub-part that can be selected with its own pseudo-element and styled separately from the button? -- GitHub Notification of comment by kbabbitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11845#issuecomment-3025753723 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 July 2025 22:37:34 UTC