Closed Bug 1595069 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 20175 - [css-text] Fix test and update TestEpectations

Categories

(Core :: Layout: Text and Fonts, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla72
Tracking Status
firefox72 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 20175 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/20175
Details from upstream follow.

Javier Fernandez <jfernandez@igalia.com> wrote:

[css-text] Fix test and update TestEpectations

The test word-break-break-all-inline-006.html is incorrectly defined, as
it was agreed in the corresponding CSS WG issue [1].

This CL changes the expected result of the test and updates the
TestExpectations accordingly, since it was failing for LayoutNG before.

The new expected result matches current LayoutNG's and Gecko's behavior,
but it implies that i fails in legacy and WebKit.

Change-Id: Ia31c89f1a4084607fbb29fd0422354b754a092d2
Reviewed-on: https://chromium-review.googlesource.com/1905549
WPT-Export-Revision: f80c6aa2db926686b00372b8175b5758a93c6574

Component: web-platform-tests → Layout: Text and Fonts
Product: Testing → Core
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

GitHub CI Results

wpt.fyi PR Results Base Results

Ran 1 tests

Firefox

PASS: 1

Chrome

PASS: 1

Safari

FAIL: 1

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/eef2b7b1e4c4
[wpt PR 20175] - [css-text] Fix test and update TestEpectations, a=testonly
https://hg.mozilla.org/integration/autoland/rev/774f6f4ddf72
[wpt PR 20175] - Update wpt metadata, a=testonly
Status: REOPENED → RESOLVED
Closed: 1 year ago1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.