Unable to set table column width on tables td's if a th exists

[stevenlaidlaw]

If a 'table > thead > tr > th' is set, weasy is not able to set the column widths on td's below it. This is a problem when trying to set widths on table columns where the table header has a colspan greater than 1.

Example:

<table>
    <thead> 
        <tr>
            <th colspan="2">The column width will not work in weasy</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>Hello</td>
            <td>Clarice</td>
        </tr>
    </tbody>
</table>

table > tbody > tr > td:first-child {
    width: 20%;
    text-align: left;
}

[SimonSapin]

I wouldn’t be surprised if we do colspan wrong in the automatic column width algorithm. @liZe does that ring a bell?

[liZe]

I think that percentages are not handled at all when no width is set to the table, even without colspans. I'll check that.

[SimonSapin]

http://dbaron.org/css/intrinsic/ describes algorithms we could implement to handle this kind of thing. At the moment, it’s the closest thing in existence to a spec of what browsers do.

[liZe]

Soooooo easyyyyyyyy!

[SimonSapin]

Of course. It’s just a small matter of programming :)

[stevenlaidlaw]

Apologies, I should have clarified that even with a table width of 100% and table-layout of fixed this still happens, but from what you've written in response it seems like you're onto it anyway. :)

[eldamir]

This is still a real pain. Any fix available?

I have a table with 6 columns, and each column has a width set, which looks great in Chrome, but with weasyprint, these widths are ignored, and all columns seem to be equally distributed 😦

[stevenlaidlaw]

I don't think anyone is working on Weasy anymore. The hacky workaround I use is just to have an invisible th row above the normal one, and hide all the margins, padding, borders, etc, then just set the widths on that. It's bad code, but it's what you have to do to get it working in Weasy :(

[liZe]

You can look at #291.

Your specific case is maybe the worst case for this algorithm (the width of the table is a too high, it's the same rendering as Chrome for example), but at least it takes care of the percentages. It's much better for other cases.

Feel free to tests and reports bugs!

[liZe]

@eldamir @stevenlaidlaw last call for tests! You can try #291 if you want.

[liZe]

@eldamir @stevenlaidlaw it's merged in master.