Joey Arhar

I was just talking to @una and she said that using a `` which accepts rich content in `` would be inconsistent because `` won't accept rich content when used...

OpenUI resolved on using an attribute instead of datalist/button to opt in to the new parser behavior: https://github.com/openui/open-ui/issues/985#issuecomment-1922141513 This would mean that the following would parse all elements: ```html one...

> Doesn't this break Step 1. of https://whatpr.org/html/10098/input.html#show-the-picker,-if-applicable ? Ah yes you're right. I moved the user activation consumption to be after the call to "show the picker"

> Looks like showPopovers() invocation of topmost popover ancestor needs to be given true. done

@domenic I updated it, we can merge now

Note to self: this will require additional changes in https://chromium-review.googlesource.com/c/chromium/src/+/5229300 if the corresponding PR to be opened gets merged

I think this needs the "toggle task tracker" concept used in details elements in order to coalesce async toggle events: https://html.spec.whatwg.org/multipage/interactive-elements.html#queue-a-details-toggle-event-task If you do this and open+close the dialog element...

Consider chrome as tentatively interested. I will file an intent to ship to get an official position when this gets a bit more attention from the other browsers, but I...

Tests can be added to the OP: https://github.com/web-platform-tests/wpt/pull/44208

~~`[popover]:not(:modal)::backdrop` and `[popover]:popover-open::backdrop` aren't working for the `overlay-transition-backdrop-entry.html` test I'm adding: https://github.com/web-platform-tests/wpt/pull/40369/files#diff-9dc3657353b3d04b1a244272b418d008cc6773665b6e7ff0e096dd35543446b3~~ ~~We need to stop matching the user-agent styles to ::backdrop when the popover is showing but its entrance...