Potentially unwanted behavior 'mark as read on scroll' marking from bottom as well

[asl97]

Technically as this isn't an issue, So I submitted it here on discussions.

Potentially unwanted behavior of marking from the bottom when scrolling back up.

Reproduction steps

1. ensure 'mark as read on scroll' is enabled
2. scroll down until some feed is off screen
3. scroll up and see the feeds that went off screen gotten marked as read
4. scroll back down and also see the feed that went off screen below was also marked as read

A user might didn't realize scrolling back up also mark feeds as read before switch feed source, which would make locating the accidentally marked as read feed hard to locate, if the user even realizes it.

[spacecowboy]

Working as "designed". It's not a bug.

I agree that it's not ideal. But there is no good way of detecting which way an item is scrolled out.

[asl97]

One way would be to only mark as read when the item is either the newest or oldest unread in the set of feeds, depending on the sort mode.

I ain't sure if such information is available in the part of code handling the function.

[spacecowboy]

don't think it'll work. things don't necessarily happen in order

[asl97]

I don't really see how things might not happen in order?

Using adb logcat and using feeder as I normally do, each of the following event are trigger individually and separated by at least 100ms and averages 500ms part (60fps=16.7ms).

2024-01-14 02:07:09.177  1660-14890 PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:13.878  1660-2738  PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:14.706  1660-14890 PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:15.275  1660-14890 PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:15.786  1660-14890 PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:16.596  1660-14890 PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:18.547  1660-14890 PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:19.194  1660-14890 PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:19.752  1660-5483  PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:20.413  1660-14898 PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:21.487  1660-14898 PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:28.477  1660-5483  PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:28.814  1660-1685  PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:29.093  1660-1685  PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:29.277  1660-2738  PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:29.512  1660-2738  PackageManager          system_server                        D  set app  component=ComponentInfo{com.nononsenseapps.feeder/androidx.work.impl.background.systemalarm.RescheduleReceiver} enabled state: 1 from null,uid=10408,pid=31448
2024-01-14 02:07:29.775  1660-2738  PackageManager          system_server  

it might be worth a try as an setting option 'only mark topmost unread on scroll', it should work well enough in most cases and it's a good behavior for the feature.

If people are swiping so fast that it doesn't trigger the mark as read to end up in the middle of the feed list, the option should make it so that it doesn't continue auto marking any as read until the user scroll back up to the topmost unread feed.

In my assume average cases I can think of, opening the app, switch feed source, after adding a new feed source, the following conditions are all meet:

1. start at the top of the feed list
2. feed is sorted by time
3. the feed goes off screen in order and get triggered in order
   • assuming people scroll at reading speed by keeping the line they are reading the same location on the phone as they read instead of doing big 'page down' kind of movement.
   • I am sure the way I read stuff ain't unique, there are papers that researches this scroll reading concept such as https://dl.acm.org/doi/10.1145/2509315.2509319 , quote:

   • Preferred reading regions on the screen varied among the participants. Most of them preferred relatively short regions.

Big page down movement where it could affect the trigger order would be an unsupported use case for this option and user can just not toggle the option for the current behavior.