Referencing "missing" event attr in JavaScript stops script instead of being "undefined"

VERIFIED WORKSFORME

Status

()

P3
normal
VERIFIED WORKSFORME
20 years ago
19 years ago

People

(Reporter: doyle.davidson, Assigned: joki)

Tracking

Trunk
x86
Windows 98
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

20 years ago
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

20 years ago
Created attachment 169 [details]
HTML to reproduct problem(s)

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → WORKSFORME

Comment 2

19 years ago
I tried this one with undefined attribute and its returning undefined instead of
stopping the script execution.
Marking it WORKSFORME.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 3

19 years ago
Worksforme too.
marking verified
You need to log in before you can comment on or make changes to this bug.