Push notifications miss host name on title in Linux KDE environment with Plasma
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: murznn, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0
Steps to reproduce:
When Firefox receives a push notification, Plasma Notification misses host information of this push notification, so it's impossible to understand which website sends it.
Same feature with Chromium works well - I see the host in notification header.
STEPS TO REPRODUCE
-
Take any Linux system with KDE Plasma session.
-
Open https://push-notifications-demo.netlify.app/ in Chromium.
Send a push notification, see that in notification header hostname (push-notifications-demo.netlify.app) is present. -
Open https://push-notifications-demo.netlify.app/ in Firefox.
Send a push notification, see that in notification header hostname (push-notifications-demo.netlify.app) is missing.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.04
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Actual results:
Hostname in not visible, and it's impossible to understand the source of the notification (domain name).
Seeing the host name of PUSH notification is especially necessary to find the real source of too spammy PUSH sources! Cuz many websites subscribes people to PUSH spam :(
Expected results:
Hostname must be visible to understand the source of the notification.
Chromium seems sends it in separate kde-specific dbus field (caught using dbus-monitor):
dict entry(
string "x-kde-origin-name"
variant string "push-notifications-demo.netlify.app"
)
But Firefox doesn't do it.
So the solution is to add this field to dbus notification.
Here https://chromium.googlesource.com/chromium/src/+/f418f24c72a3fabc8bd236a141f1d043d217bc01 is Chromium patch with implementing that feature.
Can we add similar thing in Firefox too?
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Description
•