1364490 - Closing the tab, browser or disconnecting the Android phone should not close the WebIDE debugging session.

Status: NEW

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

Description

[Jukka Jylänki]

When one uses WebIDE to connect to an Android phone to debug, performance profile, examine network tab, etc. the connection is made by connecting to the phone first, and then to a tab on that phone. After that one can access the Devtools panels Console, Inspector, Debugger, Network, Performance, and so on.

Currently if one closes the connected tab on the phone, disconnects the USB cable, or anything else like that, the WebIDE tab on the host PC immediately vanishes. This is inconvenient for UX, since it disallows keeping the results of e.g. a previous Performance profiling run or the results of a web page Console log open for a longer examination, unless one manages to keep the connection alive for the whole duration of examination. A bad wifi connection or a bad connection on the USB cable can make the captured data vanish.

It would be preferable to never force close a WebIDE window on a user, but use some other visual cue to signal that the given window has gone stale, and disallow further "active" operations on that tab. That way no data is lost and one can examine results of a performance profiling run as long as desired, and perhaps connect to another phone to do a side by side performance profile to cross compare; and not have to worry about a bad wifi, battery dying on the phone, or a bad usb cable contact.

Comment 1

[Julian Descottes [:jdescottes]]

I am moving this to about:debugging as the connect workflow will ultimately move there and there is very little chance that WebIDE will get fixed in the meantime.