Closed Bug 97004 Opened 23 years ago Closed 23 years ago

onChange() not called after <SELECT> option is selected, unselected, selected

Categories

(Core :: Layout: Form Controls, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: kiko, Assigned: rods)

References

()

Details

(Keywords: dom0)

On any bugzilla (I posted ours because the few products we have make repaints much faster) installation, the following bug can be reproduced: a) Click on First item in Program SELECT [selecting it] b) Ctrl-Click on Second item in Program SELECT [selecting it] c) Ctrl-Click on Second item in Program SELECT [unselecting it] d) Ctrl-Click on Second item in Program SELECT [selecting it] * Expected behaviour: onLoad() event should be triggered and version, component and target milestone should update. * Actual behaviour: no onLoad() event triggered, version, component, target milestone SELECTs don't update. I came upon this while writing the fix for bug 96534 (it doesn't block us, however). Can somebody confirm this?
-> DOM Level 0.
Assignee: rogerl → jst
Component: Javascript Engine → DOM Level 0
QA Contact: pschwartau → desale
I can confirm this on linux build 2001083008. Netscape 4.x works fine for me so adding 4xp. Can somebody confirm this on Windows/Mac?
Clarifying summary.
Summary: Select-Unselect-Select second SELECT item fails to generate onChange() → onChange() not called after <SELECT> option is selected, unselected, selected
duplicated on Mac OS X build 2001080316
OS: Linux → All
Hardware: PC → All
Fabian, you're the DOM man, why not verify this for us? Shouldn't be too complicated to fix, I imagine. ;)
Fabian says that: <fabian> kiko: events are not my cup'o'coffee :( <fabian> kiko: they are wierdly implemented So over to HTML controls.
Assignee: jst → rods
Component: DOM Level 0 → HTML Form Controls
QA Contact: desale → madhur
On my build (with patch for bug 34297) this is fixed. Setting dependency.
Depends on: 34297
Fixed with bug 34297 landing.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.