265974 - nbsp is ignored when between text and input element in table cell

Status: RESOLVED INVALID

(Core :: Layout: Form Controls, defect)

Description

[Douglas Richardson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

In the page at http://lbcf.org/test/nbsp.html, the button in the table cell is
separated from SHOULDNOTWRAP by a non breaking space (nbsp). However, if you
resize the browser window smaller, you will notice that the button is wrapped
before SHOULDNOTWRAP.

Reproducible: Always
Steps to Reproduce:
1. Go to http://lbcf.org/test/nbsp.html
2. Slowly resize your browser window smaller

Actual Results:  
Button1 is wrapped without SHOULDNOTWRAP.

Expected Results:  
Button1 should have been wrapped with SHOULDNOTWRAP.

Comment 1

[Bernd]

this is a linewrap issue similiar to bug 139723

Comment 2

[Uri Bernstein]

- This happens also with no table.
- This happens also with no &nbsp; (SHOULDNOTWRAP<input value="Button1"
type="button">). Is the &nbsp; supposed to be more "non-braking" than a regular
character, such as "P"?
- This seems very similar to bug 231644 (which, like this one, does involve a
table and an &nbsp;, but doesn't necessarily have to).
- See also bug 210351, which uses checkboxes instead of input, and no tables,
but is otherwise similar.

I think all of this revolves around the question whether the point between a
control and a non-breakable character is "breakable". Mozilla assumes it is.

Comment 3

[Uri Bernstein]

Attachment: original testcase from URL

Comment 4

[Uri Bernstein]

Attachment: same thing, without the table

Comment 5

[Uri Bernstein]

Attachment: same as original, without  

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Boris Zbarsky [:bzbarsky]]

This is basically the same as bug 139723.

Comment 8

[Jonathan Kew [:jfkthame]]

The CSS Text spec says that:

The line breaking behavior of a replaced element or other atomic inline is equivalent to an ideographic character (Unicode linebreaking class ID [UAX14]), and additionally, for Web-compatibility, introduces a soft wrap opportunity between itself and any adjacent U+00A0 NO-BREAK SPACE character.

I believe the <button> here is an atomic inline, and therefore according to the spec requirement "for Web-compatibility", there is a soft wrap opportunity there.

So unless the spec changes, this looks invalid.