4 ms·

Other than the web socket support in Chrome, the FF dev tools are a billion times better than Chrome now. I cannot work without the css layout overlays from FF

Other than the web socket support in Chrome, the FF dev tools are a billion times better than Chrome now. I cannot work without the css layout overlays from FF dev tools. Makes working with grid layouts insanely easy.

icemelt8 7y ago
how many production websites you work on use Grids? just curious.
- philliphaydon 7y ago
  Only for internal apps and personal stuff. I don’t really work on client facing stuff.
raugustinus 7y ago
While I mostly agree, I do switch to Chrome every once in a while when the javascript stacktrace in FFdev is a bit unclear. Chrome usually seems to be a bit better. But I always switch right back to FF.
- tester346 7y ago
  Debugging fancy JS frameworks in firefox (for me, unexperienced js user) is more painful than in chrome, but debugging js in webbrowser is pain anyway
  - eitland 7y ago
    In Angular (which I like) I have found that there is a bug in error logging that only occurs on Firefox. So every time I stumble upon that I'll open Chromium, find the stack trace and go back.
Vinnl 7y ago
I think they're almost done with the first iteration of WebSocket support in the Firefox DevTools. Might even already be in Developer Edition: https://bugzilla.mozilla.org/show_bug.cgi?id=885508 https://bugzilla.mozilla.org/show_bug.cgi?id=885508
- philliphaydon 7y ago
  Great news. This is the only thing I open chrome for! Thanks for the info.
  - digitarald 7y ago
    DevTools guy here, WebSockets will be in DevEdition in the next build, b2, next week!
    - Vinnl 7y ago
      Thanks for your work!
rndgermandude 7y ago
The Chrome profiler is a lot better (IMO) than the one Firefox ships. But then there is https://profiler.firefox.com/ https://profiler.firefox.com/ The debugger/sources view in Firefox also seems buggier still. E.g. a lot of times while it correctly displays source-mapped locations in the console, clicking on those source links will not actually go to the right place in the source view (it will either end up in the packed source or it will not go to the correct line in the source-mapped file even tho the console link gave the correct line). One thing I miss that Firefox does not have at all is the Layers view. Which would be especially important since such things are browser specific and debugging performance/memory issues and making sure the engine uses a sane set of compositing layers can be important sometimes. But the feature I miss most in my tiny corner of the world by a large margin is the Websocket support indeed. This is the thing that always makes me go back to Chrome devtools.
- digitarald 7y ago
  WebSocket inspector will be in DevEdition next week!

icemelt8 7y ago

how many production websites you work on use Grids? just curious.

philliphaydon 7y ago
Only for internal apps and personal stuff. I don’t really work on client facing stuff.

raugustinus 7y ago

While I mostly agree, I do switch to Chrome every once in a while when the javascript stacktrace in FFdev is a bit unclear. Chrome usually seems to be a bit better. But I always switch right back to FF.

tester346 7y ago
Debugging fancy JS frameworks in firefox (for me, unexperienced js user) is more painful than in chrome, but debugging js in webbrowser is pain anyway
- eitland 7y ago
  In Angular (which I like) I have found that there is a bug in error logging that only occurs on Firefox. So every time I stumble upon that I'll open Chromium, find the stack trace and go back.

Vinnl 7y ago

I think they're almost done with the first iteration of WebSocket support in the Firefox DevTools. Might even already be in Developer Edition: https://bugzilla.mozilla.org/show_bug.cgi?id=885508 https://bugzilla.mozilla.org/show_bug.cgi?id=885508

philliphaydon 7y ago
Great news. This is the only thing I open chrome for! Thanks for the info.
- digitarald 7y ago
  DevTools guy here, WebSockets will be in DevEdition in the next build, b2, next week!
  - Vinnl 7y ago
    Thanks for your work!

rndgermandude 7y ago

The Chrome profiler is a lot better (IMO) than the one Firefox ships. But then there is https://profiler.firefox.com/ https://profiler.firefox.com/ The debugger/sources view in Firefox also seems buggier still. E.g. a lot of times while it correctly displays source-mapped locations in the console, clicking on those source links will not actually go to the right place in the source view (it will either end up in the packed source or it will not go to the correct line in the source-mapped file even tho the console link gave the correct line). One thing I miss that Firefox does not have at all is the Layers view. Which would be especially important since such things are browser specific and debugging performance/memory issues and making sure the engine uses a sane set of compositing layers can be important sometimes. But the feature I miss most in my tiny corner of the world by a large margin is the Websocket support indeed. This is the thing that always makes me go back to Chrome devtools.

digitarald 7y ago
WebSocket inspector will be in DevEdition next week!