Bug 285415

Summary: colspan=0 and rowspan=0 do not behave the same way for rendering in all browsers
Product: WebKit Reporter: Karl Dubost <karlcow>
Component: TablesAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: dholbert, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
URL: https://codepen.io/webcompat/pen/dPbJGbm
See Also: https://bugs.webkit.org/show_bug.cgi?id=285414
Bug Depends on: 185341    
Bug Blocks:    
Attachments:
Description Flags
rendering in safari, firefox, chrome
none
rendering in safari, firefox, chrome none

Karl Dubost
Reported 2025-01-06 00:19:12 PST
This is not really a bug on WebKit as this is happening on all browsers. It is more a rendering difference in between colspan and rowspan. <b>simple table width border=1 / colspan=0</b> <table border="1"> <tr><td colspan="0">A1</td></tr> <tr><td>B1</td><td>B2</td><td>B3</td></tr> <tr><td>C1</td><td>C2</td><td>C3</td></tr> </table> The cell rendering of A1 doesn't spread on all cells like it would do for colspan=3 rowspan=0 creates a joint space in both firefox/chrome (and in webkit after https://github.com/WebKit/WebKit/pull/38398) which is identical to a rowspan=n for a table of n rows. On the other hand, colspan=0 is weird. It creates a square cell but doesn't really span it, it just removes the space remaining. To see the difference of behavior in Safari, we need to wait the landing of Bug 185341
Attachments
rendering in safari, firefox, chrome (223.33 KB, image/png)
2025-01-06 00:41 PST, Karl Dubost
no flags
rendering in safari, firefox, chrome (281.67 KB, image/png)
2025-01-06 00:47 PST, Karl Dubost
no flags
Karl Dubost
Comment 1 2025-01-06 00:41:37 PST
Created attachment 473792 [details] rendering in safari, firefox, chrome Probably more visible with this test. https://codepen.io/webcompat/pen/EaYoPWb we can see than 1. in the case of rowspan, the A letters are distributed for the full height of the table, 2. while in the case of the colspan it is not using the full width of the table. Again the current rendering on Safari is wrong because of Bug 185341
Karl Dubost
Comment 2 2025-01-06 00:47:04 PST
Created attachment 473793 [details] rendering in safari, firefox, chrome Added a colspan=3 to show how it should behave. Probably WPT tests are needed, depending on what we think is the right behavior.
Radar WebKit Bug Importer
Comment 3 2025-01-13 00:20:14 PST
Note You need to log in before you can comment on or make changes to this bug.