- From: Lea Verou via GitHub <noreply@w3.org>
- Date: Wed, 16 Jul 2025 17:30:39 +0000
- To: public-css-archive@w3.org
@josepharhar > > as long as base-select also applies to listboxes, authors can switch between the two already with minimal CSS > > In my opinion, this is hacky and should not be encouraged. I'm also not sure how minimal it would really be, and I'm not sure if accessibility mappings would work correctly. That’s my current thinking as well. > > size is a presentational attribute and it feels wrong to control the listbox height in HTML > > I agree, but creating a new attribute got negative feedback here: [whatwg/html#8189 (comment)](https://github.com/whatwg/html/issues/8189#issuecomment-2503177401) Let’s see how https://github.com/whatwg/html/issues/11452 goes, which is exactly about that. whatwg/html#8189 seems to be about a bunch of different things. Note that the HTML to control in-page vs dropdown is only one part of fixing this architectural issue. The other part is allowing CSS to do the same thing as what `size` currently does, i.e. setting width or height to an integer number of options. I’m not even sure what that would look like. A generalizable feature could be to set any element to an integer number of children, but options are not actually the select's children… @keithamus As I said in the call, dropdown → listbox is only half of the problem, and not even the most common use case. How do you go from listbox → dropdown? > I suppose if we had the ability to set `overlay:none`, the accessibility engine could check if the picker is in the top layer, and if not check if it has layout, and if it does then it is a listbox. That seems like the wrong order of dependencies to me. The a11y should not have to depend on computed style heuristics… -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12468#issuecomment-3079570224 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 July 2025 17:30:40 UTC