Closed
Bug 5231
Opened 26 years ago
Closed 26 years ago
onchange() event firing incorrectly for Select elements
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
People
(Reporter: zaw, Assigned: pollmann)
References
()
Details
Mozilla build # 1999041412 = M4
javascript below a pulldown menu from GMC website act weird. Start loading links
as soon as you pull the menu down.
<SCRIPT LANGUAGE="JavaScript">
//<!--
NAV = 0;
version = navigator.appVersion;
if (navigator.appName == "Netscape") {
if (version.substring(0,3) >= "4.0"){NAV = 1;} else
if (version.substring(0,3) >= "3.0"){NAV = 1;}
}
else if (navigator.appName == "Microsoft Internet Explorer") {
if (version.substring(0,3) >= "4.0"){NAV = 1;}
}
else {NAV=0;}
function switch_page() {
if(NAV == 1) {
if (document.menuform.jumppage.selectedIndex == 0) location =
'/99vehicles.html';
else if (document.menuform.jumppage.selectedIndex == 1) location =
'/denali/';
else if (document.menuform.jumppage.selectedIndex == 2) location =
'/yukonsub/';
else if (document.menuform.jumppage.selectedIndex == 3) location =
'/envoy/';
else if (document.menuform.jumppage.selectedIndex == 4) location =
'/jimmy/';
else if (document.menuform.jumppage.selectedIndex == 5) location =
'/sierra/';
else if (document.menuform.jumppage.selectedIndex == 6) location =
'/sonoma/';
else if (document.menuform.jumppage.selectedIndex == 7) location =
'/savana/';
else if (document.menuform.jumppage.selectedIndex == 8) location =
'/safari/';
}
}
//-->
Updated•26 years ago
|
Assignee: norris → vidur
Component: JavaScript → DOM Level 0
Updated•26 years ago
|
Assignee: vidur → pollmann
Summary: onchange() event firing incorrectly for Select elements
Comment 1•26 years ago
|
||
The bug seems to be that the onchange() event doesn't fire the first time we
modify the select element. It fires as soon as we next touch the select element.
So, it is actually firing, but a bit too late.
Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Updated•26 years ago
|
Status: RESOLVED → CLOSED
You need to log in
before you can comment on or make changes to this bug.
Description
•