Closed Bug 1061833 Opened 10 years ago Closed 7 years ago

Access for remote debugging directly from browser

Categories

(DevTools :: General, defect)

Product:
DevTools
Component:
General
Version:
33 Branch
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: akratel, Unassigned)

References

Details

(Whiteboard: [status:planned])

User Story

As a developer I'd like to be able to connect to remote devices or browsers from browser and be able to remote debug supported devices. 

Acceptance criteria:
- UI to guide developer to connect to a supported device and browser
- UI to save connections and re-use them (maybe should be a separate user story)
- Remote debug and use console on Safari on iOS
- Remote debug and use console on Chrome on Android
- be able to bring up a stand alone toolbox that's attached to a remote session (ideally in WebIDE, but a stepping stone might be to have a stand alone toolbox attached to a remote debugging session.)
Feverdream tracking bug to be able to connect to remote devices directly from the toolbox and without having to open webIDE. Limiting user story to remote debugging and console, and to iOS and Android.
Why do we want to be able to do that without using WebIDE?
I see this bug as a stepping stone, right? There are a bunch of things that we need do to enable remote debugging from the toolbox (step 1), and all those problems (plus more) need to be solved in order to get remote debugging from webide (step 2). Things like making webide project agnostic are part of the step 2. Multiple runtimes from a single connection are part of step 1. So this bug just calls out step 1.
I am not advocating this as a permanent solution. We need to be able to manage remote sessions and bring up a stand alone toolbox not in the context of a tab to do this. The right way to do this is to do it in WebIDE, and if we can do it by Nov 9th, that's great. If there is an interim step, let's do it. But I went ahead and removed any language in the bug that would suggest where any of this should take place.
User Story: (updated)
Summary: Access for remote debugging from toolbox → Access for remote debugging directly from browser
Note: this is the "short pole", a stepping stone to enable Feverdream before completing 1043937.
See Also: → 1043937
(In reply to Joe Walker [:jwalker] (overloaded - needinfo me or ping on irc) from comment #2) > I see this bug as a stepping stone, right? > > There are a bunch of things that we need do to enable remote debugging from > the toolbox (step 1), I don't think there's anything to do. > and all those problems (plus more) need to be solved > in order to get remote debugging from webide (step 2). Me and Ryan are working on integrating fever dream into webide. There really is nothing to do at the toolbox level. > Things like making webide project agnostic are part of the step 2. We only need to support tabs, and it's about to land: bug 1009604. > Multiple runtimes from a single connection are part of step 1. It's now possible to create multiple runtimes from the ADBHelper now (it has landed yesterday). What needs to be done to have a proper support (not including Dave's work on the webkit transport): - implement scanner + drivers mechanisms, make them extensible - create a static version of ios_webkit_debug_proxy to embed it in ADBHelper There is work to do at the transport level too. I just need to understand what the scope of this bug is exactly.
This was the feverdream (later renamed valence) tracking bug. Valence is now unsupported anymore.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.