Lemmy loses scroll position on Android FF

Not new to the Fediverse but new to Lemmy. I've noticed that after viewing a post, navigating back does not restore the vertical scroll position on the previous page. This is happening on latest stable Firefox for Android, but not on FF desktop 123.0. I tried searching but I only found this (not sure if this is even the right project):

https://github.com/LemmyNet/lemmy-ui/issues/1551

Anyone else having this issue on Android and is there anything I can do to mitigate it? Clearing the cache did not change the behavior.

19 points · 9 comments · view on lemmy.world

9 Comments

imaqtpie@sh.itjust.works · 8 pts · 2y (2 replies)

I have been having that same issue for as long as I can remember. Only way to mitigate it that I know of is to simply use an app instead of web UI. Not sure if an alternate front end like Photon or Alexandrite would fix it.

Don_Beefy@lemmy.world · 5 pts · 2y (1 reply)

Here to second the alexandrite suggestion. I have been enjoying it since liftoff was no longer being supported.

sgibson5150@slrpnk.net · 4 pts · 2y

Interesting! I see that my instance has an alexandrite front end [edit: and photon front end!]. I'm learning all kinds of things. Thanks!

user224@lemmy.sdf.org · 3 pts · 2y (1 reply)

Do you touch the screen immediately? I use Opera, and it takes it around a second to scroll back.

sgibson5150@slrpnk.net · 2 pts · 2y

I tried using the back button on the menu instead of the "go back" Android gesture to rule this out. The behavior did not change. Good suggestion, though!

Cloudless@kbin.melroy.org · 3 pts · 2y (1 reply)

In addition to Photon and Alexandrite, consider Voyager too:

https://vger.app/

Don_Beefy@lemmy.world · 3 pts · 2y

Thanks for the suggestion! I'm going to start using voyager on mobile and continue with alexandrite on desktop.

Blaze@dormi.zone · 3 pts · 2y

Same here, and I think it wasn't the case in the previous version of Lemmy? Blurry memories, to be honest

Asudox@lemmy.world MOD · 2 pts · 2y

Locking as this post violates rule 5.