Chrome DevTools in 2016 and Beyond
developers.google.com
Chrome DevTools in 2016 and Beyond
1–10 of 59 posts
Re: Chrome DevTools in 2016 and Beyond
#2Excited 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.
Re: Chrome DevTools in 2016 and Beyond
#3Very happy about debugging Node.js in DevTools. Hard to imagine any third-party debugging applications having that amount of features and polish...
Re: Chrome DevTools in 2016 and Beyond
#4Excited 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.
AppCache is no more, deprecated, dead. Luckily.
Re: Chrome DevTools in 2016 and Beyond
#5the last part of that where paul irish live edits sass looks pretty awesome! good job chrome team!
Re: Chrome DevTools in 2016 and Beyond
#6They 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"?
Re: Chrome DevTools in 2016 and Beyond
#7They 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"?
Generally, a "progressive web app" is something that behaves a bit like a regular native app, when the browser supports it and user allows it. This includes using serviceworkers to cache data for offline (and low bandwidth) use, making a home-screen icon that launches a standalone (from the task switcher perspective) window with no browser frame, and so on.
Re: Chrome DevTools in 2016 and Beyond
#8They 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"?
Generally, a "progressive web app" is something that behaves a bit like a regular native app, when the browser supports it and user allows it. This includes using serviceworkers to cache data for offline (and low bandwidth) use, making a home-screen icon that launches a standalone (from the task switcher perspective) window with no browser frame, and so on.
Pretty much what I thought, thanks!
I'm a fan of the concept, hating apps that could easily have been webpages (public transport apps are often a good example), so it sounds like a good idea to give this a name and promote it. It's too bad that this name sounds like Microsoft came up with it in the early 2000s, but oh well.
Re: Chrome DevTools in 2016 and Beyond
#9Scrolling 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.
Re: Chrome DevTools in 2016 and Beyond
#10Cool to see node-inspector go full circle, from cleverly re-purposed debugger UI to officially supported product.