Closed
Bug 1208590
Opened 9 years ago
Closed 9 years ago
console.log in content script logs to browser console rather than addon debug console
Categories
(DevTools :: Console, defect, P2)
DevTools
Console
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1006102
People
(Reporter: ashraf, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [btpp-fix-later])
Attachments
(1 file)
|
1.12 KB,
application/zip
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.99 Safari/537.36
Steps to reproduce:
Placed console.log inside content scripts in addons built via the SDK
Actual results:
console.log goes to browser console
Expected results:
console.log should go to addon debug console since it's clearly part of the addon. Checking two logs is very inconvenient.
Component: Untriaged → Developer Tools: Console
This is a simple SDK extension. Just visit any website, you'll see that the console.log inside the content script showed up in the browser console, rather than the extension debug console.
Blocks: dbg-addon
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Whiteboard: [btpp-fix-later]
|
||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
|
||
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•