On Thu, Dec 8, 2022 at 11:26 PM Alex Russell <[email protected]>
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
<https://github.com/openui/open-ui/issues/627>.) Some smaller details also
changed, such as the removal of `defaultopen` and the animations capability.

Thanks,
Mason




> Thanks,
>
> Alex
>
> On Thursday, December 8, 2022 at 4:27:28 PM UTC-8 Mason Freed wrote:
>
>> 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 [email protected]
>>
>> Explainerhttps://open-ui.org/components/popup.research.explainer
>>
>> Specificationhttps://github.com/whatwg/html/pull/8221
>>
>> 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 componentBlink>HTML>Popover
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EHTML%3EPopover>
>>
>> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/743
>>
>> TAG review statusPending
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>>
>>
>> *Gecko*: No signal (
>> https://github.com/mozilla/standards-positions/issues/698)
>>
>> *WebKit*: Positive (
>> https://github.com/WebKit/standards-positions/issues/74#issuecomment-1311566112)
>> "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
>>
>> 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
>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>> ?No
>>
>> Flag name#enable-experimental-web-platform-features
>>
>> Requires code in //chrome?False
>>
>> Tracking bughttps://crbug.com/1307772
>>
>> Estimated milestones
>> 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
>>
>> Link to entry on the Chrome Platform Status
>> https://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/_4gShWjQAAAJ
>> Intent to Experiment:
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDjJOC2%2B5aHfAoN8wOx8T0gtm%3D-o6eNK5XD6Ps5iRet6zA%40mail.gmail.com
>>
>>
>> This intent message was generated by Chrome Platform Status
>> <https://chromestatus.com/>.
>>
>

-- 
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 [email protected].
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.

Reply via email to