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

[wpt] Add tests for two grid issues. #30703

Merged
merged 1 commit into from Sep 14, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Sep 13, 2021

Bug: 1111799, 1127715
Change-Id: I9de52b03ff6fe087bde18072c9f29dc437d43b50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3158852
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Daniel Libby <dlibby@microsoft.com>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#920986}

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.

Bug: 1111799, 1127715
Change-Id: I9de52b03ff6fe087bde18072c9f29dc437d43b50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3158852
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Daniel Libby <dlibby@microsoft.com>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#920986}
@chromium-wpt-export-bot chromium-wpt-export-bot merged commit ea28b33 into master Sep 14, 2021
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-3158852 branch September 14, 2021 00:09
servo-wpt-sync pushed a commit to servo-wpt-sync/web-platform-tests that referenced this pull request Nov 16, 2023
We previously sent a " " to the linebreaker in order to ensure that the
next text had a soft wrap opportunity at the start. Calling `next(" ")`
without waiting until the returned index was 1, violated some
invariants of linebreaker ultimately causing a panic.

Instead of using the linebreaker for this, simply keep a flag in the
IFC layout state, which avoids the problem entirely.

Fixes web-platform-tests#30703.
servo-wpt-sync pushed a commit to servo-wpt-sync/web-platform-tests that referenced this pull request Nov 16, 2023
We previously sent a " " to the linebreaker in order to ensure that the
next text had a soft wrap opportunity at the start. Calling `next(" ")`
without waiting until the returned index was 1, violated some
invariants of linebreaker ultimately causing a panic.

Instead of using the linebreaker for this, simply keep a flag in the
IFC layout state, which avoids the problem entirely.

Fixes web-platform-tests#30703.
servo-wpt-sync pushed a commit to servo-wpt-sync/web-platform-tests that referenced this pull request Nov 16, 2023
We previously sent a " " to the linebreaker in order to ensure that the
next text had a soft wrap opportunity at the start. Calling `next(" ")`
without waiting until the returned index was 1, violated some
invariants of linebreaker ultimately causing a panic.

Instead of using the linebreaker for this, simply keep a flag in the
IFC layout state, which avoids the problem entirely.

Fixes web-platform-tests#30703.
servo-wpt-sync pushed a commit to servo-wpt-sync/web-platform-tests that referenced this pull request Nov 16, 2023
We previously sent a " " to the linebreaker in order to ensure that the
next text had a soft wrap opportunity at the start. Calling `next(" ")`
without waiting until the returned index was 1, violated some
invariants of linebreaker ultimately causing a panic.

Instead of using the linebreaker for this, simply keep a flag in the
IFC layout state, which avoids the problem entirely.

Fixes web-platform-tests#30703.
servo-wpt-sync pushed a commit to servo-wpt-sync/web-platform-tests that referenced this pull request Nov 20, 2023
We previously sent a " " to the linebreaker in order to ensure that the
next text had a soft wrap opportunity at the start. Calling `next(" ")`
without waiting until the returned index was 1, violated some
invariants of linebreaker ultimately causing a panic. This change
ensures that `next(" ")` is called until the entire string is processed.

Fixes web-platform-tests#30703.
servo-wpt-sync pushed a commit to servo-wpt-sync/web-platform-tests that referenced this pull request Nov 20, 2023
We previously sent a " " to the linebreaker in order to ensure that the
next text had a soft wrap opportunity at the start. Calling `next(" ")`
without waiting until the returned index was 1, violated some
invariants of linebreaker ultimately causing a panic. This change
ensures that `next(" ")` is called until the entire string is processed.

Fixes web-platform-tests#30703.
servo-wpt-sync pushed a commit to servo-wpt-sync/web-platform-tests that referenced this pull request Nov 28, 2023
We previously sent a " " to the linebreaker in order to ensure that the
next text had a soft wrap opportunity at the start. Calling `next(" ")`
without waiting until the returned index was 1, violated some
invariants of linebreaker ultimately causing a panic.

Instead of using the linebreaker for this, simply keep a flag in the
IFC layout state, which avoids the problem entirely.

Fixes web-platform-tests#30703.
servo-wpt-sync pushed a commit to servo-wpt-sync/web-platform-tests that referenced this pull request Nov 28, 2023
We previously sent a " " to the linebreaker in order to ensure that the
next text had a soft wrap opportunity at the start. Calling `next(" ")`
without waiting until the returned index was 1, violated some
invariants of linebreaker ultimately causing a panic.

Instead of using the linebreaker for this, simply keep a flag in the
IFC layout state, which avoids the problem entirely.

Fixes web-platform-tests#30703.
servo-wpt-sync pushed a commit that referenced this pull request Nov 30, 2023
We previously sent a " " to the linebreaker in order to ensure that the
next text had a soft wrap opportunity at the start. Calling `next(" ")`
without waiting until the returned index was 1, violated some
invariants of linebreaker ultimately causing a panic.

Instead of using the linebreaker for this, simply keep a flag in the
IFC layout state, which avoids the problem entirely.

Fixes #30703.
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.

None yet

3 participants