What the title says; basically, if you display an image in an iOS browser (say, iPhone) when the image size exceeds a certain limit, the image is reduced and displayed on a portion of the original resolution (i.e. 1/n number of pixels of the original).
This, I think, is a way to avoid browser crashes when image sizes become too large due to lack of memory.
My question is: what is the upper limit on image sizes before the WebView (or browser) starts fetching every nth pixel?
EXAMPLE: When displaying an image of 5760 Γ 1800, it is reduced to 1440 Γ 450 in the browser (1: 4 ratio).
source share