If I have horizontal padding on TD's (eg. "td {padding: 0 25px;}"), this padding is apparently ignored when determining column widths in a table with "table-layout: fixed". If a td has "width: 5px" that column will be 5px wide total (instead of the correct 55px wide - including padding) even though the contents of the column ARE displaced correctly by the 25px padding - and thus overflows into the next columns.
Created attachment 14017 [details] A tescase for this bug A testcase, showing both the erroneous and correct way to display the described table...
Created attachment 22124 [details] second testcase, CSS-table A second testcase. CSS-table with a fixed width of 200px. table-layout: fixed left: table cell width:100px, right: table cell width:50px and padding-left:50px webkit does not calculate the width correctly. It distributes the remaining space of the table among the cells, causing a wide left cell (100px+34px) and a smaller right cell (50px+16px).
Suspected duplicate of bug 18565.
(In reply to comment #3) > Suspected duplicate of bug 18565. They might be related, but this bug is about width of padding is not corrected added to the specified width of the table column.
(In reply to comment #4) > (In reply to comment #3) > > Suspected duplicate of bug 18565. > > They might be related, but this bug is about width of padding is not corrected added to the specified width of the table column. Sorry I meant this bug seems not the same as bug 17583. It's in deed very related to bug 18565.
Still reproducible in 535.8 (Chrome 17.0.963.2).
This is because <td>s stubbornly use border-box mode, see bug 18565 comment 9. Since bug 18565 has more information about this problem, bug 13339 should be made duplicate thereof. Unfortunately neither of these bug reports have been marked as confirmed by the WebKit team.
It seems that fix for bug 78412 fixed this one, too. The above testcases work fine for me in Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1085.0 Safari/536.5
*** This bug has been marked as a duplicate of bug 78412 ***