Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

RoboForm 6.10.2 not working in Firefox 4.0 release

  • 1 réponse
  • 69 ont ce problème
  • 15 vues
  • Dernière réponse par Domush

more options

Is RoboForm 6 supposed to work with FF 4? If so, how do I make this happen?

Neither the Mozilla site or RoboForm's site seems to comment on this. I have had no luck with more general searches.

I have been using RoboForm Pro 6.10.2 with Firefox 3.x successfully. I installed FF 4.0 as released. Now RoboForm shows up on the toolbar, but only pops up a page where I could buy version 7. I tried reinstalling RoboForm with no change in behavior. There is an .XPI that some have suggested in posts on similar problems, but it is set for RoboForm 7.2.3.

Is RoboForm 6 supposed to work with FF 4? If so, how do I make this happen? Neither the Mozilla site or RoboForm's site seems to comment on this. I have had no luck with more general searches. I have been using RoboForm Pro 6.10.2 with Firefox 3.x successfully. I installed FF 4.0 as released. Now RoboForm shows up on the toolbar, but only pops up a page where I could buy version 7. I tried reinstalling RoboForm with no change in behavior. There is an .XPI that some have suggested in posts on similar problems, but it is set for RoboForm 7.2.3.

Toutes les réponses (1)

more options

When I went to save a file in firefox, the toolbar started working once the save as dialog popped up. It is definitely a bug in 6.10.2's toolbar code. Hopefully they fix it ASAP.