Add failing displaylocking+shadowdom crash tests #30014
Merged
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
Aug 12, 2021
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-3072277
branch
from
67a1b5d
to
ba102c5
Compare
These crashing tests were uncovered by clusterfuzz after I landed a patch to use content-visibility in <details>. It turned out that all of them could also reproduce the crash without the use of <details>, so here they are. Bug: 1236774 Change-Id: Ib44f6f8167929c90d4b78c6e153ad645767e1b58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3072277 Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/master@{#911804}
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-3072277
branch
from
ba102c5
to
7c264e7
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.
These crashing tests were uncovered by clusterfuzz after I landed a
patch to use content-visibility in <details>. It turned out that all of
them could also reproduce the crash without the use of <details>, so
here they are.
Bug: 1236774
Change-Id: Ib44f6f8167929c90d4b78c6e153ad645767e1b58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3072277
Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#911804}