Chromium uses the Desktop Notifications specification¹ to display notifications².
It sets the app_icon parameter, and according to the specification³, « The "app_icon" parameter and "image-path" hint should be either an URI (file:// is the only URI schema supported right now) or a name in a freedesktop.org-compliant icon theme (not a GTK+ stock ID). »
So a file:// prefix is expected, and correct.
Can you share more details on the problem? Maybe use dbus-monitor to watch the notifications coming in, and share the value of the app_icon parameter?
Chromium uses the Desktop Notifications specification¹ to display notifications². org-compliant icon theme (not a GTK+ stock ID). »
It sets the app_icon parameter, and according to the specification³, « The "app_icon" parameter and "image-path" hint should be either an URI (file:// is the only URI schema supported right now) or a name in a freedesktop.
So a file:// prefix is expected, and correct.
Can you share more details on the problem? Maybe use dbus-monitor to watch the notifications coming in, and share the value of the app_icon parameter?
¹ https:/ /developer. gnome.org/ notification- spec /source. chromium. org/chromium/ chromium/ src/+/master: chrome/ browser/ notifications/ notification_ platform_ bridge_ linux.cc; l=582 /developer. gnome.org/ notification- spec/#icons- and-images- formats
² https:/
³ https:/