Chrome Dev Tools Console tab opens automatically on every page load
Reported by
john.br...@faulknermediagroup.com,
Apr 14 2016
|
||||||||
Issue description
Chrome Version : 50.0.2661.75
OS Version: OS X 10.11.4
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: Not applicable
Firefox 4.x: Not applicable
IE 7/8/9: Not Applicable
What steps will reproduce the problem?
1. Use the Google Chrome browser
2. Navigate to any URL
3. Right click on the page, and choose 'Inspect'
4. Observe the Chrome Dev tools opens and the Console area automatically opens as well.
5. Close the Console tab by hitting the Esc key.
6. Refresh the page, and perform steps #3 and #4 again.
What is the expected result?
Chrome Dev tools should open without the Console tab opening automatically. The Console tab takes up a significant amount of screen space, and should only be opened when needed.
What happens instead of that?
When you open Chrome Dev tools, the Console tab opens as well. This requires the user to manually close the Console tab each time a page is loaded.
Please provide any additional information below. Attach a screenshot if
possible.
This can be replicated using the Chrome browser on OSX 10.11.4 and Windows 10
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36
,
Apr 17 2016
I can attest that this happens. Every time the dev tools is open on any other tab other than the Console and an error is thrown to the console, the console automatically opens. I do not mean the Console tab itself opens, but the mini Console that can be opened on every other tab opens automatically.
,
Apr 18 2016
,
Apr 19 2016
I followed ranjitkan's instructions above, and I still experience the issue. It seems to happen only if there are any errors in the console.
,
Apr 20 2016
After a little more digging, I discovered the issue seems to be related to the "Enable CSS source maps" setting. When I had this setting enabled, the Console tab would automatically open when I start Chrome Dev Tools. I would also receive the error "Failed to parse SourceMap" in the Console. When I uncheck "Enable CSS source maps" setting, I no longer receive the "Failed to parse SourceMap" error, and the Console tab no longer opens automatically.
,
Apr 20 2016
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 22 2016
Adding one more bit of detail necessary to replicate this problem. It looks like you must have "Enable JavaScript source maps" enabled in addition to "Enable CSS source maps" for this behavior to occur.
,
Apr 22 2016
,
Apr 22 2016
,
Apr 27 2016
,
May 27 2016
,
May 31 2016
WontFix because intended behavior. Errors such as the sourcemap error are actually thrown by the browser, not generated by the page itself. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ranjitkan@chromium.org
, Apr 15 2016Labels: Needs-Feedback