Put it in the spec asap! 😆

If they’ve moved to an iframe!

Been looking forward to playing around with the combo box stuff since we talked about it in last week’s openui meeting

Nothing like the announcer curse

Perhaps at TPAC?

I’ve been following that (and my team is very interested in this proposal);

Would enjoy working to understand your team’s hesitations, especially given Mason’s last comment and all the research + collaboration with accessibility experts there has been on this.

❤️

Jake you’re not supposed to critically look at these; just hype and boost.

(Thanks for catching that, we’ll get it fixed up!)

Just finished it. Very nice write up, thanks for the work on this

At first I thought being explicit would be the easy answer. I generally like explicitness.

In this case, however, now that I’ve seen the options and the constraints (always only ever 3 rows/columns), I actually don’t mind the current spec.

I’ve got bad news for us

:/ yeah ok, makes sense. But also a bit of overhead to wire this up correctly, and I wonder how many devs would even realize it’s necessary

Dumb question: Curious about timing for this; if you do it when the component is connected, do you then need an observer to watch if the reference element changes and reassign?

Or could you assign it on the click’s capture phase to assign it as close as possible to when the native code takes over?

Command invokers is one! Since they are scoped to their own tree, it means a button in a shadow root only invokes things in that same shadow, which isn’t helpful.

I feel like that’s the only deck that a straight run is viable on. Still can be hard anyway haha

What about using a smoker? Smoke that thing for 12 hours