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.
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.
TAG review statusPending
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)?NoNo
Requires code in //chrome?False
|OriginTrial desktop last
|OriginTrial desktop first
|DevTrial on desktop
|OriginTrial Android last
|OriginTrial Android first
|DevTrial on Android
|OriginTrial webView last
|OriginTrial webView first
Link to entry on the Chrome Platform Statushttps://chromestatus.com/feature/5463833265045504
Links to previous Intent discussionsIntent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/9y-Thg9UCxY/m/_4gShWjQAAAJIntent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDjJOC2%2B5aHfAoN8wOx8T0gtm%3D-o6eNK5XD6Ps5iRet6zA%40mail.gmail.comIntent to Extend Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDgMYePRFVsPLWyzKUYgkygR4C7iT88--h0zXGBKeckXeQ%40mail.gmail.com