News for hackers. Stuff that matters.
Re:CSS and JS code coverage in Chrome DevTools by orliesaurus on Wednesday July 12, 2017 @08:42AM (#14751985)
Chrome Dev tools, the first reason why I started using Chrome. I wonder if HN has any better alternatives to suggest? I'm curious to see what I could be missing on!
Re:CSS and JS code coverage in Chrome DevTools by eterm on Wednesday July 12, 2017 @09:47AM (#14752463)
For a long time I've used firefox dev edition because their developer tools have been easier, particularly for editing and re-sending HTTP requests. (Right click "edit and resend" in firefox vs ? in chrome).

Also in firefox you can screenshot not just the whole page below the fold but screenshot any element by right-clicking the element in the elements pane.

Re:CSS and JS code coverage in Chrome DevTools by brandonwamboldt on Wednesday July 12, 2017 @08:44AM (#14752004)
It's not up to par with Chrome Dev Tools, but something to keep an eye on is https://github.com/devtools-html/debugger.html (a project run by Mozilla). This has the benefits of being open source and very accessible to developers (because of the technologies & being on GitHub).

It may one day give Chrome a run for it's money.

Re:CSS and JS code coverage in Chrome DevTools by nailer on Wednesday July 12, 2017 @12:44PM (#14754056)
Edge will probably get time travel debugging first, allowing you to rewind and inspect after something happens. Way better than adding debugger or console.log() everywhere.
Re:CSS and JS code coverage in Chrome DevTools by grahamperich on Wednesday July 12, 2017 @02:14PM (#14755018)
wow, that sounds like the holy grail of javascript debugging
Re:CSS and JS code coverage in Chrome DevTools by nailer on Wednesday July 12, 2017 @02:28PM (#14755159)
Yep. It's already in Chakra (MS's JS engine), they just need to do the Edge DevTools support.
Re:CSS and JS code coverage in Chrome DevTools by pluma on Wednesday July 12, 2017 @09:48AM (#14752468)
There is no better alternative. Or at least there wasn't earlier this year.

I tested several cross-platform browsers in Q1 this year and I always had to go back to Chrome because it's the smoothest dev experience.