Not sure it this should be here. Probably related to Bug 905327 There is a class of issues which are hard to diagnose because they happen in the transition in between two tabs. Sites opening a new tab/window for login, for downloading files, for enabling a configuration. It would be cool to have a mode where we can ask the devtools to track this kind of stuff: 1. Be on a tab for a website 2. Make an action on this site which will open a new tab 3. Have devtools track the opening of the new tab. 4. Have devtools opened on the old tab and the new tab (separate windows is fine for each tab is fine). 5. Have the devtools started BEFORE any interactions with regards to the site happened in the new tab (network included). 6. Have the possibility to tell the devtools to block the auto-destruction of the tab (some login sites for example) so we do not lose the context of the devtools.
Bug 1569859 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Not sure if this should be here. Probably related to Bug 905327 There is a class of issues which are hard to diagnose because they happen in the transition in between two tabs. Sites opening a new tab/window for login, for downloading files, for enabling a configuration. It would be cool to have a mode where we can ask the devtools to track this kind of stuff: 1. Be on a tab for a website 2. Make an action on this site which will open a new tab 3. Have devtools track the opening of the new tab. 4. Have devtools opened on the old tab and the new tab (separate windows is fine for each tab is fine). 5. Have the devtools started BEFORE any interactions with regards to the site happened in the new tab (network included). 6. Have the possibility to tell the devtools to block the auto-destruction of the tab (some login sites for example) so we do not lose the context of the devtools.