DevTools: add option to pause inspected popups on window.close
Reported by
jidanni@gmail.com,
Feb 11 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: I have found a way pages can 100% escape Developer Tools monitoring. Works every time. All the page has to do is have a button that opens a new tab/window. And then in that new tab/window do whatever it pleases. Totally with no way for the user to monitor it. It has already done what it wants to do by the time the user can switch to the new tab/window, turn on Developer tools, and then reload the page to supposedly see what it did. Because Developer tools is tab/window based, it can not govern other tab/windows. Therefore just like it has a "Preserve Logs" to last through redirects, it also needs a "Also monitor newly spawned tabs/windows". The idea would be each newly spawned window, at the bottom etc. would have their own Developer Tools half window. Another idea might be an option that would make Developer Tools "on" for all windows, instead of currently "off". How to reproduce? Fill out your U.S. tax form on the official IRS https://www.freefilefillableforms.com/ site. Then hit "print form". (Be sure to do it while the tax filing season is still open.) What is the expected behavior? Can monitor everything going in to the browser. What went wrong? Some things you still just can't monitor. Did this work before? No Chrome version: 64.0.3282.119 Channel: n/a OS Version: Flash Version: (Mainly one is interested in the Network portion of Developer Tools here.)
,
Feb 11 2018
OK. Sounds great. Please retitle my bug report to "add option to don't allow auto-closed windows to also destroy their Developer Tools window" or something.
,
Feb 11 2018
Also due to Issue 811091 , there is no way Preserve Log will be pre-checked in the new window, so much often is lost anyway...
,
Feb 11 2018
,
Feb 12 2018
While you can add an event listener breakpoint for unload & beforeunload. They do not hit unless there is a registered event listener. A chrome extension has ability to assist in this case. dgozman, what do you think of this feature request? I could go either way.
,
Feb 15 2018
I think running chrome with --auto-open-devtools-for-tabs should help. Note that we are not playing cat and mouse with web developers. If someone does not want their site to be debuggable, there is no way we can force it.
,
Feb 16 2018
OK. (I was just hoping chromium would be replacement for tcpflow for https, recording each transaction in nice tcpflow style files, not more splintered, not less splintered.) |
||||
►
Sign in to add a comment |
||||
Comment 1 by woxxom@gmail.com
, Feb 11 2018