~emersion/gamja#95: 
Notifications UX

Environment: Generic "Linux desktop" with KDE and Dbus running, Chromium. Chromium uses the native KDE notifications.

When receiving a message, the notification from Chromium/gamja stays around forever, instead of vanishing after some time as it should. One has to manually click X to remove it.

I think the notification should appear for 5 seconds, this is the timeout web clients of some chat services use.

Another thing which would be important for a good notification experience: clicking on the notification should take you to the gamja tab and open the channel with the message the notification was issued by. Again, this mirrors behaviour other services implement and thus is expected by users.

Thank you

Status
REPORTED
Submitter
~prez
Assigned to
No-one
Submitted
3 months ago
Updated
16 hours ago
Labels
No labels applied.

~emersion 3 months ago

I think the notification should appear for 5 seconds, this is the timeout web clients of some chat services use.

I'm not sure. I don't want to miss notifications.

clicking on the notification should take you to the gamja tab and open the channel with the message the notification was issued by

Should already be the case. If not, sounds like a browser or DE issue.

~prez 3 months ago

I'm not sure. I don't want to miss notifications.

Then please make it configurable. Having to manually dismiss every notification is very annoying if you have a lot coming in (especially since they paint over fullscreen applications but you cannot interact with them there - you have to exit the fullscreen application to dismiss them).

Should already be the case. If not, sounds like a browser or DE issue.

I just checked again with gamja master. This is not the case for me. And I think the KDE/Chromium combination is common enough that it could be worth taking another look at this, if you have the time.

Thanks again.

~emersion 3 months ago

Then please make it configurable

Your DE should make this configurable (maybe that's already the case?). That way, no need to add a bazillion of different setting UIs in all applications, there's a single place to configure them.

FWIW, the notification daemon I maintain (mako) supports this.

I just checked again with gamja master. This is not the case for me. And I think the KDE/Chromium combination is common enough that it could be worth taking another look at this, if you have the time.

It might be due to Chromium, IIRC it has restrictions for notifications created outside of web workers. Someone would need to look into all of this again to confirm.

~prez 2 months ago

It might be due to Chromium, IIRC it has restrictions for notifications created outside of web workers. Someone would need to look into all of this again to confirm.

Yes, I think this is the case. From the KDE settings: "This application does not support configuring notifications on a per-event basis". So even with your notification daemon this would probably have to be configurable from gamja itself.

(I also think that a timeout on the notifications would be the saner default to have, as again, this is what other chat services do. But doesn't make sense to debate this)

~emersion 2 months ago

This application does not support configuring notifications on a per-event basis

Not sure what this means. Maybe a gap in Chromium again. mako supports configuring notifications with arbitrary criteria, so should work fine.

~whynothugo 16 hours ago

Unless I’m misunderstanding, ~prez wants a different timeout specifically for this page. I think this is something chrome should implement, not every single webapp out there.

Register here or Log in to comment, or comment via email.