Support DevTools Addons on developer toolboxes connected to remote tabs

ASSIGNED
Assigned to

Status

()

Toolkit
WebExtensions: Developer Tools
P3
normal
ASSIGNED
a year ago
5 months ago

People

(Reporter: rpl, Assigned: dthayer)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: triaged)

(Reporter)

Description

a year ago
The initial version of the DevTools API is going to support the customization of developer toolboxes connected to a local tab (the regular developer toolbox available for webpages loaded in a local Firefox tab).

The goal of this issue is to analyze the additional issues (and the  changes needed) related to make the DevTools Addons created using the WebExtensions API able to support customizations of developer toolboxes connected to remote targets (in particular tabs opened on Firefox for Android).

Updated

a year ago
Priority: -- → P3
Whiteboard: triaged
(Assignee)

Updated

8 months ago
Blocks: 1371003
:mstange and I discussed something similar a few months ago, and I filed bug 1351533 to do the minimum work of exposing WebIDE's runtime data for a connection.  It wouldn't be accessible to a WebExtension, but perhaps this bug might want something similar.
See Also: → bug 1351533
We'll want to use the runtime data exposed by bug 1351533 for the internal implementation of the remote profiler WebExtension API in bug 1371003: The profiler API has a way to ask for symbol tables, and in order to get that symbol information, we'll need to pull libraries from the device.
(Assignee)

Updated

7 months ago
Assignee: nobody → dothayer
Status: NEW → ASSIGNED
(Assignee)

Comment 3

7 months ago
How far do we want to go on this? I'm interested in it purely for the Gecko Profiler, which just needs to make a panel and then use some APIs that aren't made yet, but nonetheless I have a patch ready that implements everything other than tabId. tabId is tricky because at that point everything else outside of devtools that uses tab IDs needs to be capable of interacting with remote tabs. For this reason I separated out devtools_page from a remote_devtools_page, so that remote tab access is opt-in, so as to not break any assumptions of existing extensions.
You need to log in before you can comment on or make changes to this bug.