Intent to extend Origin Trial: Popover API

Skip to first unread message

Mason Freed

Dec 8, 2022, 7:27:28 PM12/8/22
to blink-dev

Hi API Owners,

We'd like to extend the Popover Origin Trial for 2 additional milestones. The original OT was 106 to 110, but due to many good discussions and bits of feedback, we'll need more time before being able to ship this API. The OT partners would like to continue experimenting in the meantime.

This request is to extend from 110 to 112.

Contact emails




An API that can be used to build transient user interface (UI) elements that are displayed on top of all other web app UI. These include user-interactive elements like action menus, form element suggestions, content pickers, and teaching UI. This API uses a new `popover` content attribute to enable any element to be displayed in the top layer. This is similar to the <dialog> element, but has several important differences, including light-dismiss behavior, popover interaction management, animation and event support, and the lack of a "modal" mode.

Blink component


TAG review

TAG review status



Interoperability and Compatibility

Gecko: No signal (

WebKit: Positive ( "Largely positive"

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

Goals for experimentation

Validation of the shape and ergonomics of the overall popover API. Feedback should include use cases that do not work well (or that do work particularly well), performance issues, etc. Ideally, use cases should include as much of the API as possible, including multiple popover types (auto, manual), nested popovers, declarative and imperative popover invocation, etc.

Reason this experiment is being extended

Ongoing technical constraints



A feature has been added to devtools which shows all of the elements that are currently in the top layer, plus annotations of those elements in the Elements tree. Elements that use the popover API will be shown with this feature.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?


Is this feature fully tested by web-platform-tests?


Flag name


Requires code in //chrome?


Tracking bug

Estimated milestones

OriginTrial desktop last112
OriginTrial desktop first106
DevTrial on desktop104
OriginTrial Android last112
OriginTrial Android first106
DevTrial on Android104
OriginTrial webView last112
OriginTrial webView first106

Link to entry on the Chrome Platform Status

Links to previous Intent discussions

Intent to prototype:
Intent to Experiment:

This intent message was generated by Chrome Platform Status.

Alex Russell

Dec 9, 2022, 2:25:58 AM12/9/22
to blink-dev, Mason Freed
Has this feature changed in a breaking way since the first OT?



Mason Freed

Dec 12, 2022, 2:59:42 PM12/12/22
to Alex Russell, blink-dev
On Thu, Dec 8, 2022 at 11:26 PM Alex Russell <> wrote:
Has this feature changed in a breaking way since the first OT?

Yes, in the course of the OT, the name of the attribute(s) changed from `popup` to `popover`. (Context here.) Some smaller details also changed, such as the removal of `defaultopen` and the animations capability.


Yoav Weiss

Dec 12, 2022, 11:07:19 PM12/12/22
to Mason Freed, Alex Russell, blink-dev
LGTM to extend experimentation to M112

You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit
Reply all
Reply to author
0 new messages