100% guessing here, but native apps sometimes use recycling virtualized lists. That means as you scroll the list will reuse the container that renders the post title and image. Often the image is still being fetched but you already know the title. So as you scroll, it reuses a post you previously saw, instantly swaps in the new title, but the new image is still loading, so an image from a previously post in the list is displayed.
the result is you many only need to render and reuse 10 posts in the list, even if the list contains hundreds of posts.
Idk if that made any sense at all, but keep an eye out if the title is new but the image was previously seen.
Yeah, that's why key props are important. And sanity checks too. But too many programmers these days just turn off eslint rules without understanding why they exist
I’m not a recycling list expert, but I think the more keys you use the less react is able to reuse components in the list. So this is one area where keys are actually worse. You may be able to use them only on the image part of the post, but packages like expo-image have a recyclingKey prop you are supposed to use instead. But I found expo image to not work very well so 🤷
But I think think the app we were referring to isn’t react native? Idk how native recycling lists work tbh so maybe you’re right about the key thing.
16 replies
Must have been some darn fine curry.
I don't get that, what client are you using?
Eternity. Only happens once in a while, like every couple of weeks.
It's a known bug of Eternity. You have to live with it, or switch to Voyager.
I think it happened on Infinity back in the Reddit days as well
Never happened to me on Jerboa!
Which makes sense for an Eternity bug
But someone mentioned it also happening on Voyager? So it seems that it happens on both, and doesn't happen on Jerboa
Happens here too
100% guessing here, but native apps sometimes use recycling virtualized lists. That means as you scroll the list will reuse the container that renders the post title and image. Often the image is still being fetched but you already know the title. So as you scroll, it reuses a post you previously saw, instantly swaps in the new title, but the new image is still loading, so an image from a previously post in the list is displayed.
the result is you many only need to render and reuse 10 posts in the list, even if the list contains hundreds of posts.
Idk if that made any sense at all, but keep an eye out if the title is new but the image was previously seen.
Yeah, that's why key props are important. And sanity checks too. But too many programmers these days just turn off eslint rules without understanding why they exist
I’m not a recycling list expert, but I think the more keys you use the less react is able to reuse components in the list. So this is one area where keys are actually worse. You may be able to use them only on the image part of the post, but packages like expo-image have a recyclingKey prop you are supposed to use instead. But I found expo image to not work very well so 🤷
But I think think the app we were referring to isn’t react native? Idk how native recycling lists work tbh so maybe you’re right about the key thing.
Needs more coconut milk.
That used to happen on reddit.
https://safereddit.com/r/softwaregore/comments/7l05tg/reddit_still_hasnt_fixed_the_thumbnail_problem_ugh/
This is a lemmy’s sir
I know, but its funny that it carried over here.