Is there a way of doing a long running log of all network, page load speeds, etc. in Chrome and store it in a reasonably efficient format? Like a perfmon/tracer for the browser.<p>I ask this because I've been trying to track down an issue - probably caused by an ad on a news website - where Chrone pretty much freezes up on all processes. Whilst I can (and have) worked around it by installing uBlock Origin in browsers I'd really like to know what is causing the problem. I can't produce it locally so I'd like to get a log of all things that occur on Chrome over the course of a day.
They mention "Progressive web apps" and link to some info, but I can't figure out what the difference is from a normal webpage. Do they mean "web apps that use some stuff that was recently added to most modern web browsers"?
After 5+ years of developing in Chrome Dev tools, I switched to Safari 2 weeks ago (Mac) and couldn't be happier. Chrome has become bloated. Ever notice CPU fans ramping up? Only while Dev Tools is open. Memory hog is an understatement. Furthermore, while Chrome's light, prebundled Flash was an asset 3 years ago it's now a liability: most websites now gracefully fallback to HTML5 video. Safari's upcoming leading edge standard support announcement makes it a candidate for best dev browser. (Hint: try Safari's Responsive Mode)
It's ironic that scrolling stutters so much on a Google Developers page when using Chrome on Android (51.0.2704.81). Inertial scrolling is broken too.<p>I rarely have this problem on other sites. It usually only occurs on Javascript heavy sites (disproportionately frequently on Google sites using that Material UI toolkit).<p>I'm using a Samsung S7, but had this same issue on my Nexus 6.
I'm glad to see Css source diffs in there. My workflow consists of tweaking Css in dev tools and then updating source. I've found that if I map directly so Devtools updates the source file I get lost very quickly.
Incidentally I'd be interested in knowing of better ways of writing / debugging css.
slowly the browser is becoming an JS IDE, and that's nice. Ctrl-Shift-I can become the "READY" prompt of the C64.
The "next thing" is CDT auto-saving your changes to css and js for a website, and optionally re-applying them on future browsing.
Excited to see better support for App Cache and Service Workers. I still have a bad taste in my mouth from trying to integrate them into one of my applications.
Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.
NodeJS and Chromium have complete different debugging API's. It would be cool if they where the same, so you could reuse the debugging tools on both platforms.