265259 - trailing whitespace entities are stripped of input value= attributes

Status: RESOLVED EXPIRED

(Core :: DOM: HTML Parser, defect)

Description

[Julien Plissonneau Duquène]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040820 Debian/1.7.2-4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040820 Debian/1.7.2-4

The HTML parser of Mozilla removes whitespace from attribute values, even when
the whitespace is encoded as entities, e.g. in

<input type="hidden" value="&#10;&#10;test 3&#10;here&#10;&#10;" name="h2">

What actually happens is that the newline between "test 3" and "here" is kept,
but all others are discarded. When tested with IE5 or IE6, all newlines are kept.

The expected result is that trailing whitespace, when transmitted in entity
form, is kept. IE always keep whitespace even in raw form.

This is not tooltip-related (and thus not a dupe of bug 67127).
I have just been told that this is not a dupe of bug 228099.

It causes real problems with ECMAscript apps that deal with textareas and
preformatted text stored passed in <input type="hidden"> elements. I had to work
around it using <pre> and more script.

See attached testcase, in which "test 3" does not work as expected. Both "test
2" and "test 3" keep the trailing newlines on IE.


Reproducible: Always
Steps to Reproduce:

Comment 1

[Julien Plissonneau Duquène]

Attachment: testcase for newline entities in value= attribute of input element in HTML

Comment 2

[Boris Zbarsky [:bzbarsky]]

Stripping the whitespace doesn't happen in the parser; it happens in the content
sink.  By that point, the entities have long since been converted to their
string representations.

I suspect this is wontfix...

Comment 3

[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 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.