3 ms·
Firefox dev tools are sometimes painful to use and lacks some important features which Chrome's has. Some examples: - debugging with source maps: it doesn't w
by agopaul 10y ago
Firefox dev tools are sometimes painful to use and lacks some important features which Chrome's has.
Some examples:
- debugging with source maps: it doesn't work properly (I can set breakpoints and debug variables content on typescript files in Chrome, but not in FF)
- JS exceptions: clicking on the filename inside the stack opens a new window with the source of the JS file, not the debugger (ugh)
- doesn't support typescript highlighting
- fbender 10y agoDid you try the Fx DevEdition? I know of some recent Source Map related changes. If the issue persists (same with the other issues you mention), would you mind filing a bug [1]? [1] https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...
- agopaul 10y agoYup, I tried FF Dev Edition a month ago, same thing. Maybe I will try again later after updating
- ankka 10y agoOn the other hand, the network tab in the dev tools actually knows how to parse incoming JSON, unlike Chrome which only renders a string.