[notifications] configurable? notification expiry time #11
Labels
No labels
a11y
Bug
Bug fix
Critical Priority
Documentation
Feature
Feature request
Held for next release cycle
High Priority
Low Priority
Medium Priority
Minor change
Translation/Locale
WIP
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma-fe#11
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
One of my biggest annoyances with PleromaFE is that desktop notifications ignore my notification daemon's default expiry time and disappear after only a couple seconds.
I prefer to dismiss notifications manually because I like to finish what I'm doing before shifting my attention to the notification; by the time I've finished what I'm focused on, I usually only have time to read a couple words which means I need to go back to my browser and find the tab to finish reading it, rather than just reading the notification itself.
It would be nice if the expiry time was configurable with an option to disable expiry, but I would also be satisfied with just an option to disable the expiry and defer dismissal to the OS.
I've also posted this issue in
pleroma/pleroma-fe
on Gitlab in case it would be better resolved there.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1169
c71405ccad/src/services/desktop_notification_utils/desktop_notification_utils.js (L6-L8)
seems like this was added on purpose?
in any case, this was done two years ago, and there's a good chance this apparent issue in chrome is fixed.
I think it's not the web app's job to handle closing notifications, so I don't see the reason to make it a toggle -- we can just remove that altogether
Yep, I agree completely.
MDN indicates that this has indeed been fixed.