Hi Sebastian,
Thank you for replying. I did not know 1.12.x was not compatible anymore, that is good to know, thanks :) On the Firebug site beside the download link it says 'Compatible with: Firefox 23+'.
The strangest thing; when I went to FF today - opened (Ctrl+Shift+J) first - interested in what would appear... but Firebug opened... Hadn't opened for last two days... maybe with the shut down last night, cleared something out - I don't know why it has started working, but it's great news :)
When it started to work though - it got this in the script tag - 'This Version of Firefox removed the old JavaScript debugging API. Please install Firebug 2.0, which adopts the new API.'
The reason for us still using 1.12.x; is we are having trouble with 2.x
We work on a large enterprise app that is very frontend orientated with a large JS codebase. With Firebug 2.0.8 running; when loading our pages (in obfuscated & minified mode), we are getting multiple unresponsive script alerts on page load, one being:
chrome://firebug/content/debugger/script/sourceTool.js:339
Clicking continue gets the page to load but when searching script tab, Firebug seem to hang, putting Firefox into 'Not Responding`, after a while these unresponsive script alerts appear repeatedly:
chrome://firebug/content/chrome/panel.js:529'
chrome://firebug/content/bti/inProcess/compilationunit.js:77
chrome://firebug/content/lib/url.js:111
chrome://firebug/content/lib/array.js:67
Firebug 2.x seems to be having trouble traversing the large JS codebase...
In debug mode; where JS is not obfuscated & minified - the unresponsive script alerts do not appear, but it appears Firebug is not able to search the multiple files loaded with the non obfuscated & minified code. Searching Script tab puts Firefox into 'Not Responsive', when Firefox comes out of 'Not Responsive', nothing happens...
Have you seen this before with Firebug 2.x against large JS codebases? Is this something the Firebug team are actively working on?
Thanks :)