-
Notifications
You must be signed in to change notification settings - Fork 53
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
Cookies Rule Problem #434
Comments
In about:preferences Il have selected "block all third parties". And Firefox says that Chameleon is controlling this setting. But when I, click on Chameleon -> Options -> cookie, the option "Allow All" is displayed. More Precisely, when I set it to "reject third parties", then click on home (chameleon), then goes to options -> cookies, "reject 3rd parties" is still displayed. But when I click elsewhere on my screen, and then go to chameleon/option/cookies, what is displayed is "Allow all". |
@Kraxys I'll have to update how these special preferences are handled. When changes are made to about:config they aren't reflected in the Chameleon UI. I was able to reproduce the issue with "Allow all" appearing, this does seem like a bug. This should be addressed in the next update. |
In fact, despite "Allow all" displayed as cookie rule, when I export my profile, I see:
So it may only be a display problem. The rule effectively applied seems to be "reject 3rd party". |
Hi @Kraxys, Yes, this was a bug in the UI. It should be resolved in v0.21.0. |
Prerequisites
Please use issues for bugs only! Answer the following questions for yourself before submitting an issue: YOU MAY DELETE THE PREREQUISITES SECTION.
Expected Behavior
The cookies rule should remain the one the user has chosen.
Current Behavior
The Chameleon cookies rule is stucked on "Allow all" . When I select a different rule, Chameleon reset it to "Allow all". Strangely enough, the cookies rule in Firefox (Tools->options->privacy) remains set to block all third parties ((I have in FF selected "Custom").
Context (Environment)
FF 79 on W10.
The text was updated successfully, but these errors were encountered: