Open Bug 1496650 Opened 8 years ago Updated 4 years ago

WinTaskbar::GetAppUserModelID doesn't return valid AppID on 64-bit Firefox when 32bit Firefox is installed

Categories

(Core :: Widget: Win32, defect, P3)

Unspecified
Windows
defect

Tracking

()

Tracking Status
firefox64 --- affected

People

(Reporter: m_kato, Unassigned)

References

Details

(Whiteboard: widget-next)

Although I have landed bug 1155505 to support toast notification API, I found rarely environment that still uses XUL alert even if Windows 10 ver 1809. This API requires valid AppID. But this environment doesn't use valid AppID. So when I debug this, WinTaskbar::GetAppUserModelID returns false even if there is HKLM/Software/Mozilla/Firefox/TaskBarIDs. Since this environment installed Firefox 32bit (now it was alyready uninstalled), there is HKLM/Software/WOW6432Node/Mozilla/Firefox/TaskBarIDs as garbage. So WinTaskbar::GetAppUserModelID should read native registry only (don't read WOW6432Node).
Blocks: 1497425
See Also: → 1500054
Priority: -- → P2
Priority: P2 → P3
Whiteboard: widget-next

Is this still an issue?

I think this may have been fixed by https://bugzilla.mozilla.org/show_bug.cgi?id=1602195, which added a fallback to do runtime generation of the AUMID if it's not found in the registry.

Flags: needinfo?(m_kato)

If user uses 32-bit Firefox on 64-bit Windows, I think that this issue is still existed. But our Firefox installer will update to 64-bit if windows is 64bit version. So this is low priority (or we can resolve this as WONTFIX).

Flags: needinfo?(m_kato)
Assignee: m_kato → nobody

(In reply to Makoto Kato [:m_kato] from comment #2)

If user uses 32-bit Firefox on 64-bit Windows, I think that this issue is still existed. But our Firefox installer will update to 64-bit if windows is 64bit version. So this is low priority (or we can resolve this as WONTFIX).

This is true, but only for users with more than 2GB of RAM (and also doesn't happen for the full installer at all). I agree it's not super high priority, but AUMID is getting more and more important, so we should probably address this if it's not already fixed...

Assignee: nobody → nrishel
Status: NEW → ASSIGNED
Whiteboard: widget-next → [fidedi-notifications]
Status: ASSIGNED → NEW
Whiteboard: [fidedi-notifications] → widget-next
Assignee: nrishel → nobody
No longer blocks: 1497425
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.