Username/password save broken in browser? (2.1.0.11)
In 2.1.0.11/Iijoki & JollaC it seems that the browser does not really save login/password pairs, even when it is asked and user clicks 'Save'. When accessing the same (https) login page again, the same saving question pops up every time. And this is in standard, not private browsing mode.
Peculiarly, /home/nemo/.mozilla/mozembed does contain key3.db and logins.json, but the latter does not seem to be updated. signons.sqlite is also missing, but that's likely deprecated already.
logins.json only contains
{"nextId":1,"logins":[],"disabledHosts":[],"version":1}
Did you use the cookie manager in Defender app? I had the exact same problem after trying that.
eson ( 2017-04-16 08:57:21 +0200 )editNo, this is relatively fresh install (after factory reset), no openrepos repositories installed nor any tweaking w/ about:config.
twi42 ( 2017-04-16 10:10:38 +0200 )editOk, then maybe it will be enough to reinstall browser.
eson ( 2017-04-16 11:13:43 +0200 )editNope, same behavior after browser reinstall.
twi42 ( 2017-04-16 15:46:33 +0200 )editAs you found, this is the same as:
https://together.jolla.com/question/159660/bug21011-cant-update-saved-password-in-webbrowser/
As well as the mozilla profile, the browser stores some stuff here:
~/.local/share/org.sailfish/sailfish-browser/
including bookmarks. I've looked in sailfish-browser.sqlite and I know it contains history, but I don't know what else. Passwords maybe?
Looking at the file dates in the profile folder it seems some of it is unused, and that may be true of passwords. My guess - and only a guess - us that anything involving the SFOS GUI, as password saving does, has been reimplemented.
DaveRo ( 2017-05-04 09:49:44 +0200 )edit