#2312 - Web notification marking as read not efficient
-
By PDStig
- Added
- 5 views
| Identifier | #2312 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Web notification marking as read not efficient |
| Status | Closed (no changes needed) |
| Handling member | Deleted |
| Addon | core_notifications |
| Description | There are several instances where clicking on a web notification doesn't mark it as read like it should. For example, clicking on a notification about a reply on a forum doesn't typically mark that notification as read. Clicking on a periodic content review web notification doesn't mark it as read until you actually do something, like edit that content. I personally think web notifications are "read" after a user sees them (individually, not via. the 5-notification popup), even if the user didn't specifically click the link in the notification or do something regarding it. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
However, in the general case, it's not expected for notifications to automatically mark as read, as that wasn't implemented as one of the features.
I'll therefore leave this topic open for possible future improvements.
So what was the original Composr plan? In other words what would constitute as a "read" notification?
" - you're right. Almost fixed now. Was a block caching issue.
"So what was the original Composr plan? In other words what would constitute as a "read" notification?" - apart from topics, you need to mark them read via the link. I agree with your comments, just it hasn't been done initially and I didn't honestly think of it.