ASSIGNED 100279
Wrong column widths when a row has colspan and long unwrappable text and other rows cells width is specified with percentage
https://bugs.webkit.org/show_bug.cgi?id=100279
Summary Wrong column widths when a row has colspan and long unwrappable text and othe...
Nicolás Cardelino
Reported 2012-10-24 12:24:52 PDT
Created attachment 170446 [details] Last row cell with colspan=2 If the last row of a table has colspan > 1 and contains a long unwrapped text, and the width of the first cell of previous rows is specified using percentage (for example 10%), those previous cells ignore the width and take 50% instead. Given a 3 row table, with 2 columns where the last row has colspan = 2, and the first cell of the first 2 rows width is 10%, instead of this: 10% *--*------------------* *--*------------------* *---------------------* you get this: *----------*----------* *----------*----------* *---------------------*
Attachments
Last row cell with colspan=2 (610 bytes, text/html)
2012-10-24 12:24 PDT, Nicolás Cardelino
no flags
Last row cell with colspan=2 (599 bytes, text/html)
2012-10-24 12:33 PDT, Nicolás Cardelino
no flags
nowrap (474 bytes, text/html)
2013-05-06 01:51 PDT, zalan
no flags
Nicolás Cardelino
Comment 1 2012-10-24 12:33:23 PDT
Created attachment 170449 [details] Last row cell with colspan=2
zalan
Comment 2 2013-05-06 01:51:46 PDT
Created attachment 200647 [details] nowrap Both Opera and Firefox disagree with WebKit rendering.
zalan
Comment 3 2013-05-06 03:25:41 PDT
<tr><td style="width:90%;"></td><td></td></tr> <tr><td colspan="2"></td></tr> in AutoTableLayout::calcEffectiveLogicalWidth(), we ignore the percent value, when the min/max column widths are calculated (colspan is present). The second column's auto width value negates the percentage value so the available width distribution is based on the cell's content width instead. Shouldn't we do something like if (percent and auto columns only) distribute (100-percent) across the auto columns and go ahead with the 'allColsArePercent' calculation?
Note You need to log in before you can comment on or make changes to this bug.