Closed
Bug 79863
Opened 25 years ago
Closed 25 years ago
INPUT buttons with linefeeds in value break lines
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
People
(Reporter: SkewerMZ, Assigned: ian)
References
Details
(Keywords: html4, qawanted, testcase)
Attachments
(2 files)
What the buttons look like in NS4
Procedure: View the testcase.
Expected: These buttons should all be rendered on one line with spaces for the
line breaks. This is especially true for the HTML 4 BUTTON element.
According to the W3C HTML 4.01 specification, the VALUE property of the INPUT
element uses the CDATA format, which states that user agents must "ignore line
feeds" and "replace each carriage return or tab with a single space."
Actual: Carriage-return, linefeed characters are rendered as line breaks within
the button.
Build: 20010508 Win98
Adding 4xp since this particular behavior doesn't happen in Communicator 4.73,
submit and reset behave as expected and button inserts unsupported-character blocks.
This behavior is incorrect according to the HTML 4.01 specification, adding
html4 keyword. I don't really want to start another but about this, but
shouldn't the BUTTON tag be rendered as a block element (i.e., implied linebreak
before and after)? I didn't see anything about it in the spec, but that is how
IE5.5 treats it.
Unconfirmed after three days, qawanted...
Keywords: qawanted
Component was: Parser
Title was: Buttons with linefeeds in value break lines
This bug is not a duplicate of bug 55285, but the problems with the HTML 4
BUTTON element are described more completely in that bug. This bug deals with
the INPUT element whose TYPE property is set to either submit, reset, or button.
Component: Parser → HTML Form Controls
Summary: Buttons with linefeeds in value break lines → INPUT buttons with linefeeds in value break lines
|
||
Comment 8•25 years ago
|
||
assigning to hixie. I would say this will be fixed by bug 55285 being fixed --
all the elements in question are constructed in the exact same way.
Ian, what do you think?
|
Assignee | |
Comment 9•25 years ago
|
||
*** This bug has been marked as a duplicate of 55285 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
|
|
Reporter | |
Comment 10•25 years ago
|
||
Verify to clear my list of resolved bugs.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•