graphical bug when using up down navigation arrows
I cant reproduce this bug currently but here is what happened:
Somehow I stretched the hight of the text. I think this happens when scrolling up?
I used the arrow buttons down and up, and when I navigated down the text was frozen to be elongated.
So somethink stopped the text from bouncing back to normal hight, something that has to be in relation to the navigation buttons.
I've seen this too. It's pretty rare, but very strange. I think you're on the right track about how it happens. Good to have this for tracking although it'll be hard to fix. 😄
I've only seen this a few times but just managed to catch a screenshot for the first time. It's tough because it goes away if you do anything. This was the post. I think I opened the post and immediately scrolled.
Screenshot_20230923-185132_Thunder~2
(0.2.4 on Android 13, btw.)
I've had this happen a handful of times when scrolling, but I just had it appear after posting a comment and not subsequently scrolling at all. Before posting the comment I had scrolled to the end of the thread and used the reply button (which was then near the top of the screen), not the FAB.
I just saw this again using while the "Back To Top" button in the FAB on 0.3.0-1. And unlike the last cases I commented about, I can get it to reproduce, and it stays stretched after touching the screen and scrolling. I scroll all the way to the bottom of the post, long-press the FAB and tap "Back To Top."
Posts where it reproduces are here, here and here.
edit: After realizing that the three example posts linked above may end up getting more replies and becoming longer, I found a few older posts where the issue easily reproduces: post 4, post 5, post 6
After observing that the posts where it was reproducible were ones with sort of "mid-length" comment threads, and that it wasn't reproducing on longer or shorter threads when starting from all the way at the bottom, I wondered if I could reproduce this on a longer comment thread by simply scrolling down "enough" (like, the equivalent length of one of the posts I linked in my last comment) and then using "Back To Top." The answer is actually... yes. It only seems to matter approximately how far the scrolling distance is, and not that the scroll necessarily starts from the bottom of the post.