Intent to Extend Origin Trial: Popover API

[Mason Freed]

Hi API Owners,

I'd like to extend the Popover Origin Trial for 2 additional milestones. The original trial ran from 106 to 110, and was extended to 112. While the Popover feature is ready to ship now, and the spec has landed, there are some auxiliary features that enable animations of popovers. Those were initially part of the Popover API itself, but as a result of spec discussions, they were pulled out as standalone features so that they can be used for e.g. modal dialogs. However, given their criticality for normal use cases for Popovers, we'd like to wait to ship Popover until the animation features also land in the spec and ship. Hence the request to extend this OT so that there isn't a gap.

I'd like to extend this OT until 114.

Contact emails

mas...@chromium.org

Explainer

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

Specification

https://html.spec.whatwg.org/multipage/popover.html

Summary

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

Blink>HTML>Popover

TAG review

https://github.com/w3ctag/design-reviews/issues/743

TAG review status

Pending

Risks

Interoperability and Compatibility

Gecko: Positive (https://github.com/mozilla/standards-positions/issues/698)

WebKit: Positive (https://github.com/WebKit/standards-positions/issues/74)

Web developers: Positive Generally positive feedback from OT participants and OpenUI developer discussion.

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

None

Debuggability

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)?

No

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

No

Flag name

#enable-experimental-web-platform-features

Requires code in //chrome?

False

Tracking bug

https://crbug.com/1307772

Estimated milestones

OriginTrial desktop last	114
OriginTrial desktop first	106
DevTrial on desktop	104

OriginTrial Android last	114
OriginTrial Android first	106
DevTrial on Android	104

OriginTrial webView last	114
OriginTrial webView first	106

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5463833265045504

Links to previous Intent discussions

Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/9y-Thg9UCxY/m/_4gShWjQAAAJ
Intent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDjJOC2%2B5aHfAoN8wOx8T0gtm%3D-o6eNK5XD6Ps5iRet6zA%40mail.gmail.com
Intent to Extend Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDgMYePRFVsPLWyzKUYgkygR4C7iT88--h0zXGBKeckXeQ%40mail.gmail.com

This intent message was generated by Chrome Platform Status.

[Yoav Weiss]

LGTM to extend for 2 more milestones, given the strong evidence (landed spec PR, positive positions) towards shipping.

+Jason Robbins - FYI, this was missed by our tools.

--
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 blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDh%2B6z4wP00vgLx%3DEg6qvSv3qdcy7ADNp465Z1PKSH7CVw%40mail.gmail.com.

[Alex Russell]

Any thoughts you can share about why we shouldn't go straight to I2S given population support?

Best,

Alex

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfU-4K42%3D7%2BRO4jVAQHau6tCY59f2tViBfGuizX1dhgOeQ%40mail.gmail.com.

[Mason Freed]

On Wed, Feb 8, 2023 at 9:59 PM Alex Russell <sligh...@chromium.org> wrote:

Any thoughts you can share about why we shouldn't go straight to I2S given population support?

Yep, this is a great question that we wrangled with. We decided that since the animation support features are fairly core to any normal use case, it would be better to wait to ship Popover with those features. Otherwise, Popover will be "shipped" but kind of broken until animation support arrives. Hence the delay.

On Wed, Feb 8, 2023, 7:51 PM Yoav Weiss <yoav...@chromium.org> wrote:

LGTM to extend for 2 more milestones, given the strong evidence (landed spec PR, positive positions) towards shipping.

Thanks!