Linked by Thom Holwerda on Thu 15th Dec 2011 16:56 UTC
Thread beginning with comment 500235
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2007-02-17
Firefox is testing my patience with a new (n+1).0 version every month, that breaks all the Add-ons (and Add-ons was one of the reasons for using Firefox).
I want the freedom to decide if and when I will upgrade. I also expect good backwards compatibility and a sensible version numbering scheme.
Firefox doesn't break add-ons ... although some addons (hosted external to addons.mozilla.org) do break themselves.
By this I mean that addons themselves check the browser version that they are running under. If the browser versions says it is higher than expected by the addon, the addon simply declares ITSELF incompatible, whether it actually is, or not.
In truth, well over 99% of addons will still work fine under a new version number, even if the addons themselves think they won't. You can download a tool from the addons.mozilla.org site, called the Addon compatibility Reporter, that will force a recalcitrant addon to run even if the addon has declared itself incompatible. This tool will let you re-instate the majority of addons that have refused to run under a new browser version.