Closed Bug 599226 Opened 15 years ago Closed 15 years ago

page-mod should log exceptions with console.exception, not roll its own logger

Categories

(Add-on SDK Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: adw, Assigned: adw)

Details

Attachments

(1 file)

Attached patch patchSplinter Review
page-mod logs exceptions with console.error in a weird format that's not consistent with the rest of Jetpack. For example, when a content script has an undefined var, this is logged: error: XXXadw is not defined /Users/adw/jetpack-sdk/packages/page-mod-canvas/data/content-script.js 12 @/Users/adw/jetpack-sdk/packages/page-mod-canvas/data/content-script.js:12 Instead, this should be logged, which is what happens if the exception is passed to console.exception: error: An exception occurred. Traceback (most recent call last): File "/Users/adw/jetpack-sdk/packages/page-mod-canvas/data/content-script.js", line 12, in ReferenceError: XXXadw is not defined
Attachment #478164 - Flags: review?(myk)
That first error is actually all on one line.
Attachment #478164 - Flags: review?(myk) → review+
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: -- → 0.9
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: