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

DOM: Add WPTs for removing steps #44774

Merged
merged 1 commit into from
Feb 29, 2024

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Feb 25, 2024

This CL adds WPTs for removing steps, to ensure that script is never
executed during the removing steps hook 1, which are invoked
synchronously during per-node removal (that is, they are not batched,
but run this way per-node).

This CL:

  1. Augments the existing iframe removing steps WPT, to include
    pagehide events. At the time of writing this, all browsers deviate
    from the HTML Standard, and fail this test.
  2. Adds new tests for \<input> and \<button> to assert that when they
    are focused and subsequently removed from the DOM, the blur event
    is not fired, per the HTML Standard. Chromium fails this test,
    while Safari and Firefox pass it.

Bug: 40150299
Change-Id: I0aa43755ccac8ea432056800c5c4167d8e4460e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5323158
Commit-Queue: Dominic Farolino <dom@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1266801}

This CL adds WPTs for removing steps, to ensure that script is never
executed during the removing steps hook [1], which are invoked
synchronously during per-node removal (that is, they are not batched,
but run this way per-node).

This CL:
 1. Augments the existing iframe removing steps WPT, to include
    `pagehide` events. At the time of writing this, all browsers deviate
    from the HTML Standard, and fail this test.
 2. Adds new tests for `<input>` and `<button>` to assert that when they
    are focused and subsequently removed from the DOM, the `blur` event
    is *not* fired, per the HTML Standard. Chromium fails this test,
    while Safari and Firefox pass it.

[1]: https://dom.spec.whatwg.org/#concept-node-remove-ext

Bug: 40150299
Change-Id: I0aa43755ccac8ea432056800c5c4167d8e4460e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5323158
Commit-Queue: Dominic Farolino <dom@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1266801}
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.

@chromium-wpt-export-bot chromium-wpt-export-bot merged commit 2c931fe into master Feb 29, 2024
12 of 14 checks passed
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-5323158 branch February 29, 2024 03:27
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