Luke Warlow

Looking through various older open ui [issues](https://github.com/openui/open-ui/issues/252) regarding light dismiss there's also talk of lightdismiss on window resize and scroll etc which all feel like reasonable discussions and extra wipe...

> For this reason, closetrigger="backdrop" is the safer option. I'm concerned developers might think this would disable Esc and Android back?

I would avoid escape key because the new html closewatchers concept has a close signal which is deliberately abstract to include ESC and back button. I should have been more...

Removing agenda+ as it's not recent. Re add if that's a mistake and you do want to discuss this

Have you got any thoughts on what the aria -mapping for these would look like. Afaik the default number input stepper buttons aren't keyboard navigable and so probably don't have...

I'm gonna go ahead and close this and replace it by https://github.com/openui/open-ui/pull/1029 it's effectively the same and I've included you as the commit co-author @spookylukey just deals with the IPR...

The problem with the above example is the existing parser restrictions. So we'd need an attribute or datalist to enable the new parsing model (for back compat). Or a new...

So to copy across from the other issue we've actually already got fullscreen API covered in the proposal, we've also resolved to look into a clipboard copy action. So something...

When we discussed this last week we said that invokers requires a trusted event which would solve this user activation requirement. As it turns out we were wrong and currently...

To further add to this I think the HTMLMediaElement actions should largely already be covered by autoplay policy. In my chromium implementation I've currently got some user activation checks but...