Closed Bug 22707 Opened 25 years ago Closed 24 years ago

Inside hidden INPUTs stored newlines (\n) are converted to whitespaces

Categories

(Core :: DOM: Core & HTML, defect, P3)

x86
Other
defect

Tracking

()

VERIFIED INVALID
Future

People

(Reporter: andre, Assigned: pollmann)

References

()

Details

Enter something in "Titel,Pseudo,Personen", a valid email Address in "eMail", and the following text in "Text": "test test test test test test test test test" Then press "Eintragen", the entry will be previewed (correctly), on the next page press "Konsumtechnik jetzt eintragen!", Mozilla then submits everything again, but without correct Newlines (\n), as one can see at the following page It´s no PHP programming fault, because it works using IE4.x and NS 4.7
Assignee: karnaze → pollmann
Reassigning to Eric.
Whiteboard: [MAKINGTEST] noid@pcisys.net
Whiteboard: [MAKINGTEST] noid@pcisys.net
on testing if bug is still present, mozilla crashed it entered something into the fields, previewed it, went back, changed something, submitted agin, mozilla crashed tested on win2000en, mozilla build 2000020414
I'm actually seeing the newlines being stripped, not even converted to spaces.
See related bug 22983. Thanks davidr8@home.com for catching the relationship.
Status: NEW → ASSIGNED
*** Bug 34872 has been marked as a duplicate of this bug. ***
Somehow my memory is that the type of whitespace within attribute values should not be significant, although I'm not sure...
Setting milestone to M18
Target Milestone: --- → M18
This is what HTML4 spec says about the contents of CDATA attributes such as value, alt, title, href, longdesc...: # CDATA is a sequence of characters from the document character set and # may include character entities. User agents should interpret attribute # values as follows: # o Replace character entities with characters, # o Ignore line feeds, # o Replace each carriage return or tab with a single space. # User agents may ignore leading and trailing white space in CDATA attribute # values (e.g., " myval " may be interpreted as "myval"). -- http://www.w3.org/TR/REC-html40/types.html#h-6.2 See bug 2756. What we are doing is almost certainly correct, except if CRLF pairs (also known as "\r\n") are being ignored altogether instead of being turned into a single linear whitespace character (" ", the space). davidr8@home.com, could you confirm your comment of 2000-02-25 22:43? I am marking this bug INVALID, it should be reopened if you are correct and CRLF pairs are being dropped altogether (not converted to whitespace).
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Yeah, that's still happening.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Status: REOPENED → ASSIGNED
*** Bug 29677 has been marked as a duplicate of this bug. ***
*** Bug 32868 has been marked as a duplicate of this bug. ***
Note to self: Be sure to test Bug 32868 when fixing this bug. Server side may also be sensitive to \r\n vs. \n. Nav only sent \n for that case (guess that's what it receives. We would convert \n to \r\n currently...
*** Bug 40827 has been marked as a duplicate of this bug. ***
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Target Milestone: M18 → Future
Per my comments dated 2000-04-10 18:15, marking INVALID. I have filed bug 47078 for the newline stripping issue.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → INVALID
Updating QA contact.
QA Contact: ckritzer → vladimire
Verifying
Status: RESOLVED → VERIFIED
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.