Closed Bug 895548 Opened 11 years ago Closed 8 years ago

tracking bug for cases where we unexpectedly don't report JS exceptions


(Core Graveyard :: Tracking, defect)

Not set


(Not tracked)



(Reporter: Gavin, Unassigned)


(Depends on 5 open bugs)


(Keywords: meta)

There are a lot of these bugs and I think a bunch of them are probably related to each other or duplicates, but I want to track them in one place.
Depends on: 584793
My understanding following the discussion in bug 844730 is that under the current architecture, there are likely a large number of separate small bugs (a la bz's suggestion in bug 895340 comment 2), but I (as a somewhat disinterested observer, I admit) think we should change the architecture (a la bug 844730 comment 15) so that we solve this stuff with a small number of bigger (and riskier) changes.  I'm under the impression that as we convert more Web APIs that involve native code calling JS functions from Web content (e.g., Events) to WebIDL, this becomes less risky because it doesn't touch as much.
Depends on: 502718
No longer depends on: 896928
Depends on: 898811
Depends on: 851884
Depends on: 957697
Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE.
If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work
being tracked. The Core: Tracking component will no longer be used.
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.