Skip to content
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

Revert "Update popover post-toggle event naming and behavior" #38268

Merged
merged 1 commit into from
Jan 30, 2023

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Jan 30, 2023

This reverts commit 2e5ee120d7fc5df4b6c101e88d03a5f62a73d8b8.

Reason for revert: cause test failures on Linux Tests (dbg)

Example failures:
https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Tests%20(dbg)(1)/111061/
https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Tests%20(dbg)(1)/111062/

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: I6e466ecffe4726b4ec69ca14704b24842e45f5d6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4205308
Owners-Override: Phillis Tang <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Commit-Queue: Phillis Tang <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1098927}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

This reverts commit 2e5ee120d7fc5df4b6c101e88d03a5f62a73d8b8.

Reason for revert: cause test failures on Linux Tests (dbg)

Example failures:
https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Tests%20(dbg)(1)/111061/
https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Tests%20(dbg)(1)/111062/

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: I6e466ecffe4726b4ec69ca14704b24842e45f5d6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4205308
Owners-Override: Phillis Tang <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Commit-Queue: Phillis Tang <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1098927}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants