-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Set popover invoker immediately after changing popover's visibility state to "showing" #9481
Set popover invoker immediately after changing popover's visibility state to "showing" #9481
Conversation
…tate to "showing" See <whatwg#9383 (comment)>. Fixes whatwg#9383.
Test-coverage: https://github.com/web-platform-tests/wpt/blob/b87174e39fd3a502910430752d7f9fce233b1b35/html/semantics/popovers/popover-invoker-reset.html violated an assertion before, now it doesn't anymore, see #9383 (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.
This matches what I am implementing in chromium. Thanks for the PR!
Corresponding change is being merged in chromium: https://chromium-review.googlesource.com/c/chromium/src/+/4657399 |
This seems like a normative change which normally has a PR template. How can be sure implementations will align with this change? I guess there's already a test which contradicts the current specification? |
Yes, the current assertion in the spec about the invoker not being set will be hit. Presumably implementations have not added that assertion yet, because if they did, they would be hitting it without this PR |
@annevk: Yes, there's a test which currently violates an assertion, see #9383 (comment). |
See
#9383 (comment).
Fixes #9383.
/popover.html ( diff )