Re: [csswg-drafts] [css-position-4] Define "top layer" positioning scheme (#4998)

> Regarding the prior discussions, it sounds to me like there's actually a need for multiple (UA) top layers.

I just wanted to call out the [Popup API Proposal](https://open-ui.org/components/popup.research.explainer), which is being incubated in the [OpenUI WG](https://open-ui.org/). We've been thinking about these issues and many more, and we're working on a proposal, and [prototype](https://chromestatus.com/feature/5463833265045504) in Chromium, to support these use cases. There has been [significant discussion](https://github.com/openui/open-ui/issues?q=is%3Aissue+label%3Apopup). There are many nuances involved in creating the types of UI that use a "top layer" concept, so we'd really love your [feedback](https://github.com/openui/open-ui/issues/new) on the proposal. For example, a dedicated `<popup>` type element [was ruled out](https://open-ui.org/components/popup.proposal.alternatives#alternative-dedicated-popup-element) due to significant accessibility issues. Additionally, a CSS-based solution was [similarly ruled out](https://open-ui.org/components/popup.proposal.alternatives#alternative-css-property) due to significant limitations such as not allowing a tooltip on top of a dialog.

The hope is to bring the Popup API to a WHATWG PR fairly soon. There are some CSSWG pieces, such as [the `:top-layer` pseudo class](https://github.com/w3c/csswg-drafts/issues/7319) (or perhaps a different name, based on discussions).

I think this issue might need a bit of clarification. One interpretation is that it is about adding a CSS primitive to move elements into and out of the top layer. ([Hopefully not](https://open-ui.org/components/popup.proposal.alternatives#alternative-css-property).) The other interpretation is that the descriptions about how the top layer works should be augmented and moved into CSS specs.

-- 
GitHub Notification of comment by mfreed7
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4998#issuecomment-1143981323 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 1 June 2022 18:17:39 UTC