[remote-dbg-next] Reloading about:debugging on a remote runtime page should remain on the same page
Categories
(DevTools :: about:debugging, enhancement, P1)
Tracking
(firefox68 verified, firefox69 verified)
People
(Reporter: jdescottes, Assigned: jdescottes)
References
(Blocks 1 open bug)
Details
(Whiteboard: [remote-debugging-reserve])
Attachments
(1 file)
STRs: - open new about:debugging - connect to a remote device - reload about:debugging ER: User should remain on the remote runtime page AR: Redirected to this-firefox We now persist connections across reloads, so we should be able to stay connected. Note this might have slightly regressed since we aggressively try to stop ADB whenever we don't use it.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Depends on Bug 1528912 to keep connection on USB runtimes when reloading.
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 2•4 years ago
|
||
The idea is to wait for ADB runtimes to be available before trying to render the initial route.
This way if we happen to find the runtime matching the current runtime, and if we still have a connected client for it, we can display the same runtime page.
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d93d203fad60 Remain on the same Runtime page when reloading about:debugging r=ladybenko,daisuke
Comment 4•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Verified as fixed on Firefox Nightly 69.0a1 and on Firefox 68.0b5 on Windows 10 x 64, Mac OS X 10.14 and on Ubuntu 18.04 x64.
Comment 6•4 years ago
|
||
Actually I observed now that when I was connecting via USB, and after reloading "about:debugging" page, I was Redirected to this-firefox.
Is this the expected behavior in thins case?
Assignee | ||
Comment 7•4 years ago
|
||
(In reply to Hani Yacoub from comment #6)
Actually I observed now that when I was connecting via USB, and after reloading "about:debugging" page, I was Redirected to this-firefox.
Is this the expected behavior in thins case?
No it should remain on the same page (unless you are killing the ADB process for instance). Can you share more details about your test scenario?
Comment 8•4 years ago
|
||
- open new about:debugging.
- Make sure that you are connected to a network location.
- Enable USB Device.
- Connect to a mobile device. At this point you are connected via USB and via Network location.
- Make sure that the run time of the mobile device is selected.
- Reload about:debugging (it might need to reload the page 2-3 times)
Comment 9•4 years ago
|
||
Julian, did you have the time to look into this? Should I log a bug separate bug for this?
Assignee | ||
Comment 10•4 years ago
|
||
Sorry I missed your update!
Thanks for the additional info. Unfortunately I can't reproduce this for now, even reloading about:debugging very quickly a dozen of times I always remain on the runtime page for my mobile browser.
The STRs are specific enough to go into a separate bug. Since I can't reproduce this bug for now, I think we will need all the information possible (eg which mobile browser, which OS, etc). And if you can open the browser toolbox, to see if any error is logged when about:debugging fails to remain on the correct page, it would be useful as well.
Thanks!
Comment 11•4 years ago
|
||
Sure, I will add all the information needed in detail in a separate bug.
Thank you!
Comment 12•4 years ago
|
||
Logged bug 1557308.
Description
•