Comment on Anyone else get the thing where images and post titles become confused? It can often be humourous.
JesusTheCarpenter@feddit.uk 2 months ago
I don’t get that, what client are you using?
Comment on Anyone else get the thing where images and post titles become confused? It can often be humourous.
JesusTheCarpenter@feddit.uk 2 months ago
I don’t get that, what client are you using?
Diddlydee@feddit.uk 2 months ago
Eternity. Only happens once in a while, like every couple of weeks.
gigachad@sh.itjust.works 2 months ago
It’s a known bug of Eternity. You have to live with it, or switch to Voyager.
LainTrain@lemmy.dbzer0.com 2 months ago
Never happened to me on Jerboa!
gigachad@sh.itjust.works 2 months ago
Which makes sense for an Eternity bug
Flax_vert@feddit.uk 2 months ago
I think it happened on Infinity back in the Reddit days as well
afk_strats@lemmy.world 2 months ago
Happens here too
moseschrute@lemmy.world 2 months ago
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 landing so an image from a previously post in the list is displayed.
Idk if that made any sense at all, but keep an eye out if the title is new but the image was previously seen.
Kaboom@reddthat.com 2 months ago
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