Breakpoints early in the page lifecycle are not hit when using --auto-open-devtools-for-tabs
Reported by
jon.rim...@logicalglue.com,
Jan 5 2018
|
|
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: 1. Run Chrome with the command line flag --auto-open-devtools-for-tabs 2. Open a new tab, set a breakpoint on a script line that executes early in the page lifecycle. 3. Duplicate the tab. See the attached HTML file for a simple reproduction. What is the expected behavior? The breakpoint should be hit. What went wrong? The breakpoint is not hit when the tab is created. If the page is refreshed, then it is. The whole purpose of the --auto-open-devtools-for-tabs is to allow debugging of events that happen right away. If breakpoints do not work, that complete invalidates its purpose! Did this work before? N/A Chrome version: 63.0.3239.84 Channel: n/a OS Version: OS X 10.13.2 Flash Version: |
|
►
Sign in to add a comment |
|
Comment 1 by eostroukhov@chromium.org
, Jan 9 2018