Closed Bug 1516529 Opened 2 years ago Closed 2 years ago

[remote-dbg-next] Network connections are not persisted across reloads

Categories

(DevTools :: about:debugging, defect, P1)

defect

Tracking

(firefox66 affected, firefox67 unaffected, firefox68 affected)

VERIFIED FIXED
Firefox 66
Tracking Status
firefox66 --- affected
firefox67 --- unaffected
firefox68 --- affected

People

(Reporter: jdescottes, Assigned: jdescottes)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

STRs:
- start another Firefox with `--start-debugger-server 6080`
- back to test instance of Firefox
- enable network locations for about:debugging-new by setting devtools.aboutdebugging.network to true
- open about:debugging-new 
- add localhost:6080
- click on Connect
- reload 

ER: localhost:6080 should still be connected
AR: Connect button is displayed again

A fair share of the logic to refresh connections is USB-only at the moment.
Attachment #9033409 - Attachment description: Bug 1516529 - Test that network runtime connections are also persisted;r=daisuke,ladybenko,ola → Bug 1516529 - Test that network runtime connections are also persisted;r=daisuke
Attachment #9033408 - Attachment description: Bug 1516529 - Restore connections for NetworkRuntimes;r=daisuke,ladybenko,ola → Bug 1516529 - Restore connections for NetworkRuntimes;r=daisuke
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b7593c6b7d1e
Restore connections for NetworkRuntimes;r=daisuke
https://hg.mozilla.org/integration/autoland/rev/e03824ca4e74
Test that network runtime connections are also persisted;r=daisuke
https://hg.mozilla.org/mozilla-central/rev/b7593c6b7d1e
https://hg.mozilla.org/mozilla-central/rev/e03824ca4e74
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 66

Verified as fixed on Firefox Nightly 68.0a1, Firefox Dev Edition 67.0b4 and on Firefox 66.0.1 on Windows 10 x 64, Mac OS X 10.14 and on Ubuntu 16.04 x64.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.