trop[bot] d074963b30 fix: hex-encode Windows notification icon temp filenames (#50482) ...

* fix: hex-encode Windows notification icon temp filenames

NotificationPresenterWin was using SHA1HashString(origin.spec()) directly
as the basename for the temporary PNG written for toast icons.

SHA1HashString returns raw digest bytes, so the generated filename could
contain invalid path characters on Windows. That caused WriteFile to fail
when saving notification icons, which left toast XML without the expected
icon path.

Hex-encode the digest before appending .png so the temporary filename is
filesystem-safe while keeping deterministic naming for a given origin.

Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>

* Update shell/browser/notifications/win/notification_presenter_win.cc

Co-authored-by: Robo <hop2deep@gmail.com>

Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>

---------

Co-authored-by: trop[bot] <37223003+trop[bot]@users.noreply.github.com>
Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>

2026-03-27 17:07:31 -04:00

..

app

fix: correct linux zygote process titles (#50533)

2026-03-27 12:24:01 -04:00

browser

fix: hex-encode Windows notification icon temp filenames (#50482)

2026-03-27 17:07:31 -04:00

common

chore: bump chromium to 148.0.7751.0 (42-x-y) (#50429)

2026-03-26 17:02:22 -04:00

renderer

fix: InspectorFrontendHost override in embedded windows (#49794)

2026-03-09 10:53:02 +01:00

services/node

fix: recover network requests after Network Service restart (#49887)

2026-02-25 12:53:06 -05:00

utility

fix: broken OOP window.print() on macOS/Linux (#45214)

2025-01-20 10:23:44 +01:00