I was kind of leery of making this global because I didn't want it to affect thumbnails on the thread index, since they must be confined to a finite area, whereas in a thread they can flex downward. (The fetched image can be an arbitary size.) But it looks like they don't use the same selector, so should be safe.
Edit: I've updated it to support thread index, inline images, and profile pages and the differing aspect ratios
Alright, I've updated it to 0.0.5 and now it handles both inline and fixed-size index thumbnails. The thumbnails on the index get cropped to fit the hard dimensions of the squares and maintain the correct aspect ratio. In the case of inline images, they just get scaled to 50% of the original size with no constraint on the height.
Alright, those index thumbnails are confined to a 220x145 square, so we can handle those separately by using the cover method of the object-fit property to scale them. Give me a minute to update it...
this removes the ability to view the full size image without auto-media preview turned on. which...also isnt a preview at all, its full size images. Wish this place had click to expand.
Not sure I follow you. I don't have auto media preview on. This only uses the full-size images, it stops loading the downscaled thumbnails from the server. You can click to trigger a modal or you can middle click to open in new tab.
without the script, you click on the thumbnail and it opens the thread, you click the thumbnail again and it opens the full image. But with this script, the thumbnail in the thread is gone and cant be clicked.