Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preferences in private mode doesn't get saved on Firefox. #1149

Open
birbkeks opened this issue Jan 28, 2024 · 7 comments
Open

Preferences in private mode doesn't get saved on Firefox. #1149

birbkeks opened this issue Jan 28, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@birbkeks
Copy link

birbkeks commented Jan 28, 2024

Describe the issue

Authenticator doesn't applies the changes made to private mode, this wasn't a issue on Chromium based or other browsers.

Browser

Firefox

Browser Version

122.0

Extension Version

6.3.5

@birbkeks birbkeks added the bug Something isn't working label Jan 28, 2024
@birbkeks birbkeks changed the title Preferences doesn't get saved on Firefox. Preferences in private mode doesn't get saved on Firefox. Jan 28, 2024
@Sneezry
Copy link
Member

Sneezry commented Jan 29, 2024

See #1085 (comment)

@birbkeks
Copy link
Author

See #1085 (comment)

i forgot that i made that issue before but it is definitely a bug, other addons doesnt loses preferences but authenticator loses theme and and some of the other preferences, while still keeping the auth code and password that has been set. it works normal on normal tabs but on private tabs it uses the default preferences.

@Sneezry
Copy link
Member

Sneezry commented Feb 1, 2024

Could you share some examples of other add-ons that manage to retain user preferences effectively? It would be really interesting to understand how they handle the storage of configuration settings, especially if they're not using local storage. This could give us some great insights.

@mymindstorm
Copy link
Member

mymindstorm commented Feb 1, 2024

@Sneezry they likely use chrome.storage.*. We use localstorage for user preferences and chrome.storage for accounts.

@Sneezry
Copy link
Member

Sneezry commented Feb 1, 2024

@mymindstorm We are transitioning from localStorage to chrome.storage.local in MV3, which will effectively resolve the issue.

@mymindstorm
Copy link
Member

@Sneezry Could we add a version field to the storage to make future migrations easier? If that isn't already there.

@Sneezry
Copy link
Member

Sneezry commented Feb 1, 2024

@mymindstorm Indeed, that's a logical approach. Let's design a schema for the data stored in the storage system, incorporating a version element and flexible attributes to accommodate future expansions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants