news
news copied to clipboard
bubelov
Marking scrolled entries as read, marks too much when scrolling up.
Checklist
- [x] I am using the latest version
- [x] I checked, but didn't find any duplicates (open OR closed) of this issue in the repo.
- [x] This issue contains only one bug. I will open one issue for every bug report I want to file.
Steps to reproduce the bug
- Activate the setting mark scrolled entries as read.
- Go to the news tab.
- Swipe down and a few items later swipe up.
- Swipe down and you can see, there are news maked as read, which you could almost not see before.
Actual behavior
When scrolling through the articles, if you scroll back up in between times, articles are marked as read that were minimally visible on the screen before.
Expected behavior
Only the articles that disappear when scrolling up should be marked as read.
--
The bug has existed for several months.
Thanks for your work.
Known issue, the problem is: list items calculate their height before they know the exact size of their images. That allows more items to fit the screen for a moment and that's why they get marked as "seen". After that, they get pushed out of the screen, so the user technically saw them (for a few ms). It's rather annoying, but I don't use this feature and it's not easy to fix. Leaving this issue open in case someone decides to fix it
I don't know much about programming apps myself, but could you possibly fix the problem in which the function "marking scrolled entries as read" is only active when you scroll down the feed. And if you scroll up it is paused for a short time?
This feature is not connected to scrolling, it just checks what's visible on the screen. The easiest solution would be to wait a bit and make sure the content is still visible in, say, 250 ms. That would mean that a news item should be on the screen for some time in order to be registered as "seen". The downside is: quick scrolling will fail to mark some items as "seen", that's why this fix is problematic
I see, then the official news app probably implemented the feature differently or?
@BluePixel4k I haven't seen it, it may use fixed height for all items. That would solve the problem, at least in theory