allo-
allo-
Looks like for this type of settings yet another settings store needs to be implemented. Most settings are settings that afaik aren't used by extensions anymore and simple inline files,...
I already see the migration being the next thing that is removed by Mozilla. What I do not understand is that the sqlite3 file contains the settings names as text...
I guess with the requirement to create the storage in the right way it does no longer count as easy. Or may become easy again with #271.
As far as I know, it only gets active after the user confirmed to share his location. If you don't know that it for some reason shares it without consent...
I agree that it may be dangerous and I really wonder why it defaults to not storing any information, because this probably really breaks user expectations. I see it as...
In general I'd like to explain in easy terms what a setting does and why it can break things, so people can understand the trade-off. Currently we have this report...
Just to be sure: Did you check "Remember me" on the login page?
If you did not check Remember me, I suppose that the sessionstore restores your session-cookie and without session-store (or when ending the session) the session cookie is deleted. "Remember me"...
I don't think gitlab uses more than cookies to store the login (session-id). So the store seems to interfere with keeping cookies in some way. If it deletes non-session cookies...
Do you have a suggestion for a replacement? I'd like to have a list that is not static and from a serious and privacy friendly site.