Open BenLubar opened 5 years ago
That's the web frontend part resizing.
Removing it will just move the resizing part to the backend which IIRC currently allows up to 4096x4096.
Past this size any incoming picture just shows as a link...
So even removing the frontend resizing won't help much on full web page screenshot for example/long text.
Given the ubiquity of 1080p monitors, 1280x1280 is way too small. Even if the screenshots are from a 4K monitor, it's still 8 million pixels under the backend limit.
Those limits are here for a purpose: pictures are always processed server-side with ImageMagick, which will likely allocate at least one buffer holding all the uncompressed pixels. This limit is at 4096×4096 pixels, after which media files will get ignored.
The resized limit of 1280×1280 may be a bit small indeed, we could definitely increase it.
maybe set the limit to equal the backend limit of 4096x4096? that's not something you're likely to run into (a 1080p full webpage screenshot could be 8738 pixels tall without hitting the pixel limit)
Pitch
There is no reason to limit image dimensions, especially when we are already limiting attachment file size. Remove the source image resizing code from the upload process. (The code is in two files, both named
resize_image.js
)Motivation