Closed
Bug 1469058
Opened 6 years ago
Closed 6 years ago
[meta] Connect to USB devices from about:debugging
Categories
(DevTools :: about:debugging, enhancement)
DevTools
about:debugging
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: birtles, Assigned: daisuke)
References
(Blocks 2 open bugs)
Details
(Keywords: meta)
No description provided.
Reporter | ||
Comment 1•6 years ago
|
||
This meta bug covers all the work needed get USB connections working from about:debugging (but not the panel with the debugging contexts for the device).
Keywords: meta
Summary: USB connection for new about:debugging interface → Connect to USB devices from about:debugging
Reporter | ||
Updated•6 years ago
|
Priority: -- → P3
Comment 2•6 years ago
|
||
Moving major about:debugging ng work into milestone 1, leaving m0 for prior bugfix work.
Blocks: remote-debugging-ng-m1
Updated•6 years ago
|
No longer blocks: remote-debugging-ng-m0
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → dakatsuka
Status: NEW → ASSIGNED
Comment 3•6 years ago
|
||
As discussed this morning will should break this down:
- connect to a USB device (connect button, create the client when clicking on connect)
- select a connected USB device (should show runtime page for the devices, listing all targets - assuming this won't be challenging, but debugging tabs is the real priority so if we can only list tabs that's fine)
- debug tab for USB device
If is is challenging to debug other targets than tabs, we should skip it. USB tab debugging is scheduled for m1, other targets are in m2.
Updated•6 years ago
|
Priority: P3 → P1
Updated•6 years ago
|
Status: ASSIGNED → NEW
Priority: P1 → --
Summary: Connect to USB devices from about:debugging → [meta] Connect to USB devices from about:debugging
Comment 4•6 years ago
|
||
All dependencies have been resolved here, I think we can close this meta?
Flags: needinfo?(dakatsuka)
Assignee | ||
Comment 5•6 years ago
|
||
Indeed!
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(dakatsuka)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•