The second to last article is not marked as read when navigating with key "n" (always)
IMPORTANT
Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)
- [x] I have read the CONTRIBUTING.md and followed the provided tips
- [x] I accept that the issue will be closed without comment if I do not check here
- [x] I accept that the issue will be closed without comment if I do not fill out all items in the issue template.
Explain the Problem
When using the key "n" to navigate through the unread articles, the second to last article is never marked as read even though I navigated past it. This is reproducible every time, and it's always the second to last article.
Steps to Reproduce
Explain what you did to encounter the issue
- click on a folder to update the unread articles of it
- navigate through the unread articles using the key "n" only until reaching the end
- notice that the folder isn't completely marked as read
- scroll back, to a place before the second to last article
- notice that the second to last article is still marked as unread (black, not grey) although all previous articles and also the last article are marked as read (grey)
See attached video to see what exactly I did. I only used the left mouse button (to change/update the folder) and the key "n" (to navigate through the articles) while recording.
System Information
- News app version: 20.0.1
- Nextcloud version: 25.0.3
- Cron type: system cron
- PHP version: 7.4.33
- Database and version: MariaDB 10.5.18
- Browser and version: Firefox 109.0.1
- OS and version: Debian 12 (Bookworm/Testing)
Contents of nextcloud/data/nextcloud.log
[nothing during the time frame in question]
Contents of Browser Error Console
Read http://ggnome.com/wiki/Using_The_Browser_Error_Console if you are unsure what to put hereNo new notification data received [NotificationsApp.vue:389](webpack:///notifications/src/NotificationsApp.vue)
Polling interval updated to 30000 [NotificationsApp.vue:421](webpack:///notifications/src/NotificationsApp.vue)
No new notification data received [NotificationsApp.vue:389](webpack:///notifications/src/NotificationsApp.vue)
Polling interval updated to 30000 [NotificationsApp.vue:421](webpack:///notifications/src/NotificationsApp.vue)
No new notification data received [NotificationsApp.vue:389](webpack:///notifications/src/NotificationsApp.vue)
Polling interval updated to 30000
This also happens with navigation with "j" and "k"
It requires you to click the folder to reload the list again, and then you can mark the final entry as read.