Bug 168162

Summary: Table cells with colspan containing block or inline with writing-mode vertical are too small/big
Product: WebKit Reporter: Michael Dayah <michael>
Component: TablesAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, fantasai.bugs, hyatt, mmaxfield, rniwa, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: BrowserCompat, InRadar
Version: Safari Technology Preview   
Hardware: Mac   
OS: macOS 10.12   
Bug Depends on: 65917    
Bug Blocks:    
Attachments:
Description Flags
Simple test case
none
Safari 15.6.1 differs from other browsers none

Michael Dayah
Reported 2017-02-10 22:51:18 PST
Created attachment 301247 [details] Simple test case Cells in a table that are 1) beneath a colspanned cell and 2) have writing-mode: vertical applied behave incorrectly in different ways depending on whether the element with writing-mode applied is block or inline. If the contained element is inline, the cell is stretched horizontally as if allocating space for the element if it were still horizontal. If the contained element is block, the element spills out of the table and into adjoining cells.
Attachments
Simple test case (759 bytes, text/html)
2017-02-10 22:51 PST, Michael Dayah 		no flags
Details
Safari 15.6.1 differs from other browsers (1.40 MB, image/png)
2022-08-18 10:06 PDT, Ahmad Saleem 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2017-02-15 09:12:33 PST
<rdar://problem/30535294>
Ahmad Saleem
Comment 2 2022-08-18 10:06:39 PDT
Created attachment 461715 [details] Safari 15.6.1 differs from other browsers I am able to reproduce this bug in Safari 15.6.1 on macOS 12.5.1 and as can be seen from attached screenshot, all other browsers render different and similar to each other. I tried Safari Technology Preview 151 and it still has same issue. Thanks!
fantasai
Comment 3 2025-06-04 12:59:02 PDT
I believe this is either a duplicate of, or blocked by, bug 65917.
Note You need to log in before you can comment on or make changes to this bug.