Keith Cirkel

It is not just `` but also ``. This is intentional. Triggers need to be able to receive focus, and be presented as a page control to assistive technologies. It...

Elements with a `role=button` will not work because only `button` & `input` have the mixin. You can use the imperative API of `popover.showPopover()`/`popover.hidePopover()`/`popover.togglePopover()`, or alternatively the custom element can have...

An element like `` could reflect the attribute to a button in the underlying ShadowDOM. Alternatively this could make for a motivating use case for built-in customised elements, so having...

Yeah FWIW I'm not suggesting it couldn't (or even wouldn't) be supported but I'm explaining the current rationale. Currently `role=button` cannot be supported because the mixin only applies to ``...

In order to use the popover API cross-root, you will need to use JS. If the popover API is used entirely in light DOM, or entirely within a shadow root,...

I wonder if flipping customised built in elements on their head would be useful? `` is arguably still SOLID vs ``.

We briefly discussed a solution that could work for this in the hack week discussion on AOM reference targets. @lukewarlow or @alice might be able to say more but I...

I can't speak for Mozilla, but the implementation I'm writing in Gecko attaches event listeners to the close watcher to propagate the events for dialog & popover. In other words...

Oh yeah I meant to back link. Thanks for doing that @sroucheray

Looks like `--dialog-scrollgutter` isn't being applied which is causing the shift in the underlying body content... But that's not the issue @maximedegreve is describing here, is it? It looks like...