ColdFire 1.2.89.89
This version is an update to both the Firefox extension and the coldfire.cfm ColdFusion debugging template. Below are the highlights for this release:
Better Variable Formatting
Prior to this release we were using the JavaScript Dump Method from NetGrow. While this worked, it was less than ideal because the NetGrow code is designed for debugging JavaScript, not ColdFusion variables that happened to be serialized in JavaScript. So for this release I've rewritten the variable dumping code using Firebug's domplate templating engine, with the end result being that the output in variables tab should match that of <cfdump>.Fallback to Classic or Dockable Debugging Templates
I've gotten this request from a few people so I finally added it to this release. You can now configure coldfire.cfm to include the classic or dockable debugging templates when the ColdFire extension is not available. To do this you just need to make a small tweak to the coldfire.cfm. If you want to fallback to the classic.cfm template, just change the hard coded condition on line 44:<!--- Set to true if you would like to fall back to classic.cfm --->
<cfelseif false>
<cfinclude template="classic.cfm" />
The same is true for dockable, just change the condition on line 48:
<!--- Set to true if you would like to fall back to dockable.cfm --->
<cfelseif false>
<cfinclude template="dockable.cfm" />
</cfif>
Once you make one of the above changes users will see the alternate debugging output if they are using a browser other than Firefox, or if they have the ColdFire extension disabled. (In other words, if you enable an alternate debugging template you can no longer "hide" debugging info.)
Variable Traces and Trace Categories
Before this release the trace panel only displayed output from text traces, i.e. <cftrace text="Hello" />. Variable traces, i.e. <cftrace var="myVar" />, were not encoded by the coldfire.cfm debugging tempalte and thus were not displayed by the extension. This release fixes that and also adds support for the category attribute, so if you happen to assign your trace a category it will show up in the Category column under the Trace tab.
That's it for this release. I already have a few ideas for the next release, but if you have something you really want to see in ColdFire let me know.

It seems that the coldfire plug-in for Firebug v1.1 is missing. I only see the one for Firebug 1.2. The readme doc states their should be a version for each Firebug.
--Dave
If you need a version compatible with 1.1 let me know and I'll send it your way.
Yeah, I still do a ton of testing in FF2 (it's still pretty much my default dev browser.) Oddly enough, it has the largest browser share in our application--so I stick to it for development. So I still use Firebug 1.1 (since 1.2 does not work in FF2.)
Note, I'm not maintaining this version so there are no updates, but it is there if you need it.
I have tried changing the coldfire.cfm file (where it enums the variables into a query) but it does not work. I suspect there are changes to be done to the xpi as well?
Is there anything I can do to make it show all the Application, Session, Form and URL variables?
I do still have a question - if you would be so kind as to answer please...
Just like CFDump, I see you can click on the keys and they expand and collapse.
Is there a way to make the dump "collapsed" by default?
From page to page, the list of variables that I specify dissapears from page to page. Is this to be expected, or is it a bug? - It unfortunately still requires a refresh of the page if it keeps disappearing on each new page.
As for collapsed structure dumps, I'm not sure of an easy way to do that. Again, if it is something you would really like to see please put in an enhancement request and I will investigate it. (The enhancement requests make sure I don't forget about anything when I have time to work on ColdFire.)