Synchronize browser.shell.customIcon.id between selectable profiles
Categories
(Firefox :: Shell Integration, task)
Tracking
()
People
(Reporter: mconley, Assigned: mconley, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [omc])
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
This preference is what's used to select the icon on startup of a new profile, and is how we show the selected icon in about:settings. Since all selectable profiles will be sharing the same custom icon, we should synchronize this pref.
Syncing this might also fix bug 2056386, since the pref is being used at startup to choose which icon to use - we should check that once this one is fixed.
| Assignee | ||
Comment 1•17 days ago
|
||
Updated•17 days ago
|
Hey, I know this is patch to make e.g. 2057059 less buggy until each profile can have its own AUMID. But I think it may be a regression. I find it less stressful to identify different profiles with distinctive whole icons (retro, pixelated, Momo) than with the tiny top-right inharmonious icons (a leaf, a soccer ball) introduced with the new profile system. Even if they don't combine like I reported on 2057059.
Updated•13 days ago
|
Updated•13 days ago
|
Comment 5•5 days ago
|
||
Backed out for causing TV and xpcshells failures at customIconManager.js
Backout Link
Push with failures
Failure Log
Failure line TEST-UNEXPECTED-CRASH | browser/components/shell/test/unit/test_customIconManager.js | Test crashed
Comment 7•4 days ago
|
||
| bugherder | ||
Comment 8•4 days ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: Clients that use the new browser icon customization mechanism will find that their selectable profiles "go out of sync" about which icon to show, which is confusing.
- Code covered by automated testing?: yes
- Fix verified in Nightly?: no
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: This change is restricted entirely within the custom icon mechanism, which is inert unless the user actually chooses to customize / change their browser icon.
- String changes made/needed?: None.
- Is Android affected?: no
| Assignee | ||
Comment 9•4 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D313752
Updated•4 days ago
|
Updated•4 days ago
|
Comment 10•4 days ago
|
||
| uplift | ||
Description
•