-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Add imperative access to popover invoker, and connect popover/invoker to implicit anchor element #10728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
domenic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normative behavior looks good. A variety of editorial tweaks.
mfreed7
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick review! I think I got everything, LMK if I missed something.
domenic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Editorially LGTM (with one more nit). Let us know when all the boxes are checked.
Thanks! Done. It would be good to get the attention of @annevk and @smaug----, since the implementer support checkbox relies on our joint resolution at the form controls task force. (And I therefore didn't want to clutter up the standards positions requests for this.) |
This includes two related changes:
1. The `showPopover()` and `togglePopover()` methods now include an
options bag that allows setting the popover invoker.
2. Popover invokers (declaratively or imperatively set) now create
an implicit anchor reference for that popover.
This new behavior was resolved in the [WHATWG/CSSWG/OpenUI joint task
force meeting on June 26, 2024](whatwg#9144 (comment)).
Closes whatwg#10442
Closes whatwg#10675
691b3fb to
5602678
Compare
|
@mfreed7 OP doesn't include a link to a PR for renaming the tests away from |
There seems to be a chicken and egg problem with this. I've had folks complain about renaming .tentative too early (before the spec PR lands) and too late (after the spec PR lands).
|
Ideally you create a PR against web-platform-tests that the specification editors can merge. That's how we have done this thus far. |
The spec PR landed: whatwg/html#10728 so this removes .tentative from the WPTs. Bug: 364669918 Change-Id: I35e50fff8d94ff52e212844814a4e597c35d78b4
The spec PR landed: whatwg/html#10728 so this removes .tentative from the WPTs. Bug: 364669918 Change-Id: I35e50fff8d94ff52e212844814a4e597c35d78b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6025803 Commit-Queue: Di Zhang <[email protected]> Reviewed-by: Di Zhang <[email protected]> Auto-Submit: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1384325}
The spec PR landed: whatwg/html#10728 so this removes .tentative from the WPTs. Bug: 364669918 Change-Id: I35e50fff8d94ff52e212844814a4e597c35d78b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6025803 Commit-Queue: Di Zhang <[email protected]> Reviewed-by: Di Zhang <[email protected]> Auto-Submit: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1384325}
The spec PR landed: whatwg/html#10728 so this removes .tentative from the WPTs. Bug: 364669918 Change-Id: I35e50fff8d94ff52e212844814a4e597c35d78b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6025803 Commit-Queue: Di Zhang <[email protected]> Reviewed-by: Di Zhang <[email protected]> Auto-Submit: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1384325}
Yeah, ok. The Chromium process makes that a bit harder, since we're accustomed to doing the review for WPT stuff within our code review system, and it then gets pushed automatically. I don't know if there's an easy way to tell it not to merge the WPT PR when the Chromium PR gets merged. If you know of one, please let me know! |
Yeah. It's just a lot more work. 😄 |
|
That seems strange. It really shouldn't be. |
Only due to familiarity. I spend 99% of my time writing C++ code within Chromium's tooling, so venturing outside is painful. It's ok - I'll try to put up the rename PRs like this in the future. |
…PTs, a=testonly Automatic update from web-platform-tests Remove .tentative from popover invoker WPTs The spec PR landed: whatwg/html#10728 so this removes .tentative from the WPTs. Bug: 364669918 Change-Id: I35e50fff8d94ff52e212844814a4e597c35d78b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6025803 Commit-Queue: Di Zhang <[email protected]> Reviewed-by: Di Zhang <[email protected]> Auto-Submit: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1384325} -- wpt-commits: 6572d5b33f7e95cb1f857ed76d2cdd7939ef47ad wpt-pr: 49225
FWIW, similar here. Writing wpts is quite a bit easier on mozilla-central vs dealing with wpt repository explicitly. |
This includes two related changes:
showPopover()andtogglePopover()methods now include an options bag that allows setting the popover invoker implicitly. Previously this was only possible via the declarativepopovertargetattribute.This new behavior was resolved in the WHATWG/CSSWG/OpenUI joint task force meeting on June 26, 2024.
Closes #10442
Closes #10675
(See WHATWG Working Mode: Changes for more details.)
/dom.html ( diff )
/infrastructure.html ( diff )
/popover.html ( diff )
/references.html ( diff )