Remove profile-per-install onboarding UI
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox90 | --- | fixed |
People
(Reporter: mossop, Assigned: mossop)
References
Details
Attachments
(3 files)
It has been nearly two years since we implemented profile per install but we are still showing users the attached onboarding experience when they run a new install of Firefox. I think at this point the behaviour is established enough that we can remove this, what do you think Romain?
Comment 1•3 years ago
|
||
Can you please refresh my memory on the exact condition this gets displayed?
ALso quantifying when it happens, I have this query but can you please confirm the "scalar_parent_startup_profile_selection_reason" the scenario here maps to? https://sql.telemetry.mozilla.org/queries/63029/source#161642
Assignee | ||
Comment 2•3 years ago
|
||
(In reply to Romain Testard [:RT] from comment #1)
Can you please refresh my memory on the exact condition this gets displayed?
This happens when starting an install of Firefox for the first time that is either brand new or has been upgraded from a version prior to 67 (released May 21st 2019) and there is already a different install of Firefox on the computer which has claimed the old-style (not per-install) default profile. Then we create a new profile for this install and display this UI on startup. The intent was to show users who had multiple Firefox installs which would have all used the same default profile previously an explanation for why different installs were now getting different profiles.
ALso quantifying when it happens, I have this query but can you please confirm the "scalar_parent_startup_profile_selection_reason" the scenario here maps to? https://sql.telemetry.mozilla.org/queries/63029/source#161642
Ah yes I had forgotten about that telemetry, this is firstrun-skipped-default
or restart-skipped-default
. The restart case would most likely be following an auto-update from Firefox <67 so unsurprisingly the number there is tiny, 27. The other is likely new installs of Firefox and that is at 14,700, which looks to be less than 0.001%.
Now this isn't causing any maintenance hassle that I'm aware of so there isn't any issue with leaving it in, I'm just not sure the message it is giving is correct for the current circumstances. It was really written in mind of explaining what happens as users upgraded and so the modal was important. Now it mostly happens when a user installs a new Firefox.
Comment 3•3 years ago
|
||
Thanks for the details!
I agree that circumstances are now different and users installing Firefox should expect that a new install of Firefox would have a fresh new profile. I'm fine with removing this.
Assignee | ||
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Note: please also remove browser/locales/en-US/chrome/browser/syncBrand.dtd
as part of this patch. This page should be the last consumer of &syncBrand.fxAccount.label
, after bug 1702118 lands.
https://searchfox.org/mozilla-central/search?q=syncBrand&path=&case=false®exp=false
Comment 5•3 years ago
|
||
Any chance we could target this in 90? My main concern is making sure it doesn't end up in the next ESR, otherwise we'll need to support it for another 9 months in our localization toolchain.
Assignee | ||
Comment 6•3 years ago
|
||
Assignee | ||
Comment 7•3 years ago
|
||
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 8•3 years ago
|
||
(In reply to Francesco Lodolo [:flod] from comment #5)
Any chance we could target this in 90? My main concern is making sure it doesn't end up in the next ESR, otherwise we'll need to support it for another 9 months in our localization toolchain.
Yes, sorry I had meant to push this up earlier in the week. I see a string freeze starts tomorrow so I suspect we can't get this into 89 but will land it after the merge.
Comment 9•3 years ago
|
||
(In reply to Dave Townsend [:mossop] from comment #8)
(In reply to Francesco Lodolo [:flod] from comment #5)
Any chance we could target this in 90? My main concern is making sure it doesn't end up in the next ESR, otherwise we'll need to support it for another 9 months in our localization toolchain.
Yes, sorry I had meant to push this up earlier in the week. I see a string freeze starts tomorrow so I suspect we can't get this into 89 but will land it after the merge.
I would definitely merge this after merge day. This won't have a practical impact before we drop ESR78 from our systems, so 90 is more than enough.
Comment 10•3 years ago
|
||
Pushed by dtownsend@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ea3e4e639ef6 Remove profile-per-install onboarding UI. r=Gijs
Assignee | ||
Comment 11•3 years ago
|
||
Updated•3 years ago
|
Comment 12•3 years ago
|
||
Pushed by csabou@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f06480a3358b Remove now unreferenced horizontal-lockup.svg
Comment 13•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/ea3e4e639ef6
https://hg.mozilla.org/mozilla-central/rev/f06480a3358b
Description
•