Closed
Bug 3374
Opened 26 years ago
Closed 26 years ago
script element is not processed when nested
Categories
(Core :: XUL, defect, P1)
Tracking
()
VERIFIED
FIXED
People
(Reporter: rubydoo123, Assigned: karnaze)
Details
build: 2/26/99
other platforms: winNT, mac, linux
expected results: when display the file within app, the dynamically generated
select list should have option elements display in the drop down list.
what happened: the option elements were listed outside of the seelct box
boundaries.
steps to reproduce: copy the following code into a local file, save the file and
display within the app. The select box within the form is not processed
correctly, the option elements are listed outside of the select element
boundaries.
<HTML>
<HEAD>
<TITLE>Step Load</TITLE>
<SCRIPT LANGUAGE="JavaScript">
var urlChoice // index of the currently selected URL
var winArray =
[
"http://www.zdnet.com",
"http://www.auctionuniverse.com",
"http://www.classifieds2000.com",
"http://www.ebay.com",
"http://www.onsale.com",
"http://www.monster.com",
"http://talk.excite.com",
"http://www.icq.com",
"http://www.talkcity.com",
"http://www.tripod.com",
"http://dailynews.yahoo.com",
"http://www.buycomp.com",
"http://www.chumbo.com"
]
</SCRIPT>
</HEAD>
<BODY>
<p>There are <script
language="javascript">document.write(winArray.length);</script> URL's in this
test suite.</p>
<FORM NAME="Myform">
URL Select List:<BR>
<SELECT NAME="select1" onchange="Go(this.form)">
<SCRIPT language="javascript">
document.write ('<OPTION>pick a URL');
for (i = 0; i < winArray.length; i++)
{
value = winArray[i];
document.write('<option>' + value);
}
document.write ('</SELECT>');
</script>
<br>
</FORM>
</BODY>
</HTML>
|
Reporter | |
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
|
|
Reporter | |
Comment 2•26 years ago
|
||
using the 3/4 build, using apprunner - this now renders correctly, marking
fixed/verified -- something must have gotten checked in in the last couple of
days.
|
|
Reporter | |
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•