Bug 1446276 Comment 30 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Hey Criprian, I think you're right, and I think I've reproduced the issue. The steps are probably a variant to the steps impacting Michael, but I think the root of the problem is the same.

What I did:

1. I'm In Canada, so I started with a CA region.
2. Create a new profile. Should see stories.
3. Turn off stories using the mechanism in about:preferences#home
4. Restart the browser (not sure if this is needed, but it's what I did)
5. Set region to DE (this part is important, and what I was missing in previous steps) We're now in a state of DE region in an en-CA browser. This state actually removes the pref (which also means stories are off), vs setting it to false, it seems. You can verify this at this after step 6 by checking about:preferences#home and you should see there is no longer an option to turn stories on or off. And you shouldn't see stories at this point.)
6. Restart
7. Now set region back to CA
8. Restart

Stories are now back and I never set them to be back.

I think the root of the issue is this.

While we have a mechanism in place to ensure a user set pref cannot be changed to another value, it doesn't stop the value from being reset. Once it's reset, it can now be changed again, and the mechanism to prevent user changed prefs from being updates is no longer in place, because the pref is no longer user set.
Hey Criprian, I think you're right, and I think I've reproduced the issue. The steps are probably a variant to the steps impacting Michael, but I think the root of the problem is the same.

What I did:

1. I'm In Canada, so I started with a CA region.
2. Create a new profile. Should see stories.
3. Turn off stories using the mechanism in about:preferences#home
4. Restart the browser (not sure if this is needed, but it's what I did)
5. Set region to DE (this part is important, and what I was missing in previous steps) We're now in a state of DE region in an en-CA browser. This state actually removes the pref (which also means stories are off), vs setting it to false, it seems. You can verify this at this after step 6 by checking about:preferences#home and you should see there is no longer an option to turn stories on or off. And you shouldn't see stories at this point.)
6. Restart
7. Now set region back to CA
8. Restart

Stories are now back and I never set them to be back.

I think the root of the issue is this:

While we have a mechanism in place to ensure a user set pref cannot be changed to another value, it doesn't stop the value from being reset. Once it's reset, it can now be changed again, and the mechanism to prevent user changed prefs from being updates is no longer in place, because the pref is no longer user set.
Hey Criprian, I think you're right, and I think I've reproduced the issue. The steps are probably a variant to the steps impacting Michael, but I think the root of the problem is the same.

What I did:

1. I'm In Canada, so I started with a CA region.
2. Create a new profile. Should see stories.
3. Turn off stories using the mechanism in about:preferences#home
4. Restart the browser (not sure if this is needed, but it's what I did)
5. Set region to DE (this part is important, and what I was missing in previous steps) We're now in a state of DE region in an en-CA browser. This state actually removes the pref (which also means stories are off), vs setting it to false, it seems. You can verify this at this after step 6 by checking about:preferences#home and you should see there is no longer an option to turn stories on or off. And you shouldn't see stories at this point.)
6. Restart
7. Now set region back to CA
8. Restart

Stories are now back and I never set them to be back.

I think the root of the issue is this:

While we have a mechanism in place to ensure a user set pref cannot be changed to another value, it doesn't stop the value from being reset. Once it's reset, it can now be changed again, and the mechanism to prevent user changed prefs from being updated is no longer in place, because the pref is no longer user set.

Back to Bug 1446276 Comment 30