Closed Bug 1797250 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 36642 - Write column-count back to legacy correctly.

Categories

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

task

Tracking

()

RESOLVED FIXED
108 Branch
Tracking Status
firefox108 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Morten Stenshorne <mstensho@chromium.org> wrote:

Write column-count back to legacy correctly.

Column-count was written back to legacy by resolving it separately after
actual layout. At this point we don't have the information we need - the
content box inline-size. We were actually passing the available
inline-size from the containing block instead, which is wrong (unless
the content-box inline-size of the multicol container happens to be
identical to the containing block inline-size), and worse: it could be
indefinite, which may be the case if the multicol container is a grid
item. We'd end up with both division by zero and correctness issues.

It's much better to write column-count back during actual multicol
layout, just like we already do for column inline-size.

Bug: 1349884
Change-Id: I6ab3f13bc3bc3f47bda12bf9c54f1bb1171ffda4
Reviewed-on: https://chromium-review.googlesource.com/3970622
WPT-Export-Revision: 8b60ac4f6e5222168e486bb2a3558c817d93a32d

Component: web-platform-tests → Layout: Columns
Product: Testing → Core
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0e7b6b5495aa
[wpt PR 36642] - Write column-count back to legacy correctly., a=testonly
https://hg.mozilla.org/integration/autoland/rev/2e2642db0151
[wpt PR 36642] - Update wpt metadata, a=testonly
Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in before you can comment on or make changes to this bug.