1445634 - linewrapping inside nested table cells with nowrap="nowrap" treated differently than Blink

Status: RESOLVED DUPLICATE of bug 221154

(Core :: Layout: Tables, defect)

Description

[Josh Matthews [:jdm]]

Visiting https://bugs.chromium.org/p/chromium/issues/detail?id=814100 in Firefox yields a long list of email addresses that cover up the actual page content. In Chrome, the addresses form rows of the table on the left side of the page instead. If I disable the `inline-block` property of the div elements that contain each address, Firefox displays the same as Chrome.

Comment 1

[Josh Matthews [:jdm]]

Attachment: Testcase

Here's a minimized testcase that demonstrates the issue.

Comment 2

[Daniel Holbert [:dholbert]]

Attachment: testcase 2

This is about "nowrap" on ancestor td elements. We honor it; chrome does not (though they only don't if the ancestor happens to have a specified width, regardless of what that width is).

Here's a testcase that demonstrates this. Chrome differs from us (and wraps the text) on the 3rd line.

Comment 3

[Daniel Holbert [:dholbert]]

Edge agrees with us on "testcase 2". I'm pretty sure that testcase (and the fact that Chrome is wrapping on the original page here) is a Chrome bug -- I'll file.

(As for the original page, Edge renders it like Firefox except that they clip the text rather than letting it overflow. I think that they're correct there -- our difference from Edgethere is covered by bug 221154.  Basically, we're not quite honoring "overflow-x:hidden" on the table cell.)

Comment 4

[Daniel Holbert [:dholbert]]

Filed https://bugs.chromium.org/p/chromium/issues/detail?id=821915.

Comment 5

[Daniel Holbert [:dholbert]]

Attachment: screenshot of how this bug looks, on chromium bug tracker

Comment 6

[Daniel Holbert [:dholbert]]

I filed https://bugs.chromium.org/p/monorail/issues/detail?id=3585 on fixing the bug tracker itself to avoid this problem (since they're including some markup and then inadvertently relying on the fact that Chrome/Safari ignores that markup, basically).

Comment 7

[Daniel Holbert [:dholbert]]

I'm just going to dupe this to bug 221154, since that's the Firefox bug that's coming into play here. (There's also some Tech Evang outreach to be done to fix the site, but that's basically covered by the bug I filed in comment 6.)

Comment 8

[Daniel Holbert [:dholbert]]

The monorail bug (from comment 6) has been fixed, so this issue is no longer reproducible at the live URL where jdm encountered it. (It's not reproducible there for me, anyway.)