502718 - Errors in DOMAttrModified handler not displayed in the Error Console

Status: RESOLVED FIXED

(Core :: XPConnect, defect)

Description

[Sylvain Pasche]

Attachment: 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.

Comment 1

[(mostly gone) XtC4UaLL [:xtc4uall]]

ok: http://hg.mozilla.org/mozilla-central/rev/ee5135f3f773
fails: http://hg.mozilla.org/mozilla-central/rev/163e9f2fa5c1
range: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=ee5135f3f773&tochange=163e9f2fa5c1
another fallout of Bug 455436 it seems.

Comment 2

[Norm Fox]

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)

Comment 3

[Nochum Sossonko [:Natch]]

Probably too late for 1.9.2 blocking, but perhaps this should be looked into for 1.9.3?

Comment 4

[Johnny Stenback (:jst)]

Not blocking. But is this in any way specific to DOMAttrModified, isn't this just how event handler errors are treated nowadays?

Comment 5

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Or specifically, any events caused by javascript doing something. I.e. javascript calling form.submit() (fires submit event), calling setAttribute (fires mutation events), etc

Comment 6

[BMO Automation]

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.

Comment 7

[Boris Zbarsky [:bzbarsky]]

Works fine now, with webidl bindings.