I am having trouble debugging my Extjs 4 files in Firebug. In the scripts tab of firebug I am only seeing app.js, ext-all-debug.js, and a bunch of files under /ext-4.0.7/ext-all-debug.js/eval/seq. I am unable to see any of the javascript files for my custom extjs objects.
3
votes
Open the NET tab and see if they're loaded or 404.
- Diodeus - James MacFarlane
I've given up on debugging ExtJS with Firebug -- whenever it needs to refer to a line number within the big files like ext-all-debug.js, it's off by dozens if not hundreds of line numbers. Don't know if anybody else has seen this, but I've switched to Chrome for this reason
- Dexygen
Yea, Firebug tends to get buggier with every version.
- user123444555621
@GeorgeJempty You're right Chrome works flawlessly. It's a shame that Firebug doesn't work nearly as well.
- Reflux
Never use Firebug. It often generates weird error when I have the firebug panel turned on, and the bug will disappear when I off it. A lot of issue with it, so rather, better use g.chrome.
- Lionel Chan
1 Answers
0
votes
I do not have a problem debugging ExtJS in firebug at all. A super helpful addition to firebug for ExtJS is Illuminations for Developers plugin. I highly highly recommend this tool, even if you just get the evaluation version. Paid version is even better and is worth every penny! I do not have any relationship with the creator other than I am a paying customer.
Having said that, Chrome stack traces generated by ExtJS are actually better. So I will switch to Chrome if I have a a consistent error that I want to trace.
