Bug 269202

Summary: Nested multi-columns can cut off text
Product: WebKit Reporter: Brad Andalman <bya>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: bfulgham, bw, illenberger, karlcow, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: BrowserCompat, InRadar
Version: Safari 17   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
HTML exhibiting the bug (cut-off text)
none
Renders of the HTML in Safari (incorrect), Chrome (correct), and Firefox (correct) none

Brad Andalman
Reported 2024-02-12 09:38:07 PST
Created attachment 469828 [details] HTML exhibiting the bug (cut-off text) I have attached HTML with two nested multi-column layouts: the outer sets a specific `column-width` while the inner one sets the `column-count` to 2. The outer-column’s height is set so that it can’t fit two lines of text in one of its columns, which means that each number should appear in its own column. Instead, the text is cut off (in addition to being out-of-order: see bug #269197, which has a similar setup). Chrome and Firefox render this correctly.
Attachments
HTML exhibiting the bug (cut-off text) (1.17 KB, text/html)
2024-02-12 09:38 PST, Brad Andalman 		no flags
Details
Renders of the HTML in Safari (incorrect), Chrome (correct), and Firefox (correct) (251.99 KB, image/png)
2024-02-12 09:38 PST, Brad Andalman 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Brad Andalman
Comment 1 2024-02-12 09:38:45 PST
Created attachment 469829 [details] Renders of the HTML in Safari (incorrect), Chrome (correct), and Firefox (correct)
Karl Dubost
Comment 2 2024-02-14 17:14:11 PST
Thanks for the bug. Indeed. Maybe covered by one of these tests https://wpt.fyi/results/css/css-multicol?label=master&label=experimental&aligned&q=safari%3Afail%20firefox%3Apass%20chrome%3Apass
Radar WebKit Bug Importer
Comment 3 2024-02-14 17:14:20 PST
<rdar://problem/122982032>
Frank Illenberger
Comment 4 2025-11-11 23:01:47 PST
vote +1 from me
Note You need to log in before you can comment on or make changes to this bug.