New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 610308 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

[Improvement] Toggleable setting to hook DevTools' Network panel on pages by default

Reported by raphael...@gmail.com, May 9 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36

Steps to reproduce the problem:
This is an improvement/suggestion.

Current:
Right now, DevTools will only hook to the page when it's opened. Meaning any network events will not be recorded until is opened.

What is the expected behavior?
Improvement:
Implement a DevTools' setting where user can toggle an option to make DevTools always hook to the pages, independent of having it opened or not. 

What went wrong?
Why/Pros:
As a web developer, sometimes we must investigate defects or stumble upon them on a daily basis. This would save time as Network panel would record all ajax and files, enabling us to check the Network tab right away, without having to refresh the page to start the flow all over again because DevTools wasn't open at the time. This is most critical on one-time scenarios, like error on first attempt or one-time pages (order confirmation page, for e.g.).

Cons:
This might make Chrome spend more resources (ram, cpu, etc) since it would be hooking on all pages, but that setting could be implemented as an Experiment, meaning need some flag toggled beforehand @ chrome://flags/ in order to avoid common users to not toggle it by mistake and complain about "Chrome is slow", "Chrome is using XXgb ram" and etc.

Did this work before? N/A 

Chrome version: 50.0.2661.86  Channel: n/a
OS Version: OS X 10.10.5
Flash Version: Shockwave Flash 21.0 r0

Discussion @ DevTools From: 
https://groups.google.com/forum/#!topic/google-chrome-developer-tools/15zWYh4d_ck
 

Comment 1 by caseq@chromium.org, May 10 2016

Cc: paulir...@chromium.org dgozman@chromium.org
Components: -Platform>DevTools Platform>DevTools>Network
Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 2 by allada@chromium.org, Jul 22 2016

Status: WontFix (was: Assigned)
This would cause blink to hold far too much request data for pages and would likely cause many times more problems than it would solve. What would likely happen is that we'd get developers complaining that their chrome is using extreme amounts of memory when visiting heavy ajax sites and such which would be because they forgot to turn the feature off.

We think developers will likely have devtools open when they plan on debugging a page. Yes it's one extra step, but the cost vs gain is too high.

Sign in to add a comment