-
Notifications
You must be signed in to change notification settings - Fork 5
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
The "Content Blocking" setting is not reset to the previous one after the end of the study #8
Comments
When you move the time forward by one year, you are now testing the shield study utils, and that it unenrolls correctly, it does not. However, we are planning on having Normandy do the actual unenrolling/uninstalling of the addon. |
Thanks @ericawright ! We will wait for the build with the unenrollListener so we can perform another round of testing. Also we will try this out using the Normandy stage server. |
The signed xpi is posted here: https://bugzilla.mozilla.org/show_bug.cgi?id=1522309 |
I have retested this issue using the latest add-on (cookie-restrictions-strict-list-study@shield.mozilla.org-1.4-signed-testing.xpi) version using Normandy stage server tools with the following methods:
After testing each mentioned method the add-on was uninstalled and the prefs were correctly reset to the default ones. However, it seems that the "study_state": "user-disable" ping is sent after the recipe is disabled from the Delivery Console or the recipe automatically expires after a set time. Is this the right behavior, or the "study_state": "expired" ping should be sent instead. @erica Please let us know if you have any methods using Normandy in mind so we can verify this issue. |
[Affected versions]:
[Affected Platforms]:
[Prerequisites]
[Steps to reproduce]:
[Expected result]:
[Actual result]:
[Notes]:
-> network.cookie.cookieBehavior to 4
-> urlclassifier.trackingAnnotationTable to test-track-simple,base-track-digest256,content-track-digest256
-> browser.contentblocking.category to custom
The text was updated successfully, but these errors were encountered: