Chrome and Firefox browser debug comparison

Recent projects using EXTJS5, one of the main features is the dynamic loading of JS file, before using the Firefox browser to debug JS files, break point, only for when the debugging effective, after the refresh, due to the dynamic loading of JS file (file name after adding some random number) to change, The breakpoint you hit before will not work.

Today, when using chrome, it was found that this browser, even after the refresh, the breakpoint still works, which is very convenient when debugging.

I've heard that chrome development is more efficient than Firefox, and we've found a bit today.

But I found a little worse than Firefox, is Chrome's network is not as convenient as Firefox, in addition, the console control of Firefox can see the log, but also can see the request (usually I do not use Firefox network).

To summarize:

Comparison:

Chrome Benefits:

1. The dynamic loading of JS debugging more convenient.

2. js file after loading, there is a directory structure, convenient choice.

Firefox Benefits:

1. The console can view network request information.

Recently started to contact the front-end debugging, or a rookie, I hope that Daniel, can be more advice. I will also update this comparison information, so that everyone learn to learn.

Chrome and Firefox browser debug comparison