Open Bug 1433724 Opened 4 years ago Updated 2 years ago

Web Extension API to listen console log messages


(WebExtensions :: Developer Tools, enhancement, P5)



(Not tracked)



(Reporter: kabilan.vk, Unassigned)



(Whiteboard: [design-decision-approved][dev-ux])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce:

Support to listen console messages using new browser extensions.

Actual results:

No support as of now.

Expected results:

Way to access console messages through extensions.
Severity: normal → enhancement
Component: Untriaged → WebExtensions: Untriaged
OS: Unspecified → All
Product: Firefox → Toolkit
Hardware: Unspecified → All
It helps streamline the decision-making progress for proposed new APIs if you can explain what sorts of extensions would use this API and how they would use it.
Flags: needinfo?(kabilan.vk)
Whiteboard: design-decision-needed
Component: WebExtensions: Untriaged → WebExtensions: Developer Tools
We are using the consoleexport ( extension to download all console log messages for our QA automation testing purposes. ConsoleExport actually uses Firebug to listen console logs. When Firebug is deprecated by Firefox, we moved to this example ( posted in GitHub to achieve the same. The example used the console API as i mentioned in the bug description but that's gone now in Firefox Quantum. Can you please add console API support in new web-extensions framework?
Flags: needinfo?(kabilan.vk)
Product: Toolkit → WebExtensions
Priority: -- → P5
Whiteboard: design-decision-needed → [design-decision-approved]
Whiteboard: [design-decision-approved] → [design-decision-approved][dev-ux]
You need to log in before you can comment on or make changes to this bug.