Determine why Windows launch on login option sometimes does not show in about:preferences
Categories
(Firefox :: Shell Integration, defect, P3)
Tracking
()
People
(Reporter: nipunshukla002, Unassigned)
Details
Changes were landed in Fx127 to enable launch on login by default. As a result, if I download Release Firefox (128.0.2) with a fresh profile and unenroll from the Launch on Login Treatment A Rollout in about:studies I can see the option in about:preferences. However, there are user reports of seeing the related infobar and messaging system components while being unable to see the checkbox in about:preferences. The way we reveal the checkbox is by checking against the browser.startup.windowsLaunchOnLogin.enabled pref which is set to true by default so some investigation is required here.
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Updated•2 years ago
|
Hi Nipun, do you happen to have details on whether those reporting this issue were on MSIX builds and/or the version of Firefox used?
To decide whether to show the checkbox in about:preferences, we actually rely on both the value of the browser.startup.windowsLaunchOnLogin.enabled pref and this check. This isn't a perfect match to the targeting used for the related in-tree messages.
Another possible route for investigation: It looks like we disabled launch on login for Windows builds in Fx127, then reenabled it in Fx128. It looks like the messages about this feature might not have recieved the corresponding targeting update that would exclude MSIX builds until Fx128.
|
|
Reporter | |
Comment 4•2 years ago
|
||
I'm waiting on a response to whether the reports are on MSIX and which specific version. I'll update the bug with that info as soon as I get it. I think you're onto something with the checks being subtly different and I'll further investigate that. Thanks! Aside from that, I was under the impression that if I modified an in-product message in, for example, Fx127 and then re-enabled it in Fx128 it'd be seamless because a user doesn't actually get the updated message until they update their install to Fx128, when they start seeing the message again. Is that understanding incorrect?
That's right, users will only see in-tree messages landed in their current version of FF or earlier. I didn't dig too much into timeline for changes to the that messages' targeting, so that might not be what's happening here.
Description
•