Firefox Pre-Preview Release Available for Testing
Saturday September 11th, 2004
Asa Dotzler writes "We took one more important change into the builds last night, moving from a blacklist to a whitelist for external protocol handlers, so today's builds are the new candidate 1.0PR builds. If all goes well with these builds, they'll become the official Firefox 1.0 Preview Release builds on Tuesday morning. Please help us test these bits and if you find any major regressions, please file bugs and nominate those as PR blockers with the bug flag "blocking-aviary1.0PR?" so that the Aviary team will see.
Note that this is not the final 1.0 Preview Release. That will happen on Tuesday if all goes well with the testing of these candidate builds. We appreciate any and all help testing the candidates and strongly encourage you to report any problems. Only you can prevent buggy releases ;-)"
#39 Re: extension mechanism DID change
Sunday September 12th, 2004 12:42 PM
You are replying to this message
It didn't change afaik (just some bugs were fixed). Anyway, extensions should be checked by their authors and re-shipped (update mechanism provides a mean to update them without re-installing the whole extension but I don't think it works yet). Even if a certain extension is not updated, one could modify it (assuming he/she is sure there are no compatibility issues). Simply open the xpi file as zip and modify "em:maxVersion>xxx" line inside install.rdf. This way, the extension will become "compatible" with the new FF version. Beware that extensions might severely broke user's profile so always keep a copy of the latter.