Closed Bug 2056382 Opened 18 days ago Closed 1 day ago

Windows taskbar button icon not reflecting custom browser icon when not pinned

Categories

(Firefox :: Shell Integration, defect, P1)

defect

Tracking

()

RESOLVED FIXED
155 Branch
Tracking Status
firefox154 --- fixed
firefox155 --- fixed

People

(Reporter: yazan, Assigned: yazan)

References

(Blocks 1 open bug)

Details

(Whiteboard: [omc])

Attachments

(2 files)

Prerequisites:

  1. In a recent Windows build, ensure that browser.shell.customIcon.enabled is set to true
  2. Ensure Firefox is not pinned to taskbar, and doesn't have a shortcut in per-user Start Menu directory

STR:

  • Visit about:settings#appearance, and change the default browser icon

ER:

  • Taskbar icon changes

AR:

  • Taskbar icon remains the same
Blocks: 2039322
Flags: needinfo?(mconley)
Severity: -- → S4
Flags: needinfo?(mconley)
Priority: -- → P1
Attachment #9614580 - Attachment description: WIP: Bug 2056382 - Add a shortcut to per user start menu folder so taskbar icon can be modified → WIP: Bug 2056382 - Add a shortcut to per user start menu folder so taskbar icon can be modified. r?mconley,hsohaney
Attachment #9614580 - Attachment description: WIP: Bug 2056382 - Add a shortcut to per user start menu folder so taskbar icon can be modified. r?mconley,hsohaney → Bug 2056382 - Add a shortcut to per user start menu folder so taskbar icon can be modified. r?mconley,hsohaney
Whiteboard: [omc]
Pushed by yalmacki@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/cba4ffe327de https://hg.mozilla.org/integration/autoland/rev/5a12167c19e6 Add a shortcut to per user start menu folder so taskbar icon can be modified. r=mconley,hsohaney,fluent-reviewers,bolsson,mossop
Status: NEW → RESOLVED
Closed: 1 day ago
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch

The taskbar falls back to using the icon of the shortcut (with a matching AUMID) located at the system-wide start menu path, when a matching shortcut doesn’t exist at the user-level start menu. We cannot modify the icon at the system-wide shortcut so it stays the same.

When pinned, a shortcut gets created at the user-level, which we can edit, and hence the problem doesn’t exist there. The fix is to add a shortcut to the per user start menu directory. The shell prioritizes that shortcut’s icon over the system-wide one when both are present, and we have the ability to modify it.

Original Revision: https://phabricator.services.mozilla.com/D313551

Attachment #9623822 - Flags: approval-mozilla-beta?

firefox-beta Uplift Approval Request

  • User impact if declined/Reason for urgency: Users will be not see the browser taskbar icon updating when using the new browser custom icon feature if their browser is not pinned to taskbar
  • 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: medium
  • Explanation of risk level: I flagged this as a medium as we are introducing a new shortcut, which affects where the taskbar icon is being read from. There were initially some concerns of possible affects to taskbar tabs but no issues were identified when reviewing the patch.
  • String changes made/needed?: One string was added but translations were migrated.
  • Is Android affected?: no

adding l10n team for string review especially since it is so late in the beta cycle

Flags: needinfo?(bolsson)
Flags: needinfo?(bolsson) → needinfo?(francesco.lodolo)

Hm. Didn't realize there was a string in this patch. Is it possible to pull from custom.properties directly for the Beta patch? Or is it not packaged in the Firefox omni.ja?

If this was migrating from a Fluent file, it wouldn't be a problem to uplift

Missing .properties strings need to be packaged in the build and langpack, so we shouldn't uplift this patch as is.

Flags: needinfo?(francesco.lodolo)

Actually, now that coffee kicked in… It's OK to uplift this to beta.

I'll run the migration in a few minutes, so translations for the new Fluent string should be in-tree tomorrow. The .properties string is staying around for the time being.

Attachment #9623822 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: