-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Cookie AutoDelete extension installation doesn't sync with Firefox Sync #369
Comments
You are talking about the extension itself right and not the extension settings like in #30 |
That's correct. The extension itself. |
It seems like it's a browser bug. Let's see if other people report the same. |
Is there anything I could try or test for you in the meantime? All my other extensions sync, just not this one. |
In case it helps, I've found another extension that has this same issue: Temporary Containers. |
This may or not be related but both Temporary Containers and CAD use the Containers API. |
Deleted my previous comment, as it was on the wrong issue. Temporary Containers finally synced over, but CAD still has not. I've seen other reports, so I think this issue is already reported for Firefox. I'll check, and report it if not. |
Having the same issue, CAD does not sync to other profiles. |
I installed the extension on my Windows 10 machine and it does not get synced to either the other Windows 10 machine or the Ubuntu 18.04 one. |
It seems as if this is no longer a problem, at least for me. Closing. Reopen if it's still an issue for others. |
Describe the Bug/Feature
When I install most other extensions from "Firefox Add-ons", I can then sync Firefox on my other computer and the extensions I installed on the first computer will automatically install on the second. This extension does not do that. Everything else syncs fine: other add-ons, preferences, open tabs, etc. Am I doing something wrong, or is this extension specifically not syncing?
Steps for anyone to reproduce the bug
Your settings
The text was updated successfully, but these errors were encountered: