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

Steps to reproduce the problem:
I didn't want to introduce a new, duplicate issue for 141129, however, given its current status, the only recourse for non-contributors is to file new bugs.

I'd prefer to wait for  Issue 141129  be re-opened to comment further, but I would be remiss if I don't address some now.

> Restricting comments since the comments being given are not on topic for the issue tracker.
https://bugs.chromium.org/p/chromium/issues/detail?id=141129#c42

This is just a garbage move. (Unless the 'off-topic' comments have been deleted.) Of all the 48 comments on the issue, I wouldn't consider even one of them as 'not on topic'.

> With this being a feature request it is low priority and combine that with a low star count, it isn't getting any higher on the list.
https://bugs.chromium.org/p/chromium/issues/detail?id=141129#c39

Another terrible argument.
1. Most people don't file bugs.
2. Most people don't go to an issue tracker to "star" bugs (now) 4 year old bugs.
3. Most people, when they encounter a bug, will go find an alternative that works.

Sure. One could use a more advanced tool like CharlesProxy, Wireshark, Tcpdump. But, more concerning for Chrome\Chromium, most people could just switch to Firefox, Safari, or IE.

> Labels: -Type-Bug Type-Feature
https://bugs.chromium.org/p/chromium/issues/detail?id=141129#c39

(I hope this is taken respectfully as I am not intending to troll.) Your head is firmly up your ass if you think this is a 'Feature' and not a 'Bug'.

What is the expected behavior?
Absolutely not.

What went wrong?
The issue with DevTools is well documented in 141129 and its duplicates.

Did this work before? N/A 

Chrome version: 50.0.2661.102  Channel: stable
OS Version: OS X 10.11
Flash Version: Shockwave Flash 21.0 r0