You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is not related to CM+ itself, but rather to nsICookiesManager interface. You can see it by attempting delete such cookie via built-in cookies manager, it will incorrectly show that cookie was successfully deleted, but after relaunch the cookie manager it will show that cookie again.
In my tests I could delete this cookie right after browser restart, but after a while this cookie created again it can't be deleted again. Also to note, on dev profile in FF50 I could not reproduce this issue, the cookie can be deleted just fine, so it's either they fixed it, or it's related to other installed extensions/plugins or something else.
The text was updated successfully, but these errors were encountered:
don't worry... it's a common issue that the cookies from .google and google can't become deleted or get recreated after the deletion. It seem that there is need to look closer to the code responsible for the deletion, because it's not only one issue releated to it
I'm getting duplicate cookies such as .google.com NID
Turned out the only difference between them is originAttributes data:
appId 4294967294 reference to SafeBrowsing
This issue is not related to CM+ itself, but rather to nsICookiesManager interface. You can see it by attempting delete such cookie via built-in cookies manager, it will incorrectly show that cookie was successfully deleted, but after relaunch the cookie manager it will show that cookie again.
In my tests I could delete this cookie right after browser restart, but after a while this cookie created again it can't be deleted again. Also to note, on dev profile in FF50 I could not reproduce this issue, the cookie can be deleted just fine, so it's either they fixed it, or it's related to other installed extensions/plugins or something else.
The text was updated successfully, but these errors were encountered: