I still have the previous "jump" session open and continued using it for your debugging proposals:
I'm not sure the jumps I see now are the same. I now reach the bottom of the site and then the batch loads and then the jump happens over that batch. In my previously encountered jumps I was not at the bottom of the site. Please keep this in mind for the following answers:
scroll through, and see if any API requests fail when you experience one of the jumps?
No failing requests. All are green 200 and 204. Jumped posts will get the mark_as_read POST request on scrolling back up past them.
Also, what about any of the feed options? Any of those set?
I have not set them to anything specific. It looks the same except the lower two options are missing for me.
Disable media embeds in the feed and see if that is the issue
Thanks for the additional info. When I switch to my other PC, I'll try to do a run through against feddit.org, scaled sort, with all the options you had set. Hopefully I can reproduce it.
It looks the same except the lower two options are missing for me.
Yeah, Feddit.org is on 0.19.5 and those two options require 0.19.7 or higher, so they're hidden/disabled.
I'm hoping the issue is just with the embeds enabled in the feed. Like I said, that's been deprecated and I rarely test in that configuration. I also have some memory hacks in place that turn those back into thumbnails when they're out of the viewport, so maybe there's a bug in that process when embeds are 'always on'?
If that does turn out to be the case, then the good news is it'll be fixed in 1.4.30 since everything is click-to-play.
Edit: I think I was able to see what you're referring to. It only did it once for me (and I had matched your settings), but I believe I can confidently say that the issue does exist. So, that's progress.
Hypothesis is that when the infinite scroll buffer overflows and it pops the oldest entries from the beginning of the feed, there's some weird behavior with FF (I don't think I've seen this on FF mobile, though).
Will keep testing and see if I can pin that down as the cause or rule it out.
Thanks. I believe that's what I saw, though I could only trigger it once.
I think I know where the problem is, and I've made some changes in 1.4.30 that should address that if I'm right.
Unfortunately, 1.4.30 is a little behind schedule because I wanted to take the opportunity to re-write and clean up the rendering pipeline for the different post media in addition to my other "to do" items and bugfixes. That said, I'm going to have to wait until those are finished before testing the fix properly.
If you'd be willing to run a beta, I can give you a shout when I'm putting the final touches on the next release and you can let me know if that addresses the issue for you. Probably be about a week from now, give or take a few days.
In the mean time, if it gets to be too annoying, the only workaround I can think of would be to disable infinite scroll, set the posts per fetch to 30, close the tab, and relaunch (there's a known quirk when togging infinite scroll).
All good, take your time :)
While it is annoying, the posts don't get marked as already seen which means they just reappear somewhere in the future.
If you'd be willing to run a beta, I can give you a shout when I'm putting the final touches on the next release and you can let me know if that addresses the issue for you.
If I can pull the beta in via a podman tag, I'll happily give it a try.
Not sure if this issue would be a blocker though, as it doesn't seem to be super common for anyone else.