Closed Bug 1451777 Opened 6 years ago Closed 5 years ago

Some errors are clearly webextension-related but not tagged as webextension-related

Categories

(Firefox :: General, defect, P3)

Product:
Firefox
Component:
General
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox61 --- affected

People

(Reporter: Gijs, Unassigned)

References

Details

For most of these, I think this is the intended behavior. Most of these errors are extension-related, but not errors in the extensions themselves.

Some of them are particularly annoying...

https://sentry.prod.mozaws.net/operations/nightly-js-errors/issues/3171944/ is from some terrible person throwing a raw Cr.NS_ERROR_ILLEGAL_VALUE. But, in any case, it's in the unexpected error branch, so it should not be reported as an extension error.

These should be reported as extension errors, but we apparently fail to capture the caller location for one reason or another:

https://sentry.prod.mozaws.net/operations/nightly-js-errors/issues/3191511/

These could be reported as extension errors if we captured the caller location, but that's its own bug:

https://sentry.prod.mozaws.net/operations/nightly-js-errors/issues/3164145/
https://sentry.prod.mozaws.net/operations/nightly-js-errors/issues/3187621/

The rest are framework problems that need to be fixed.
Priority: -- → P3

JavaScript error collection is being shut down and has already been removed from Nightly, so this isn't relevant anymore.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.