Closed
Bug 136598
Opened 23 years ago
Closed 23 years ago
Input text in fieldset with unminimized checked attribute appears outside box
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: peter, Assigned: rods)
Details
(Keywords: testcase)
Attachments
(1 file)
|
975 bytes,
text/html
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311
BuildID: 2002031104
When you put <input type="text"> fields into a fieldset that also has radio
buttons with an unminimized checked attribute (because of XHTML), the value
appears outside the box.
Reproducible: Always
Steps to Reproduce:
1. copy/paste the attached code
2. and view as a .htm page
3.
Actual Results: Text appears outside the textbox.
Expected Results: Text should appear inside the textbox.
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Input text value outside box</title>
</head>
<body>
<form id="form1" action="result.htm" method="get">
<!-- A few pointers: if you comment out the checked="checked"
in the above radio-button or the fieldset, the effect disappears.
Also, if you comment out the legend, the effect partially disappears.
//-->
<fieldset>
<legend>Legend</legend>
<p>Label:
<input id="one" type="radio" tabindex="6" value="one" name="foo" checked="checked"
/><label for="one">one</label>
<input id="two" type="radio" tabindex="7" value="two" name="foo" /><label
for="two">two</label>
</p>
<p>And look what happens here:
<input type="text" id="id" name="lin" maxlength="10" size="10" value="yowza!?" />
</p>
</fieldset>
</form>
</body>
</html>
|
||
Comment 1•23 years ago
|
||
|
|
||
Comment 2•23 years ago
|
||
WFM 2002040903/Win2K
Reporter, could you install the latest nightly build and try it again?
http://ftp.mozilla.org/pub/mozilla/nightly/latest/
Keywords: testcase
|
Reporter | |
Comment 3•23 years ago
|
||
I used the latest build (2002041003) and the problem indeed appears to be fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•