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.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
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.
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.
|OriginTrial desktop last||112|
|OriginTrial desktop first||106|
|DevTrial on desktop||104|
|OriginTrial Android last||112|
|OriginTrial Android first||106|
|DevTrial on Android||104|
|OriginTrial webView last||112|
|OriginTrial webView first||106|
Has this feature changed in a breaking way since the first OT?
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%3DNeDiY%2BGQvrhvVpp5PYF-nQ9_R3JUbFRbJi1a12gJvG%2B58DA%40mail.gmail.com.