Bug 11630 – REGRESSION (r17068): Layout goes completely wrong

• Component: Layout and Rendering
• Status: RESOLVED INVALID

[Thomas Engelmeier]

The content DIV is rendered far too wide. 

The rendering is a regression compared to the shipping Safari variant, and works in Opera, Firefox, and Windows IE6 and 7.
Sorry, I am not enough a Webdesigner to strip it down, but the CSS & structure is already as easy as possible.
The only "formal" bug is that the Webserver supplies the html as "ISO-Latin-xxxx" but the xhtml states UTF-8 encoding.

Created attachment 11551 [details]
Reduction

Opera agrees with TOT. Results are the same in strict mode.

The regression was in r17068 (fix for bug 9347). Based on the description of that bug, I think the new result is correct (making this bug invalid).

Created attachment 11590 [details]
Text-transform eating up non-breaking space reduction

"Completely wrong" in the bug summary may refer to the popup being on the right of the menu instead of under it. In that case, this is because of a text-transform: capitalize regression demonstrated here. In shipping Safari, Firefox and Opera, there's a space between the two 100x100 squares due to the text which includes non-breaking spaces. This is also the case in TOT if text-transform:capitalize is not specified.

From StringImpl::capitalize:
        // Replace &nbsp with a real space since ICU no longer treats &nbsp as a word separator.

This was added in r13702 to address <rdar://problem/4502311> text-transform:capitalize needs to 
treat nbsp as a regular space when ICU changes.

I think the solution might be as simple as copying from m_data[i - 1] instead of stringWithPrevious[i] in the loop that copies the non-capitalized characters.

[Thomas Engelmeier]

Actually I meant the first reduction which - after reading a bunch of the CSS 2.1 spec - seems to be rendered correct - the second problem I considered more an cosemtic side-effect.

Seriously, I did not expect for "absolute" positioning the viewport and not the (html or body) parent objects are to consider for positioning. 

Thanks for the promt response and reductions. 

Closing this bug as invalid. Opened bug 11671 to track the text-transform: capitalize issue. Sorry for the mess.