IceCubesApp
IceCubesApp copied to clipboard
Feature request: Limit image size to fit on screen in posts
On iPad, posts that contain 1 image are often display "as large, or as wide, as possible". That is, a single image will be the entire width of the post area, no matter the height of the image. This has the effect of sometimes making the image take up the entire screen in portrait, or even more than 1-screen height in landscape (how I often use it). So I can't see the whole image without scrolling. Sure I can open it in a new overlay, but sometimes that really isn't worth it for images I don't care about and want to keep scrolling past. I want to see the whole thing, but it's not an image or post I care to engage with.
I would like a setting to be able to set a maximum image size to display an image, inline on a post. For example if my iPad resolution was 1024x768, the max image height could be set to "700pt/px" so that the image would be scaled down (aspect fit) to that max height I entered. I could even set it to "300pt" and make all images really small. Or perhaps it's set by percentage of screen height, so it's a slider from 100% screen height to ~10% maybe. Additionally, maybe that should also include a max width option. In a perfect world, IceCubes could automatically set the max height/width based on the device screen size, and the orientation I'm holding the device (auto switch between P/L).
If this somehow is already an advaned feature I'm unaware of, tag me with instructions. Thanks!
Screenshot of how I often see images larger than the viewport (v1.7.1)
@JamaicanRumCream We're working on this on #1693.
Great thanks, feel free to close this now.
@Dimillian should I add a setting option to limit the timeline's width? I think that may be a good idea because it makes the layout more balanced. Facebook, X, and many apps(websites) have already done that. More importantly, it is just an option, users can decide what they want.
The first version of the iPad had this. I think I even shipped a few versions with it, but it was weird. We could have it back as an opt-in setting, but I think it could be quite a bit of work to get it working properly.
Worth a try.
Can you tell me how it weird and which version is?