09:23
<cwilso>
Thanks Noam! I can do the minutes/summary stuff afterward
12:49
<Jake Archibald>
jarhar: I see that show-popover is called to show the <select> popover. This includes firing a beforetoggle event, but I don't see that happening in Chrome. Which is wrong, the spec or the implementation? (also, the spec doesn't say which element to fire the event on. edit: oh yes it does I just didn't see it)
13:03
<Luke Warlow>
jarhar: I see that show-popover is called to show the <select> popover. This includes firing a beforetoggle event, but I don't see that happening in Chrome. Which is wrong, the spec or the implementation? (also, the spec doesn't say which element to fire the event on)

It gets fired on the picker element which is inside the selects UA shadow root. So isn't accessible to JS.

https://github.com/whatwg/html/issues/11564 - this proposes exposing it to the select itself.

Good point that it's missing a target currently.

13:08
<Jake Archibald>
Luke Warlow: Cheers! I ran into this when looking for a way to prevent the picker going into top-layer https://github.com/w3c/csswg-drafts/issues/13467
13:12
<Luke Warlow>
Would listbox select cover this use case? e.g. <select size="3">
13:13
<Jake Archibald>
Luke Warlow: yeah, I guess. I was trying to come up with a pure CSS way.
13:14
<Luke Warlow>
We played around with it a while back and there's some ways to get something like that but they all had issues, and I think were problematic for accessibility reasons too. Fwiw customisable listbox select (including multiple) will be in Chrome 145 I think.
13:15
<Jake Archibald>
nice, yeah, that's fair
14:28
<Noam Rosenthal>
No worries. If you are still around, can you Agenda- the things that were already discussed please?