Linked by Thom Holwerda on Tue 27th Sep 2011 19:45 UTC, submitted by lemur2
Mozilla & Gecko clones Mozilla has released Firefox 7. Unlike releases of Firefox 5 and Firefox 6 which were relatively minor upgrades to the browser, Firefox 7 includes a number of significant improvements, most important of which is probably the drastically reduced memory usage.
Thread beginning with comment 491122
To view parent comment, click here.
To read all comments associated with this story, please click here.
smitty
Member since:
2005-10-13

I think that success rate is only true of release versions. With the alpha version of FF, I know firsthand that disabled plugins have been much worse. However as you indicate, this is because addon developers aren't keeping the version numbers in synch with mozilla's alpha builds, not because a genuine incompatibility exists.

Addon developers who host with Mozilla no longer even need to update the version numbers. Mozilla is doing that automatically, then testing, and reverting back on the couple of percent that are broken.

I'm sure they don't do that for the Alphas, though, so you aren't seeing the benefit.

Reply Parent Score: 2

lemur2 Member since:
2007-02-17

Addon developers who host with Mozilla no longer even need to update the version numbers. Mozilla is doing that automatically, then testing, and reverting back on the couple of percent that are broken.


I'm sure that this is a source of confusion for people.

Almost all of the addons hosted at addons.mozilla.org (AMO) are automatically compatible. Users who get their addons from there will not see a problem. The addons will automatically update on the first run of an updated Firefox.

User who accept or install "addons from all over" will see at least some of their addons disabled after an update of Firefox. Many will simply assume that the Firefox update has "broken" their addons, without realising that if they update Firefox they have to update their non-AMO addons also. Manually.

Mozilla has no control over "addons from all over". Mozilla can't check an addon for compatibility if it is not known to Mozilla. Firefox has to assume that an addon which says it is compatible only with an earlier version of Firefox is not compatible with the newer version, even though it very probably is compatible.

Reply Parent Score: 2

Alfman Member since:
2011-01-28

lemur2,

"User who accept or install 'addons from all over' will see at least some of their addons disabled after an update of Firefox. Many will simply assume that the Firefox update has 'broken' their addons, without realising that if they update Firefox they have to update their non-AMO addons also. Manually."

Well here's the thing, all the addons I've ever installed were managed automatically by mozilla. The FF updates do regularly disable them. This may have something to do with the fact that I'm using an alpha build. I want to be absolutely clear that I am not using manually installed plugins through a third party, these are managed by mozilla themselves.

I switched to the alpha releases about 5 months ago to get the fixed memory leaks and never turned back, but this situation with plugins being disabled is more than a little annoying.

Reply Parent Score: 2