Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

RoboForm 6.10.2 not working in Firefox 4.0 release

  • 1 antwoord
  • 69 hebben dit probleem
  • 15 weergaven
  • Laatste antwoord van Domush

JoeM845
JoeM845
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.

Alle antwoorden (1)

Domush
Domush
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.