Reland "Update popover post-toggle event naming and behavior" #38269
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wpt-pr-bot
approved these changes
Jan 30, 2023
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-4205710
branch
from
ea78570
to
d7ed58d
Compare
This is a reland of commit 2e5ee120d7fc5df4b6c101e88d03a5f62a73d8b8 It seems that the event coalescing behavior changes cause a segfault in the event dispatch code. This reland (compare to Patchset 1) just includes the event renaming, and not the new behavior. I'll land the new behavior in a separate CL to make it smaller if it gets reverted again. This part should be safe. Original change's description: > Update popover post-toggle event naming and behavior > > This CL updates the post-toggle event in the following ways: > 1. Rename the 'aftertoggle' event to 'toggle'. > 2. Rename PopoverToggleEvent to ToggleEvent. > 3. Rename the currentState attribute to oldState. > 4. Add event coalescing behavior. If two transitions occur before the > first 'toggle' event has been fired, cancel the first event and > queue a replacement that has oldState === newState. > > These changes were driven by the corresponding changes to the spec PR: > whatwg/html#8717 > > Bug: 1307772 > Change-Id: Iabc5a9093d7cef3bbd6e54e488d8e571c51ea568 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4195120 > Auto-Submit: Mason Freed <[email protected]> > Commit-Queue: Joey Arhar <[email protected]> > Reviewed-by: Joey Arhar <[email protected]> > Cr-Commit-Position: refs/heads/main@{#1098728} Bug: 1307772 Change-Id: Iede18bbf05516cec4ee881f1afc663c45380c82e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4205710 Reviewed-by: Joey Arhar <[email protected]> Commit-Queue: Joey Arhar <[email protected]> Auto-Submit: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1099397}
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-4205710
branch
from
d7ed58d
to
e24e557
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a reland of commit 2e5ee120d7fc5df4b6c101e88d03a5f62a73d8b8
It seems that the event coalescing behavior changes cause a segfault
in the event dispatch code. This reland (compare to Patchset 1) just
includes the event renaming, and not the new behavior. I'll land
the new behavior in a separate CL to make it smaller if it gets
reverted again. This part should be safe.
Original change's description:
Bug: 1307772
Change-Id: Iede18bbf05516cec4ee881f1afc663c45380c82e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4205710
Reviewed-by: Joey Arhar <[email protected]>
Commit-Queue: Joey Arhar <[email protected]>
Auto-Submit: Mason Freed <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1099397}