This thread was archived. Please ask a new question if you need help.
signon.rememberSignons preference does not work after 62.0
Hi! After updating to Firefox 62.0 seems to preference signon.rememberSignons does not work anymore. It was set using defaultPref as unchecked, but in 62.0 it appear as selected. Also, seems to lockPref does not work. Confusing for many users. Any ideas? More thanks, Alar.
All Replies (12)
Separate Security Issue, please update your Flash 27.0 r0 by removing it with this tool : https://helpx.adobe.com/flash-player/kb/uninstall-flash-player-windows.html If you use it Reinstall with Flash Player Version: 126.96.36.199 Current Version https://get.adobe.com/flashplayer/otherversions/ Step 1: Select Operating System Step 2: Select A Version (Firefox, . . . .) Note: Other software is offered in the download. <Windows Only>
Do not know any thing further than below, all info archived will need to see below or wait for someone that knows.
https://support.mozilla.org/en-US/products/firefox-enterprise Should maybe find some info here as is new home of MDM Web Docs.
Ok, fixed it, thanks. We'll wait then for someone to reply on subject. Alar.
Can you provide more details on your usage of signon.rememberSignons?
I assume you mean in autoconfig?
It's possible your autoconfig is not being read at all because of sandbox and you need to set a pref for that.
Do you see errors on the console?
^Quote: Do you see errors on the console?
Note that this is about the Browser Console.
Hi and thanks! Sorry for delay. Yes, using autoconfig. Can’t say about console, must study it, but no other settings missed, as far I’m aware of. More thanks, Alar.
I've verified that signon.rememberSignons is definitely the pref that maps to "Asl to save logins and password for websites"
The signon.rememberSignons pref should work in an autoconfig file (I use it myself, but with a defaultPref() call), so if it isn't working then something else is wrong. That is why I suggested to check the Browser Console for right-click context menu.
Can you post the content of the autoconfig file?
You aren't using GPO or a policies.json file that might interfere?
Hi and thanks! Well, yes, nothing to-do with named in subject preference. “ReferenceError: Components is not defined”. Used in cfg one “components” and as this became obsolete (at least for using in cfg as used to) … error and rest of cfg wasn’t processed. … Why not just to ignore such obsolete references by design!? More thanks, Alar.
Modified by MozAlf
This is because autoconfig is sandboxed by default on Firefox 62.
Add the pref
general.config.sandbox_enabled and set it to false in autoconfig.js
What are you using Components.classes for?
This is because autoconfig is sandboxed by default on Firefox 62. Add the pref general.config.sandbox_enabled and set it to false in autoconfig.js What are you using Components.classes for?
Hi and thanks! Yes, I read out about sandbox’ing and tried also pref You mentioned, but … probably couldn’t set it work properly. Anyway, I used “Components.classes["@mozilla.org/toolkit/crash-reporter;1"].getService(Components.interfaces.nsICrashReporter).submitReports = false;”, from old time. No more “components” involved. More thanks, Alar.
Hi and thank You! Yes, as soon I find it (~ code) out and wasn’t able to get it work by using other means I commented it out, not so important to have it there, I think. More thanks, Alar.