370498 - style="table-layout:fixed" does not cut extreme long words

Status: RESOLVED INVALID

(Core :: Layout: Tables, defect)

Description

[Tobias Krais]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

Following example:
<table style="table-layout:fixed">
  <tr>
    <td width="100px">ContentAndContentAndContentAndContent
    </td>
  </tr>
</table>

In this example the table cell will be extreme long, although the specification of table-layout:fixed says that width="100px" should overbalance it. In this case, IE interprets it correctly.

Reproducible: Always

Steps to Reproduce:
See code above.
Actual Results:  
Table cell was too large.

Expected Results:  
Table cell should have a width of 100px

Comment 1

[Frank Wein [:mcsmurf]]

Reporter: You observed this bug with Firefox 2.0.0.1 right?

Somehow this bug here is the same as Bug 368600. But Bug 368600 was caused by the reflow branch landing, which did not affect FF 2...

Comment 2

[Bernd]

according to http://www.w3.org/TR/CSS21/tables.html#fixed-table-layout

The table's width may be specified explicitly with the 'width' property. A value of 'auto' (for both 'display: table' and 'display: inline-table') means use the automatic table layout algorithm. 

That is exactly what happens here. 

Microsoft did however lobby to get their behavior into the spec:

"However, if the table is a block-level table ('display: table') in normal flow, a UA may (but does not have to) use the algorithm of 10.3.3 to compute a width and apply fixed table layout even if the specified width is 'auto"

Comment 3

[Daniel.S]

Tobias, HTML width attributes don't know values like '100px', only numbers and percentages. You should work solely with CSS if possible.

Anyay, the table above is using the Automatic Table Layout Algorithm. Opera9 and Safari3.1 agree, and it looks like IE8 is going to agree as well.

There is no spec violation, so this is an Invalid bug.