Closed
Bug 6329
Opened 26 years ago
Closed 25 years ago
Referencing "missing" event attr in JavaScript stops script instead of being "undefined"
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: doyle.davidson, Assigned: joki)
Details
Attachments
(1 file)
(deleted),
text/html
|
Details |
In general under Milestone 5, JavaScript events are really flaky. Attached is
a HTML page containing JavaScript that attempts to display information about
the various mouse/click events using both a "button" and a text "span".
*** BE SURE TO REMOVE COMMENTS TO CAUSE SCRIPT TO "STOP" ****
Assuming the DOM2 UI-event model (I'm not real sure what attributes are
available for what events - any clues?). Any attempt to reference
an "undefined" attribute results in the current script function to just quit
executing.
Reporter | ||
Comment 1•26 years ago
|
||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Comment 2•25 years ago
|
||
I tried this one with undefined attribute and its returning undefined instead of
stopping the script execution.
Marking it WORKSFORME.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 3•25 years ago
|
||
Worksforme too.
marking verified
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•