Antifascist! | Pronouns: Any |Age:24| Nonbinary | Furry | Artist | discord: Siio Sytry#7689
You don't understand, I was already about 30% of the way down when I realized my mistake, and then I was just completely adrift with no frame of reference, I had to reload the page
I knew what it was. I knew what to expect. I still opened in a new tab to click show post.
Never had to use the full length of my phone screen for maximum scrolling velocity before
today i have learned that Firefox’s function to save a screenshot of the full page has a maximum vertical resolution of 32767 pixels
PNG can technically go up to 2 billion. I think that 32k is where current image handling libraries give up. They figure that "nobody has enough memory for more than this", or "if you want more, you're solving the wrong problem. Go back and make a tiling system.".
oh! initially i was thinking 16384 pixels isn't that much to scroll on an ultrahd monitor, but apparently the 1px width causes additional fun! the image gets scaled to the full width of the post, and the length expands according to the aspect ratio. excellent multiplication, well done
...I think this image causes floating point errors in Firefox rendering
Oh god it's so bad
I saw this for the very brief moment when you tested it earlier and I thankfully knew better than to open it.
I opened it anyway.
i had the clever thought "i will press End and then scroll up to see if there's something funny at the bottom", and then was completely jumpscared by the image suddenly snapping to fill the whole screen and somehow preventing me from scrolling back down.
This behavior was replicable many times in a row on macos Chrome. It's super spooky. One second only a few pixels of the bottom the post border on screen, the next second you are Permanently In The Void.
Works fine in Firefox, where I was finally able to claim the reward at the bottom of the post ^__^
