Transition Q&A

The image resizer code being used on SSA is client side javascript that gets processed after the page has already rendered.
I don't much care for that because it means your perception of the sites rendering speed becomes even more dependent on your browser (and that scripts) behavior than the actual site's performance, and anyone without javascript enabled here wouldn't see any benefit of it.

I'll continue to consider it and possibly put a vote about adding that a secondary option on top of the CSS change I made so that the only time people would see the scroll bars is when they weren't allowing JS or had overriden it's settings.



The container has no way to know the image was spoilered, all it knows is that something is trying to display beyond it's boundaries and that's not allowed to happen, so it makes scroll bars so you can see the whole thing. I could change it to clip instead of scroll, but that's even more annoying. What it really needs is a resize to fit option but that's just not something the current standards support.

I think for rare cases where we have high resolution images it's not that much of a hassle to: "right click, copy img url, open new tab, paste url, enter"
Once we get maple on 1024xIDK we'll probably start seeing more images bigger than the screen.