Closed Bug 1746267 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 32089 - [wpt] Fix expectation of WPT test.

Categories

(Core :: Layout, task, P4)

Product:
Core
Component:
Layout
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
97 Branch
Tracking Flags:
Tracking Status
firefox97 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Ian Kilpatrick <ikilpatrick@chromium.org> wrote:

[wpt] Fix expectation of WPT test.

The test-expectation for:
css-sizing/table-child-percentage-height-with-border-box.html
is incorrect.

From:
https://github.com/web-platform-tests/wpt/pull/32026

Specifically it is incorrect about how table-cell children resolve their
percentages, as defined by:
https://drafts.csswg.org/css-tables-3/#table-cell-content-relayout

(it was asserting that content-box behaves as border-box for table-cell
children where the table-cell is auto height which is incorrect).

Bug: 1280198
Change-Id: I8d9e1f17a0e647425aeaa169f8849ba76df663a2
Reviewed-on: https://chromium-review.googlesource.com/3342920
WPT-Export-Revision: f74c79baf02c3e27c42b7cc5679095097a487df4

PR 32089 applied with additional changes from upstream: 815ddbc514cce543f78a47ff3c0fc18ac7979055
Component: web-platform-tests → Layout
Product: Testing → Core
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6f513f5091c8
[wpt PR 32089] - [wpt] Fix expectation of WPT test., a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/6f513f5091c8

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox97: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
You need to log in before you can comment on or make changes to this bug.