[wp-trac] [WordPress Trac] #61959: Enhance Support for `popovertarget` and `popover` Attributes in Native Browser Popover API
WordPress Trac
noreply at wordpress.org
Thu Jan 30 22:46:18 UTC 2025
#61959: Enhance Support for `popovertarget` and `popover` Attributes in Native
Browser Popover API
-------------------------------------+-------------------------------------
Reporter: harshdeepgill | Owner: tirth03
Type: enhancement | Status: assigned
Priority: normal | Milestone: 6.8
Component: General | Version: 6.6.1
Severity: normal | Resolution:
Keywords: has-patch reporter- | Focuses: ui, accessibility,
feedback | javascript, css
-------------------------------------+-------------------------------------
Changes (by joedolson):
* milestone: Future Release => 6.8
Comment:
It's more accurate to say that certain accessibility guardrails are baked
in, but not enough to actually turn it into an independent accessible
interface component.
But I'll freely admit that I'm on the fence about this. But right now the
accessibility API mapping is a moving target, because it's been changing
fairly rapidly. Last I checked, it had very irregular handling on mobile &
was limited in WebKit, but that was months ago.
But one of the largest concerns is that since CSS Anchor Positioning is
not yet mainstream, there are limitations on how usable the popover will
be without JS.
What I'll say is that this can wait until late in the release cycle; it's
pretty trivial to add; I just need to find the time to thoroughly check it
over so that I know the exact cross-browser limitations.
Happy to move it back into the 6.8 milestone, just with the caveat that
it's going to need an accompanying article on usage and limitations, and
that should be considered a blocker to commit.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/61959#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list