Bug 45138

Summary: Incorrect intrinsic width with columns
Product: WebKit Reporter: Erik Arvidsson <arv>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: ahmad.saleem792, bfulgham, dglazkov, mstensho, priyajeet.hora, slightlyoff, webkit-bug-importer
Priority: P2 Keywords: HasReduction, InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Test case none

Description Erik Arvidsson 2010-09-02 15:37:21 PDT
Created attachment 66422 [details]
Test case

When an element has column-width and it needs to have its width set to the intrinsic width (using absolute pos, floats or width: intrinsic) the width is not correct.

In the test case, all the columns should have white background.
Comment 1 Morten Stenshorne 2013-05-23 02:14:42 PDT
While the exact behavior isn't described in any final spec yet, there's common sense and also the following ED to guide us: http://dev.w3.org/csswg/css-sizing/#multicol-intrinsic

I think the particular test case in this bug report will be tricky to fix, since it's about finding "the max-content measure of a multi-column element with restrained-height columns". The spec suggests that we need to perform a layout pass to get that measure, and currently WebKit doesn't do that when calculating intrinsic widths.

I have some changes in this area (but they currently only cover the cases where column-count is non-auto) that I'd like to submit, but since I probably won't manage to make the test case in this bug pass, I suppose I'd better open a new bug.
Comment 2 Morten Stenshorne 2013-05-23 08:42:35 PDT
Bug 116677 reported, with patch.
Comment 3 Brent Fulgham 2022-07-12 13:34:34 PDT
No two browsers seem to agree on behavior here. Safari and Chrome are close (though Chrome clips more than Safari. Firefox is the most different.
Comment 4 Radar WebKit Bug Importer 2022-07-12 13:35:01 PDT
<rdar://problem/96907406>
Comment 5 Ahmad Saleem 2023-02-22 04:14:12 PST
Is this will be fixed by bug 116677?

As mentioned in below Chromium bug?

https://bugs.chromium.org/p/chromium/issues/detail?id=54626