Closed Bug 1241448 Opened 8 years ago Closed 8 years ago

Support chrome.debugger

Categories

(WebExtensions :: Untriaged, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: hsteen, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [debugger][triaged])

For parity with Chrome, we should add chrome.debugger support to our WebExtensions goals:

https://developer.chrome.com/extensions/debugger
Priority: -- → P2
Whiteboard: [debugger][triaged]
Unfortunately the chrome.debugger API is tricky to make it compatible with the Chrome one:

This API directly exposes the JSON debugging protocol to addons, on Firefox we have our own JSON debugging protocol which exposes similar features but with a different JSON protocol, so exposing our protocol to WebExtensions will not make existent chrome addons able to work on Firefox without changes in the addon itself.

I don't exclude that we can decide to expose our debugging protocol to addons through this APIs, but I do not consider it a proper chrome-parity issue, so it will have a lower priority of the devtools.panels or the devtools.inspectedWindow APIs.

PS: In the Firefox, we have a project called Valence that translate our JSON debugging protocol into the Chrome JSON debugging protocol to make it possible to debug a remote Chrome/Webkit-based target using our developer tools, which is actually the opposite of what this chrome.debugger API would need to do to be able (theoretically) to run Chrome addons that uses this API as WebExtensions without handling two different debugging protocols.
Based on comment 1 closing, if that's not the case then we should re-open.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Flags: needinfo?(lgreco)
Product: Toolkit → WebExtensions
Flags: needinfo?(lgreco)
You need to log in before you can comment on or make changes to this bug.