Bug 13080 – Quirk: Non-breaking spaces next to an image should not provide a line-breaking opportunity within a table cell

• Component: Layout and Rendering
• Status: RESOLVED FIXED

[David Kilzer (:ddkilzer)]

Summary:

Non-breaking spaces (&nbsp; or \uC2A0 in UTF-8) around <img> tags within <td> tags are not collapsed when rendered in Safari.

Steps to reproduce:

1. Open Safari/WebKit.
2. Open one of the two test cases.

Expected results:

The non-breaking spaces should be collapsed so that the test cases look the same in Safari/WebKit as they do in Firefox 2.0.0.2.

Actual results:

The non-breaking spaces are not collapsed, causing the test cases to render incorrectly.

Regression:

Shipping Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8L127) renders the test cases incorrectly, so this is not a regression.

Tested with a local debug build of WebKit r20211 with the above software.

Note:

Non-breaking spaces in this situation are collapsed when rendered in Firefox 2.0.0.2 and Opera 9.10.  MSIE 6/7 have not been tested.  Mac IE 5.2.3 does not collapse the non-breaking spaces like Safari.

[David Kilzer (:ddkilzer)]

Created attachment 13645 [details]
Test case (using  )

[David Kilzer (:ddkilzer)]

Created attachment 13646 [details]
Test case (using utf-8 \uC2A0)

In standards mode, Firefox behaves like WebKit.

Actually, in Firefox's rendering, the spaces aren't collapsed, they just don't provide a line breaking opportunity.

This bug means that there's still some craziness missing from the implementation in  <http://trac.webkit.org/projects/webkit/changeset/19342> of the crazy Firefox/Opera quirk.

See attachment 12778 [details] and attachment 12779 [details] for the full extent(?) of the quirk in Firefox and WinIE.

[David Kilzer (:ddkilzer)]

Note that this was originally seen on automated search email sent by eBay.

I can provide the email message (which renders incorrectly in Mail 2.1 (752/752.2) on Mac OS X 10.4.8 (8L127)) as well if that would be helpful.

[Robert Hogan]

WebKit renders the test cases the same as FF22 and Opera presto. So this isn't a bug anymore I think.