To read all comments associated with this story, please click here.
They *work*, but often the developer of the extension just fails to update the extension to include the new version of Firefox as compatible. You either have to wait for the developer or use the Nightly Tester extension to override.
I don't think there's much of an elegant solution to it, besides perhaps Firefox building-in auto-update functionality for extensions (which currently does not exist).
No, same here and everywhere, of course.
When I read "Current users of Firefox 1.x should not use Firefox 2 Beta 2 and expect all of their extensions and plugins to work properly." I thought "Is this something new?"
It is one of the most unnerving feat^^bugs of Firefox, moreso given how often it is updated. The extensions system are one of this browser's greatest selling points and at the same time its greatest annoyance. I vent^^wrote about this in a short piece
http://www.nezmar.com/minefield-and-the-extensions-mess/
when trying out Minefield, a version of Firefox tailored for Mac OS X.
nda
when trying out Minefield, a version of Firefox tailored for Mac OS X.
Minefield isn't a version tailored for OSX, it is the trunk. IOW, it is what will someday become Firefox 3.0 and is currently very, very, very far from even alpha status. Which is why they called it "Minefield." You never know when it will blow up in your face.
I don't know how people can complain about 3rd party extensions not working with a pre-alpha or even beta product. Start complaining when they don't work with the 2.0 final release. Until then, if you expect things to work then you shouldn't be using betas anyway.






Member since:
2006-04-21
...or do extensions and plugins often fail to work between one *release* version and another, anyway?