You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just as dialog element, Pop Up API will allow users to create overlays that are accessible.
Most of those APIs are in proposal stage but putting this on Interop 2023 would allow those highly anticipated features as quickly available in multiple browsers as possible. Still focusgroup for example is already in dev traials and planned for origin trails in chrome/edge.
I see that #135 overlaps slightly with this proposal. Other than :modal, it looks like none of the specifications listed are on the standards track. Do you expect all or some of this to be in a standards track spec by the time we start to evaluate proposals?
Can you check out the README and then decide if you want to pursue a Focus Area or Investigation Effort proposal? If you want to edit this issue to match either template that's fine, but I think filing a new issue would be cleaner.
Description
Implement / update implementations of things needed for native overlays - mostly but not only those from list below.
Specifications
Popup AP
Popup API - Micosoft
Popup API - OpenUI
:modal / :top-layer pseudoclass
:modal / :top-layer
:modal w3
CSS Anchor Positioning,
CSS Anchor Positioning,
focusgroup
focusgroup
Rationale
Just as dialog element, Pop Up API will allow users to create overlays that are accessible.
Most of those APIs are in proposal stage but putting this on Interop 2023 would allow those highly anticipated features as quickly available in multiple browsers as possible. Still focusgroup for example is already in dev traials and planned for origin trails in chrome/edge.
Chromium implementation status
focusgroup
CSS Anchor Positioning
The Popup API
CSS :modal Pseudo Class
The text was updated successfully, but these errors were encountered: