1632530 - Remember selected evaluation context when reloading/reopening the console

Status: NEW

(DevTools :: Framework, enhancement, P3)

Description

[Nicolas Chevobbe [:nchevobbe]]

Alex was wondering if we could have a way to remember the selected context when re-opening the console, and it made me think of the following use case.

As a webapp developer, you're chasing a bug in an iframe/worker.
You selected the target you wanted to run some assertions on.
Then you do edits in your code and reload the page to check things again.
At the moment, when reloading the remote frames/workers targets are going to be destroyed, which mean we'll select the top level target again.
So you have to select the right target again in the selector.

Maybe it would be nice if the console remembers that you selected a given context, and try to select it again for you.

Comment 1

[Alexandre Poirot [:ochameau]]

Actually, I was wondering while testing the browser toolbox. I could easily see value there, especially about toolbox opening.

But your scenario with page reload sounds even more important/useful.

We may investigate the two independently as toolbox opening and page reload may require distinct code? (I have no idea yet if that's the case)

Comment 2

[Chris Peterson [:cpeterson]]

Tracking Fission DevTools bugs for Fission Nightly (M6) milestone

Comment 3

[:Harald Kirschner :digitarald]

Agreed, having this behave like Inspector, where it reselects the current node on reload, would be useful affordance.

Comment 4

[Chris Peterson [:cpeterson]]

dt-fission-m2-reserve bugs do not need to block Fission Nightly (M6). For now, let's track them for Fission riding the trains to Beta (M7) so we revisit these bugs before we ship Fission.

Comment 5

[Neha Kochar [:neha]]

Bulk move of all dt-fission-m2-reserve bugs to Fission MVP milestone.

Comment 6

[Chris Peterson [:cpeterson]]

Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.