Closed Bug 1714736 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 29199 - [TablesNG] Fix box-sizing width

Categories

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

task

Tracking

()

RESOLVED FIXED
91 Branch
Tracking Status
firefox91 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

b'Aleks Totic <atotic@chromium.org>' wrote:

[TablesNG] Fix box-sizing width

TD could specify width \< border_padding.
TD's width must be >= border_padding.

Bug: 1215846
Change-Id: I2b00c76fabc5d0333bede08a445561a172b0c593
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2936330
Reviewed-by: Ian Kilpatrick \<ikilpatrick@chromium.org>
Commit-Queue: Aleks Totic \<atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#889092}

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

CI Results

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

Total 1 tests and 11 subtests

Status Summary

Firefox

OK : 1
PASS: 9
FAIL: 2

Chrome

OK : 1
PASS: 10
FAIL: 1

Safari

OK : 1
PASS: 11

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

/css/css-tables/tentative/td-box-sizing-003.html
table 9: FAIL linked bug:Bug 1710799
table 10: FAIL

New Tests That Don't Pass

/css/css-tables/tentative/td-box-sizing-003.html
table 9: FAIL (Chrome: PASS, Safari: PASS)
table 10: FAIL (Chrome: PASS, Safari: PASS)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fe7ffbde8506
[wpt PR 29199] - [TablesNG] Fix box-sizing width, a=testonly
https://hg.mozilla.org/integration/autoland/rev/eaffdff0effa
[wpt PR 29199] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.