1. Get 117.0.1 https://support.mozilla.org/en-US/kb/install-older-version-firefox 1. Use it to create a new profile using about:profiles 1. Copy in user.js with test id for natural enrollment in the new user experiment 1. Quit 1. Start with the new profile 1. "Check for updates" to get 118 downloaded, but DO NOT RESTART 1. Check `about:studies` to see that natural enrollment has occurred 1. Search `about:config` for 'startup', make sure `browser.startup.homepage_override.once` pref does NOT EXIST or is NOT SET 1. Restart 1. Make sure 118 WNP seen 1. Search `about:config` for 'startup', make sure the `browser.startup.homepage_override.once` pref EXISTS and IS SET to the WNP homepage 1. Restart 1. Check that Moments page is seen Broadly, we'd like to figure out how much of an edge case this is. To help with that, some open questions that would help us assess that include 1. this should presumably affect 118 to 119 updates as well. Does it? 2. do the "search about:config steps" ever fail to return what's written above? If/when they do does it affect what gets shown after the next restart? 3. current hypothesis is that if the browser stays open for 5 minutes after step 7, and then one reloads about:config, that pref should then be set. Is this correct?
Bug 1859437 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
1. Get 117.0.1 https://support.mozilla.org/en-US/kb/install-older-version-firefox 1. Use it to create a new profile using about:profiles 1. Copy in user.js with test id for natural enrollment in the new user experiment 1. Quit 1. Start with the new profile 1. "Check for updates" to get 118 downloaded, but DO NOT RESTART 1. Check `about:studies` to see that natural enrollment has occurred 1. Search `about:config` for 'startup', make sure `browser.startup.homepage_override.once` pref does NOT EXIST or is NOT SET 1. Restart 1. Make sure 118 WNP seen 1. Search `about:config` for 'startup', make sure the `browser.startup.homepage_override.once` pref EXISTS and IS SET to the WNP homepage 1. Restart 1. Check that Moments page is seen Broadly, we'd like to figure out how much of an edge case this is. To help with that, some open questions that would help us assess that include 1. this should presumably affect 118 to 119 updates as well. Does it? 2. do the "search about:config steps" ever fail to return what's written above? If/when they do, does it affect what gets shown after the next restart? 3. current hypothesis is that if the browser stays open for 5 minutes after step 7, and then one reloads about:config, that pref should then be set. Is this correct?
1. Get 117.0.1 https://support.mozilla.org/en-US/kb/install-older-version-firefox 1. Use it to create a new profile using about:profiles 1. Copy in user.js with test id for natural enrollment in the new user experiment 1. Quit 1. Start with the new profile 1. "Check for updates" to get 118 downloaded, but DO NOT RESTART 1. Check `about:studies` to see that natural enrollment has occurred 1. Search `about:config` for 'startup', make sure `browser.startup.homepage_override.once` pref does NOT EXIST or is NOT SET 1. Restart 1. Make sure 118 WNP seen 1. Search `about:config` for 'startup', make sure the `browser.startup.homepage_override.once` pref EXISTS and IS SET to the WNP homepage 1. Restart 1. Check that Moments page is seen Broadly, we'd like to figure out how much of an edge case this is. To help with that, some open questions that would help us assess that include 1. this should presumably affect 118 to 119 updates as well. Does it? 2. do the "search about:config steps" ever fail to return what's written above? If/when they do, does it affect what gets shown after the next restart? 3. current hypothesis is that if the browser stays open for 5 minutes after step 7, and then one reloads `about:config`, that pref should then be set. Is this correct?