- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 07 Aug 2025 15:22:58 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-forms-1] UA styles for base appearance listbox select elements`. <details><summary>The full IRC log of that discussion</summary> <zcorpan> jarhar: I incorporated feedback from the last meeting<br> <zcorpan> jarhar: overflow (etc) examples. Any feedback on these?<br> <emilio> q+<br> <zcorpan> fantasai: field-sizing: contents<br> <astearns> ack fantasai<br> <zcorpan> jarhar: The idea was ignore the size attribute, make it as tall as it would normally be<br> <zcorpan> fantasai: OK<br> <zcorpan> jarhar: Luke I think suggested this. Makes it easer to write tests<br> <zcorpan> emilio: What is the behavior if you remove field-sizing: contents?<br> <zcorpan> jarhar: customizable select I didn't use it in the UA style. Turning off intrinsic sizing. We should be consistent, but ok to make changes<br> <astearns> ack emilio<br> <zcorpan> emilio: We're making appearance: base select a scrollable block. Get field-sizing: contents for free<br> <zcorpan> jarhar: We should say field-sizing: content !important<br> <zcorpan> emilio: Unnecessary? Can remove and have the same effect<br> <zcorpan> emilio: I think (MISSED) doesn't match other form control behavior<br> <zcorpan> jarhar: user-select, I can go back to the issue and link the previous discussion<br> <zcorpan> emilio: makes sense to be consistent, but curious why<br> <zcorpan> emilio: Could be use cases for e.g. a search field on the picker<br> <zcorpan> emilio: It inherits down<br> <jarhar> q?<br> <jarhar> https://github.com/whatwg/html/issues/8189<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12510#issuecomment-3164665078 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:22:59 UTC