4 ms·

There was a great comment i read here yesterday. Developers build stuff on chrome because the console is amazing. So if the user uses chrome, there's a guarante

There was a great comment i read here yesterday. Developers build stuff on chrome because the console is amazing. So if the user uses chrome, there's a guarantee the website will work. Yes, firebug started it all, but chrome is killing it right now. Mozilla, why don't you start copying the chrome console already.

starik36 8y ago
What exactly is missing in Firefox DevTools? If anything, they are superior. I've switched over to Firefox DevTools for 2 reasons: 1. The box model is on the right instead of on the bottom, so I can mess with it and immediately see results in the Inspector styles window and the browser. https://i.imgur.com/KfxmRQT.png https://i.imgur.com/KfxmRQT.png 2. I can click on the Event bubble next to the element to see events that are bound to it and go to it if I choose so. https://i.imgur.com/UWiMttX.png https://i.imgur.com/UWiMttX.png
- 75dvtwin 8y ago
  In Firefox, debug breakpoints do not seem to always stay in tact when page is reloaded. Also hoovering mouse pointer over, does not always show variable's value. These problems are not present on Chrome.
- frankietwenty9 8y ago
  Can't resize columns in 'network' tab Step, Step Into, Resume.. use different function keys than I'm used to on Linux. Edit + Resend doesn't work for me on Linux. It works on Windows for me. Copying headers doesn't work well for me on Linux. I have to click 'Raw Headers' to copy a header. Works fine on Windows. Chrome is still faster than Firefox. I prefer chrome and Edge's download monitor. I prefer Firefox's proxy controls.
- maple3142 8y ago
  I found that chromium devtools is better at javascript debugging, but firefox devtools wins at css.