Small images don’t show metadata on hover because they do not lightbox, that is, the entire image fits in the post.
The behavior feels slightly inconsistent at least, since multiple images on the same post offer metadata on hovering or not depending on whether they are small or large, but for the reader at this point there’s no distinction between such images because they’re all the same size. The behavior feels arbitrary.
I’d suggest showing at least the details on hovering, irrespective of the image size. Then perhaps not expanding for those which are small.
No plans for this and it is not on our current roadmap in any form. I also don’t agree.
On top of that it would be super irritating to see “metadata” on this image
Indeed, most people don’t care about metadata on bananas.
The behavior was unexpected and surprising because the images were all about the same size, and then the divergence of a few pixels meant a completely different user experience when hovering over the image. Felt broken.
Same issue discussed here
I agree people dont want to see metadata on dancing bananas or little robots (so they wont click on it) but they might want to check out a close up view of a chart, a UFO sighting, or something (and will click it).
How about a threshold that let’s the little bananas/robots and other images coexist? Just doesnt seem very Discoursey on small devices the way it is now on mobile with default no zom. Maybe not so easy that the team should drop everything.
BTW, I really like the way images get lightboxed with the slide show arrows. I am assuming those edge case images that are not light boxed get left out. At least there wont be any bananas or robots but that’s what the threshold is for.
Yeah, that’s the exact same issue. Besides the zooming aspect, it’s also unsettling to see two images next to each other, looking pretty much as the same size on the user screen, part of the same post and same context, but behave differently for unclear reasons. By design or not, feels like a bug.
You can zoom at all times in iOS on Mibile Safari so that is no longer a valid criticism.
Behavior on Android is exactly the one @scombs describes.