Keep requests visible when different tabs are selected

[#1]

The previous version of the debugger keeps all the requests open when changing tabs in the browser. The current version shows only the requests for the active tab.

This creates extra steps in the workflow when working between two or more tabs and the debugger window. This is often required when validating variables in an Adobe Analytics workspace while testing a page. Leaving the tab also collapses the request so it has to be re-opened and then scrolled to the right to see the current hit.

It would be better if the request would stay open, even when the active tab is changed. It would also be better if the focus remained on the most recent hit, rather than adding them outside the window so that they have to be scrolled to.

[#2]

Thank you @Don_R ; we will discuss this request and keep you posted.

[#3]

This is the same problem that I am having with the new version. 

[#4]

Agreed. This feature requires extra steps in my workload. Previous version layout was much more user friendly.

[#5]

YES!!

It is SO annoying that the information disappears the second you move off the website.  I have 3 monitors going; one with the debugger, one with the website I am debugging and one with Workspace.  I am constantly having to refresh my webpage to get the information back in the debugger, which is super inefficient! I have to clear calls and start the experience all over to make sure I have the right number of calls firing since the information doesn't stay put and I had to refresh prior.  It throws my counts all off and takes longer.  It should never go away.  Just keep populating additional report suites below like the beta debugger did.

[#6]

@jnkametz If you return to the tab with the site you are debugging, the information should re-appear in the debugger. It will be collapsed and you still have to open it and scroll all the way over to see the most recent hits (extra clicks and scrolling in the workflow - also annoying - but at least you don't lose the train of information).

[#7]

@Don_R  this will be coming the next Debugger release.

[#8]

@Don_R @jnkametz  @CatCura @SvenBuning 

Version 1.2 of the AEP Debugger supports persisting all the events in the `Network` tab across all browser tabs: https://experienceleague.adobe.com/docs/debugger/using-v2/release-notes.html?lang=en#version-1.2.0-o...

Can you please take a look and let us know if that solves your previous concerns?

Thank you.

Joe

[#9]

No, this does not solve the problem.  

While I can move off the active website tab and the network tab within the debugger stays active, vs the analytics solution tab disappears, when I move around the website, the information is not complete within the network tab.  Therefore I still have to go back to analytics to view.  For instance, I was on the homepage, navigated to a different landing page, and items such as page name did not collect in the network tools tab.  They appear as blank analytics calls, yet the information is being collected under the Analytics solution.

[#10]

Picture for reference.

It would be nice, not only did the analytics solution stay to the forefront when toggling around, but even if it collapses, when you come back to the active website tab, it should reopen at the last click/page call, instead of going back to the beginning of the session.  Then you have to scroll and find where you left off and if it collected the last action you took and debug if everything is working as designed.  It currently is a terrible experience as I usually have my site, debugger, and workspace open all at the same time when investigating.