Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Toto vlákno bylo archivováno. Pokud potřebujete pomoci, založte prosím nový dotaz.

RoboForm 6.10.2 not working in Firefox 4.0 release

  • 1 odpověď
  • 69 má tento problém
  • 15 zobrazení
  • Poslední odpověď od 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.

Všechny odpovědi (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.