Closed Bug 1641377 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 23807 - [TablesNG] New test suite: colspan redistribution

Categories

(Core :: Layout: Tables, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla80
Tracking Status
firefox80 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Aleks Totic <atotic@chromium.org> wrote:

[TablesNG] New test suite: colspan redistribution

Investigation into how cells with colspan > 1
redistribute their min/max/% widths.

Browsers often disagree, and spec allows for variations.

Bug: 958381
Change-Id: I588053d1392e00e9d199cdd1095b93a148101fc4
Reviewed-on: https://chromium-review.googlesource.com/2219093
WPT-Export-Revision: a9555eab805bffc160c0eed37fa3660a6284f9ae

Component: web-platform-tests → Layout: Tables
Product: Testing → Core

CI Results

Ran 12 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 24 subtests

Status Summary

Firefox

OK : 1
PASS: 20
FAIL: 4

Chrome

OK : 1
PASS: 17
FAIL: 7

Safari

OK : 1
PASS: 17
FAIL: 7

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/css/css-tables/tentative/colspan-redistribution.html
table 12: FAIL (Chrome: PASS, Safari: FAIL)
table 22: FAIL (Chrome: FAIL, Safari: FAIL)
table 23: FAIL (Chrome: FAIL, Safari: FAIL)
table 24: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/64dc5d727b49
[wpt PR 23807] - [TablesNG] New test suite: colspan redistribution, a=testonly
https://hg.mozilla.org/integration/autoland/rev/09d53898d89a
[wpt PR 23807] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in before you can comment on or make changes to this bug.