I take this back, it was easy enough to work around. But inspecting the accessibility tree and using a screenreader, it still requires a fair bit of wiring up with aria attrs
I haven’t done any cross browser testing outside of chrome since we’re an electron app, but for a tooltip component I had to fully wire it up together as if I was building it without popover. Which is fine I guess, the auto anchor behavior and top-layer is nice enough on its own
I imagine the advice will be to favour this over popover, since it is more capable generally and equally capable in terms of popover. The article I linked says:
> the new command and commandfor attributes, enhancing and replacing the popovertargetaction and popovertarget attributes
To be clear `popover` attribute remains. It's the popovertarget and popovertargetaction which is duplicated by commandfor/command so yeah once browser support is better it's probably best to just use command consistently.
Comments
I found this post (+ the links in it) pretty good to outline what you need to consider when using it https://hidde.blog/popover-accessibility/
At the bottom of the post I share a snippet of some stuff you can do do make it play nice together but it's still not perfect.
https://dev.to/link2twenty/dialogs-popovers-the-top-layer-mess-27li
> the new command and commandfor attributes, enhancing and replacing the popovertargetaction and popovertarget attributes