Roboform already release his compatibility, if you install popular addon from addons.mozilla, we try to increase compatibility always before release

Link to latest Roboform version: http://www.roboform.com/platforms/browsers/firefox

If this reply solves your problem, please click "Solved It" next to this reply when signed-in to the forum.

Not related to your question, but...

You may need to update some plug-ins. Check your plug-ins and update as necessary:

• Plug-in check --> http://www.mozilla.org/en-US/plugincheck/
• Adobe Shockwave for Director Netscape plug-in: Installing (or Updating) the Shockwave plugin with Firefox
• Adobe PDF Plug-In For Firefox and Netscape: Installing/Updating Adobe Reader in Firefox
• Shockwave Flash (Adobe Flash or Flash): Updating Flash in Firefox
• Next Generation Java Plug-in for Mozilla browsers: Installing or Updating Java in Firefox

gentlemen, thanks for the replies but it looks like I wasn't clear enough in my original post.

I'm fully aware of how to update plugins. My point is that I don't want to touch a firefox update if (key) plugins (eg and especially Roboform) aren't yet ready (which is often the case). I do NOT want to find out AFTER I've permitted a firefox update that the plugins are incompatible.

I wouldn't dream of doing that to my own users and I can't imagine how and why Mozilla haven't addressed the issue before now. It's basic common sense.

I've also written to Roboform about the issue, in case Mozilla prove unable or unwilling to address the issue and asked them to make it clear on their download page, the latest versions of the supported browsers which have been tested with their software. They are considering this request as we speak.

Harry,

Firefox has the ability to automatically update installed add-ons during the Firefox program update process, but the add-on developer needs to use that feature in their add-on. This process works best when the add-on is hosted at the official add-ons website (as Swarnava mentioned in his response), but Firefox will look for an update and install it from any secure HTTPS server that the add-on developer specifies in the install.rdf file in their Firefox add-on.

Third-party products/software (i.e., Roboform, Adobe Flash, RealPlayer, Firewall-AV/AS products, etc.) should be checked periodically by the user for updates. Some third-party products, including Roboform, install an Add-on (toolbar or other) into Firefox. Keeping third-party products updated is as important as keeping your OS updated.

As for Roboform and their version compatibility page: http://www.roboform.com/support/news (information that I found on the internet indicates that Roboform 7.6.3 was released on 11/10/2011 - two days after Firefox 8 was released. Many/most third-party vendors will not release updates until or shortly after the formal public release of a new version of Firefox).

For example, as of the date of your original question, you need to update the following third-party products that have installed "Plug-ins" into your Firefox:

• These would be covered in the bottom section of my post "Not related to your question, but... You may need to update some plug-ins."
  • Shockwave Flash 11.0 r1 (aka Adobe Flash) - you are at least one/several updates behind
  • Adobe PDF Plug-In For Firefox (Adobe Reader) - you are at least one/several updates behind
  • Next Generation Java Plug-in 1.6.0_20 (Java) - you are 9 updates behind
• The QuickTime Plugin - you need to check with the QuickTime site
• Foxit Reader Plug-In - you need to check with the Foxit site
• npFFApi - part of ZoneAlarm Toolbar; you need to check with their site. Current version is 10.1.065.000.

If this reply solves your problem, please click "Solved It" next to this reply when signed-in to the forum.

nobody is addressing the actual issue I am raising.

I'm fully aware of how the update process works - including third party addons

The design flaw I'm addressing is the Firefox update procedure itself. Telling us that an addon is incompatible AFTER the update is as useful as a chocolate teapot.

We need to know BEFORE THE FIREFOX UPDATE PROCEEDS whether or not key addons (of our choice) are already compatible. If they are not, then we should simply have the option of delaying the update until the addons have caught up.

To achieve this, we need an additional option in the Addon manager which says something like "Delay Firefox Update (and warn user) if Addon is incompatible with update".

We could then mark the relevant key addons and be assured that, come the next firefox update, it would check the compatibility status of those marked addons before proceeding with the update. If if found any not yet ready, it would warn the user that the update could not be carried out without disabling the addon (and give the user an option to proceed regardless, if, for instance, the user decides the benefits of updating firefox - eg to fix a major security flaw - outweigh the inconvenience of losing the addon for a few days)

I hope that is clearer now.

un'king believable. Both Roboform and Firefox claim that RF version 7.64 is compatible with FF 8.01. So I stupidly went ahead and installed FF8.01 and then RF 7.64. FF refused to enable RF. So I then reinstalled FF7.01 and then reinstalled RF 7.64 again. Now FF 7.01 is refusing to enable RF...

Jeez...

The problem was caused by firefox not "releasing" the reference to the previous version of RF and insisting that the version suitable for FF 7.2.3 was still installed. No amount of installing the RF update would fix that, but manually REMOVING the addon from FF then allowed the RF update to install properly in both FF 7.01 and 8.01.

The question is: whose fault was that? FF or RF? Or, perhaps more usefully: who is best placed to fix it? FF or RF?

I think the root probem still is UNSOLVED. I understand the requestor for this problem, goofed in checking the addon updates, but still the problem persists.

For e.g., in my case, I am a fulltime user, and a fan of Tab Utilities Lite addon. Now this is incompatible with my the latest version of firefox. Firefox updates to latest version without my permission, without knowing he mess it creates??

Sorry if I have missed out a basic thingy here.