New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Chrome native notifications #375
Comments
I'd guess chromium behaves the same and I tested it yesterday on chromium: In general a notification server can support "capabilites". In the thread there said, that Only forcing chromium helps doing this. |
Hm, from what I see in the source the only capabilities required are |
@tsipinakis Maybe @hobarrera can tell you more he participated in the thread. |
Sorry, there's not much more that I can add. The patch that does the blacklisting itself is here. My C++ isn't good enough to follow through, but maybe you can find something relevant. |
Actually, it seems the
The latest stable release of dunst returns this: |
Wait, so you guys are saying that notifications posted by chrome should not be display via dunst? The two entries starting with p.s. that's chrome 61 but has been working every since google introduced native notifications on linux. |
@JesseFarebro What version are you running can you verify that you're using one that supports native notifications? @tadly Can you provide a dbus-monitor dump starting with closed chrome and receiving a notification? Just to have an idea on how chrome behaves from launch to notification sending and actions. The icon thing may be related to #339 if you're on the latest stable. |
@tadly could you also please provide the setting of the flag |
@tsipinakis if you tell me how to, sure. Never used any of the dbus tools nor did I ever work with dbus itself. Would save me a lot of time :) Also, icons do generally work. Chrome is the only one I've noticed it not doing so (I don't get a whole lot of notifications on linux though) @bebehei |
Just close chrome entirely, run |
@tsipinakis Didn't know where else to put it but here you go... https://pastebin.com/uS6bJn4q |
So that's the reason for it. Can you please test, that "default" does not show notifications? @tsipinakis For me, this looks like an implementation bug of chrome. dunst provides all required caps and it looks like chrome behaves wrong in its "default" behavior. |
@bebehei Can confirm. Setting it back to default gives me chromes notifications again. |
@tsipinakis Running Chrome 61, latest version. I do have #enable-native-notifications enabled and when I run Anything else you can suggest? |
Comment from the sources of the last stable chromium:
So as you can see this behavior is intentional, while Mac uses native notifications for "Default", Linux does not and requires the flag 😞.
On the latest master the icon is still not showing when notification is sent by chromium (e.g. by this website). As it was mentioned, images are present when notifications are sent by other apps, so it must be something to do specifically with chromium. @JesseFarebro I noticed that if I run UPDATE: I discovered that this is the right way to enable this flag via CLI arguments: |
The flag has been enabled by default and will ship in Chromium 64. The notification shows the generic Chrome icon when using 64.0.3278.0 (dev channel). |
@slokhorst Thanks for notifying us. As the feature is now shipping downards the stream and will released at the end of January, I'll close this issue. The missing icons probably are related to #447. I can say for sure, that a new dunst release is shipped out before chromium. |
Just wanted to get a discussion going to see what kind of work would be needed to support Chrome's native notifications. It seems dunst supports most of the capabilities Chrome needs but dunst is still being blacklisted in Chrome.
More discussion can be seen here: https://bugs.chromium.org/p/chromium/issues/detail?id=676220
The text was updated successfully, but these errors were encountered: