Closed Bug 502718 Opened 12 years ago Closed 2 years ago

Errors in DOMAttrModified handler not displayed in the Error Console

Categories

(Core :: XPConnect, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- -

People

(Reporter: sylvain.pasche, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: regression, testcase)

Attachments

(1 file)

Attached file testcase
This is similar to bug 415498. If you try the attached testcase, no errors are reported in the Error Console. They are reported with Firefox 3.0, so it's a regression.
obvious JavaScript syntax errors like Object..parm are also not getting picked up by the error console.  (Seen in FF 3.5.1 on OSX 10.5)
Probably too late for 1.9.2 blocking, but perhaps this should be looked into for 1.9.3?
Blocks: 455436
blocking2.0: --- → ?
Flags: wanted1.9.2?
Not blocking. But is this in any way specific to DOMAttrModified, isn't this just how event handler errors are treated nowadays?
blocking2.0: ? → -
Or specifically, any events caused by javascript doing something. I.e. javascript calling form.submit() (fires submit event), calling setAttribute (fires mutation events), etc
Blocks: 895548
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INACTIVE
Works fine now, with webidl bindings.
Depends on: ParisBindings
Resolution: INACTIVE → FIXED
You need to log in before you can comment on or make changes to this bug.