Nick McSpadden has posted some notes about using the Firefox CCK to manage Firefox 10 ESR here:
http://groups.google.com/group/macenterprise/browse_thread/thread/614aab9bde90485a#
It grates on me that (since about version 8) any time a new version of Firefox is released, I get to choose between the following evils:
- Repackage Firefox.
- Run a script or install an auxiliary package after installing a new version of Firefox.
- Leave Firefox unmanaged.
This problem isn’t so bad if your machines are pretty tightly managed, but if your users can upgrade Firefox on their own or have figured out they can run Firefox from any location they have write access to, then Firefox is essentially unmanageable.
Managing OS X 
If you are re-packaging then you may find the following script to be useful (requires luggage) : https://github.com/henri/luggage-examples/tree/master/firefox/download_modify_and_build
I have just tried the method outlined in the above post for the first time using FF 18.0.1. It turns out the scope changes MUST now live in the /Firefox.app/Contents/MacOS/defaults/preferences folder rather than the ‘prefs’ folder. Mike Kapley’s blog post mentions the change here: – http://mike.kaply.com/2012/10/15/get-ready-for-the-firefox-17-esr/ Hope this helps someone else.
Mike W