[w3ctag/design-reviews] The Popup API (Issue #743)

Wotcher TAG!

I'm requesting a TAG review of the Popup API. This is a third attempt at a TAG review for this feature; see https://github.com/w3ctag/design-reviews/issues/599 for the first, and https://github.com/w3ctag/design-reviews/issues/680 for the second.

A very common UI pattern on the Web, for which there is no native API, is "popup UI" or "popups". Popups are a general class of UI that have three common behaviors:

  1. Popups always appear on top of other page content.
  2. Popups are ephemeral. When the user "moves on" to another part of the page (e.g. by clicking elsewhere, or hitting ESC), the popup closes.
  3. Popups (of a particular type) are generally "one at a time" - opening one popup closes others.

We are proposing a set of APIs to make this type of UI easy to build.


  - Explainer: https://open-ui.org/components/popup.research.explainer

  - User research: https://open-ui.org/components/popup.research

  - Security and Privacy self-review²: 
  - GitHub repo (if you prefer feedback filed there): https://github.com/openui/open-ui/issues (please use the Popup label)
  - Primary contacts (and their relationship to the specification):
      - Mason Freed (@mfreed7), Google
  - Organization/project driving the design: Google and Microsoft
  - External status/issue trackers for this feature: https://chromestatus.com/feature/5463833265045504


Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - The group where the incubation/design work on this is being done (or is intended to be done in the future): https://open-ui.org/

  - The group where standardization of this work is intended to be done ("unknown" if not known): WHATWG mostly
  - Existing major pieces of multi-stakeholder review or discussion of this design: https://github.com/openui/open-ui/issues?q=is%3Aissue+label%3Apopup

  - Major unresolved issues with or opposition to this design: No major unresolved issues or opposition that I'm aware of. [There are several details](https://github.com/openui/open-ui/issues?q=is%3Aissue+is%3Aopen+label%3Apopup+-label%3Apopup-spec) still under active discussion.
  - This work is being funded by: Google and Microsoft

You should also know that...

This is a third attempt at a TAG review for this feature. The [first attempt](https://github.com/w3ctag/design-reviews/issues/599) was closed due to the lack of an Anchor Positioning proposal. That has now been proposed, and there's a [draft spec](https://tabatkins.github.io/specs/css-anchor-position/). The [second attempt](https://github.com/w3ctag/design-reviews/issues/680) was closed because we changed directions from a `<popup>` element to a `popup` content attribute. This third TAG review is for that new content-attribute-based approach.

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify @mfreed7


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/743

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/743@github.com>