If a user recieves a notification, it will appear on both the header of
the landing page and in the notification dropdown, icrementing the
corresponding badge count. However, if the user navigates to the location
of said notification from the landing page (esentially reading it),
although it is removed from the landing page, it is not "read" in the
notification dropdown until the user also clicks on the "inbox" icon.
TO TEST: The converse - reading notifications from the notification
dropdown rather than the landing page; does the landing page also not
update?
RELATED:
- https://www.audiotool.com/board/feature_requests/notification_dropdown
- https://www.audiotool.com/board/feature_requests/opening_notification
- https://www.audiotool.com/board/feature_requests/mark_notification_read
- https://www.audiotool.com/board/feature_requests/disable_notifications
- https://www.audiotool.com/board/feature_requests/add_a_menu_to
Comments (4)
UPDATE: I just tested the converse (listed above)
As it turns out, this is definitely a bug because reading notifications from the dropdown does in fact remove them from the landing page.
By "Landing page" do you mean "Activities"? https://www.audiotool.com/newsfeed
I never noticed that anything got removed from this list.
I understood the highlighting as a "new to you"-marker rather than "unread". I receive too many notifications that cannot be "read" in a traditional way. Like "Like XY accepted invitation to YZ". This is more of a timeline than a message inbox.
There is some synchronization missing between the drop-down and the activities list (skimming through one of them should unmark the other). But I'm not sure if this is the issue you're bringing up.
I will try and make a demo illustration as soon as I get home.
I don't mean the entirety of the newsfeed, but the top section of the page that appears after a user logs in (to be precise, according to the underlying code: document.querySelector(".newsfeed.log") I believe).
@mbelow Can you catch this?