input form fields with type hidden sometimes display as empty text input fields in the page.

RESOLVED FIXED

Status

()

--
minor
RESOLVED FIXED
16 years ago
16 years ago

People

(Reporter: ventatsu, Unassigned)

Tracking

Other Branch
x86
Windows 98
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2) Gecko/20021126

If an input filed with type set to hidden is not preceded by either the body
open tag or text it will be displayed as a text field, but will not have it's
default value set.

Reproducible: Always

Steps to Reproduce:
1. Save the following in a file:
<html>
<form action="/listings/update.php" method=post>
<input type=hidden name=test1 value=value1> :test1<br>
test2: <input type=hidden name=test2 value=value2><br>
 </table>
</form>
</html>

2. Load the file in Mozilla

Actual Results:  
An empty text input field apears before the test ' :test1'


Expected Results:  
the field should have been hidden and kept its value.

Workarounds are trivial, the <body> tag or any text, even a period, prior to the
hidden input will cause it to behave normaly.

Comment 1

16 years ago
Build: Mozilla/5.0 (X11; U; Linux i686; rv:1.2) Gecko/20021126

This also happens with the above build.
This is 1.2-branch only.  See bug 182500.
Status: UNCONFIRMED → NEW
Component: Layout: Form Controls → Parser
Depends on: 182500
Ever confirmed: true
Version: Trunk → Other Branch

Comment 4

16 years ago
"input form fields with type hidden sometimes display as empty text input fields
in the page."

Yes when the page has no <BODY> tag.
I have tested that this bug was an instance of bug 182500 / bug 182253 based on
comparison of two Linux builds compiled with gcc 3.2.  This bug was present in
the 1.2 release and was the only bug fixed in the 1.2.1 release (and the reason
for the 1.2.1 release).

Marking this bug as fixed since it should be fixed in the 1.2.1 release.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.