- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Feb 2025 16:56:22 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Incremental rollout plan for form controls`. <details><summary>The full IRC log of that discussion</summary> <jarhar> masonf: i went through all of the form controls and some other things and detailed what ive heard from openui about whats needed<br> <jarhar> masonf: its a list of controls that i hope we consider in scope for appearance base<br> <jarhar> masonf: it also has thoughts about how to ship it, but we can punt that to later<br> <jarhar> masonf: if there are comments, id love to hear them<br> <lwarlow> q+<br> <astearns> ack lwarlow<br> <astearns> q+<br> <jarhar> lwarlow: it mentions that button might be good as is. there are still situations where styling them can be a bit of a pain. ios safari might need to reset some properties to be able to style it<br> <jarhar> lwarlow: i dont think that if you apply padding to it that it works out of the box<br> <jarhar> lwarlow: also stuff around text selection that differs, which would be good to formalize in base appearance<br> <jarhar> masonf: im familiar with text selection stuff. i dont know about the issue you brought up first, but both of them sound like interop issues<br> <jarhar> masonf: when i say good as is i mean that theres not necessarily anything to opt in to with appearance base<br> <jarhar> t1m: for buttons, i think that for appearance base we will want to use the same styling as select. inerhit all the properties and use currentcolor and all that stuff<br> <jarhar> masonf: the one value that would provide is that people dont have to do resets<br> <jarhar> masonf: the good as is list means that you can reset it and make it stylable<br> <jarhar> astearns: what about elements not in this issue? are they absolutely not relevant? or is there a subset that you're pretty sure aren't relevant but you'd like confirmation?<br> <jarhar> masonf: i tried to be complete as i could. i did not include details summary, which maybe is on the border of relevant<br> <jarhar> masonf: we should have as inclusive a list as possible<br> <jarhar> masonf: dont want to leave something out. please comment to add stuff<br> <jarhar> astearns: would be good to add a comment saying that<br> <jarhar> t1m: i mentioned earlier that composability is not part of css forms 1. the pseudo elements that im planning to introduce are cover a lot of use cases you mentioned. input type number with a set of pseudos you can do a plus one and minus ui<br> <jarhar> t1m: by messing with the ordering and display contents and the pseudo elements<br> <jarhar> t1m: i can add more about the depths of customization you can get to in the spec<br> <jarhar> t1m: the current set of pseudos can get you really far without needing to replace all the content thats in the control<br> <jarhar> t1m: once i get the spec out there we can discuss which ones still need composability<br> <jarhar> lwarlow: make a comment with all the other html elements that exist, that would answer the question, would also help us find things that we misses<br> <jarhar> *missed<br> <jarhar> masonf: ill have to consider whether deprecated elements like <blink> are included<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10804#issuecomment-2640465825 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 February 2025 16:56:24 UTC