sasquatch wrote:... No. On starting a new release of Firefox the first time, you get a dialog informing you which extensions and themes were disabled. It also provides an update button. Besides, disabled extensions are still listed in the extension manager and can be updated by clicking the update button.
So, the procedure is to restart with new version, attempt to update, if no updates available take your chances with old version?
I believe that the problems with themes and extensions listed with too low a max version has been fixed in the newest build (2004-06-24). I imagine the same will be true with 0.9.1.
ehume wrote:I believe that the problems with themes and extensions listed with too low a max version has been fixed in the newest build (2004-06-24). I imagine the same will be true with 0.9.1.
The browser displays an error message that it will not install the theme. There is no option to override.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040624 Spacegecko/0.9.0+
(Trust me, it's June 24 build with a couple of extensions installed :-)
In case some have missed it, Ben edited the first post of this thread...
Updates: - the visual display version number will read "0.9.1" but since the update system works poorly at present (the generic web service is not yet deployed on update.mozilla.org) the extension app version will remain 0.9.0. This should not be a problem as there are not major changes that would cause extensions to break. - We are taking only the fixes above plus a few other critical issues. Other bugfixes that have taken place on the aviary branch-trunk ("brunk") since 0.9 was released (such as the new security indication etc) will not be included to minimize QA issues.
Steffen wrote:vfwlkr, I think one of the reasons for the new extension management is to avoid installing outdated extensions which break the app.
so just bump the EM version number any time you make a change that would make extensions incompatible. don't bump the EM version when you release a new version of FF that lets old extensions still work. I'm pretty sure that's what vfwlkr meant. the question is, how easy would it be for the devs to determine for sure when they've made changes that render old extensions incompatible. if that's too difficult, it makes this solution impractical.
bengoodger wrote:and the wacky infinite restart loop
... and some updates to Winstripe.
We'll have candidates available for testing available shortly. .
I have a feeling that after getting 0.9 off their shoulders, the devs are working with much better efficiency. Yes, that happens to me too when I finish off my finals and start back the research work.
Whoa! Major upgrade to Winstripe! It looks good! I'm quite impressed with the primary five icons. I will miss the directional triangles. I thought they were a neat "different" feel, but the new forward and back arrows are just great. Refresh looks super. So does "stop." The house is pretty standard fare, although much more like Qute than Winstripe's first take at it. Losing the low-laying shadows was probably a good choice, considering how non-Windows-y that style of shadow is.
I'm... still... waiting... for the <strong>new</strong> "new tab" icon -- one that <em>doesn't</em> look like a toaster. Other "secondary" icons I'm assuming will be updated to fit more with this style?
But seriously, this is great. Small icons look good, too! Great job to Gerich and Horlander! It seems there was a dramatic response to feedback generated regarding the theme.
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.