Fix for Taskbar Grouping / AUMID Collision on Windows (Portable versions)

[anonymous3210]

Preliminary checklist

• I have read the README
• I have searched existing issues for my feature request. This is a new issue (NOT a duplicate) and is not related to another issue.
• I have searched wont fix issues and this request is not among them
• This is a feature request for the Cromite browser; not the website nor F-Droid nor anything else.

Is your feature request related to privacy?

Is there a patch available for this feature somewhere?

.

Describe the solution you would like

Problem Summary

Portable Chromium forks (like Cromite and Ungoogled Chromium) are being grouped together in the Windows Taskbar because they share the same internal AppUserModelID (AUMID) and Window Class. Users cannot fix this via shortcuts because the engine overrides the identity at startup.

Proposed Technical Solution

To ensure Cromite is treated as a unique entity by the Windows Desktop Window Manager (DWM), the following changes are needed at the engine level:

1. Modify install_static: Update kCompanyPathName and kProductPathName in chrome/install_static/chromium_install_modes.cc from "Chromium" to "Cromite".
2. Unique AUMID Logic: In chrome/browser/shell_integration_win.cc, ensure the AUMID generation appends a unique "Cromite" identifier. For portable builds, consider hashing the execution path into the AUMID to prevent collisions between different instances.
3. Custom Window Class: Change the hardcoded Chrome_WidgetWin_1 string in ui/views/win/hwnd_util.cc to Cromite_WidgetWin_1.

This would natively isolate Cromite from other Chromium-based browsers without relying on user-side workarounds.

Describe alternatives you have considered

.

[uazo]

Thank you for letting me know.