|
|
|
|
|
by rndgermandude
2489 days ago
|
|
The Chrome profiler is a lot better (IMO) than the one Firefox ships. But then there is 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. |
|