Closed Bug 1819313 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 38740 - Don't exceed max-block-size when encompassing intrinsic block-size.

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
113 Branch
Tracking Status
firefox113 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Morten Stenshorne <mstensho@chromium.org> wrote:

Don't exceed max-block-size when encompassing intrinsic block-size.

If the constraint space has been set up for min-block-size to encompass
intrinsic block-size, don't let it exceed computed max-block-size.

Bug: 1417976
Change-Id: I8f7d381a9c8611c58819ae3331afbf48b8d484b6
Reviewed-on: https://chromium-review.googlesource.com/4295426
WPT-Export-Revision: dffc098067f8ecf1d35ceb7ff15514928f588e91

Component: web-platform-tests → Layout
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

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

Total 2 tests

Status Summary

Firefox

PASS: 2

Chrome

FAIL: 2

Safari

FAIL: 2

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3302b781bd1f [wpt PR 38740] - Don't exceed max-block-size when encompassing intrinsic block-size., a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in before you can comment on or make changes to this bug.