Roboform is changing preferences when enabled
I have been using Firefox for years and using Roboform with it for years also, recently i have noticed that my saved passwords in Firefox have not been being used when I log into Firefox and have Roboform enabled. This is a new problem. using Firefox 57.0.2 64 Bit and Roboform 8.4.3.4 Has anyone else noticed this problem
Valitud lahendus
thank you for your response. It appears that this action is designed into RoboForm as noted in this response from RoboForm support
"Natalia replied (2017/12/28 10:09 am EST) Hello Philip,
The behavior described by you is by design in Chrome and Firefox. A user can disable RoboForm extension to enable the built-in password manager in the browser. The user is intended to use either at a time, not both.
Loe vastust kontekstis 👍 2All Replies (7)
https://addons.mozilla.org/en-US/firefox/addon/roboform/ 8.4.38 is current version. Note, the Developer has their own Support page and Contact.
Please go to the 3 Bar Menu ---> Addons then find your Roboform and check the settings for updating and anything else. Go to the Gear Icon at Top Page Right and Click to Update All. Test SAFE MODE
- https://support.mozilla.org/kb/Safe+Mode
- https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
In Firefox Safe mode these changes are effective:
- all extensions are disabled (about:addons)
- default theme is used (no persona)
- userChrome.css and userContent.css are ignored (chrome folder)
- default toolbar layout is used (file: localstore-safe.rdf)
- Javascript JIT compilers are disabled (prefs: javascript.options.*jit)
- hardware acceleration is disabled (Options > Advanced > General)
- plugins are not affected
- preferences are not affected
TEST Create a new profile as a test to check if your current profile is causing the problem.
add your Roboform and test. TEST
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem. Never work with original files.
- https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data
- https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile
- http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox
Please let us know if this solved your issue or if need further assistance.
Valitud lahendus
thank you for your response. It appears that this action is designed into RoboForm as noted in this response from RoboForm support
"Natalia replied (2017/12/28 10:09 am EST) Hello Philip,
The behavior described by you is by design in Chrome and Firefox. A user can disable RoboForm extension to enable the built-in password manager in the browser. The user is intended to use either at a time, not both.
I am glad to hear that your problem has been resolved. If you haven't already, *Please select the answer that solves the problem* YOURS. This will help other users with similar problems find the solution more easily. Thank you for contacting Mozilla Support.
That's really stupid! There is no conflict between the two. For years, I have used Firefox as my primary 'form filler' while using Roboform for higher security passwords. As the USER I should be able to choose between the legacy behavior and this new "I know what's best for you" behavior.
Thanks for the answer. They both work fine in Firefox 53, so Ill just go back to it and the hell with security.
rckmns said
Thanks for the answer. They both work fine in Firefox 53, so Ill just go back to it and the hell with security.
At least consider using Firefox 52 ESR so you will get security updates for a while still and not be so vulnerable with the old Firefox 53.0.3. The 52.9.0esr out on July 3rd is likely to be the last update.
Muudetud
It seems that freedml and rckmns have pointed to the answer. What did FF change between 53.0.3 and the latest versions. Like freedml, I too have always used both Firefox as my primary 'form filler' while using Roboform for higher security passwords and the problem still exists even without Roboform as an extension. Thus it is an issue in FF. Mozilla needs to look at what controls the memory of that option and find out what has changed between 53 & 59