Feature #1157
openAllow rendering images below specified size
0%
Updated by Soren Stoutner 8 months ago
What would be the use-case for this feature?
Updated by ask low 8 months ago
I think this FR requires comparison between the size of the image & value in kB provided as limit.
The issue with this feature, is the more images a site has, the more CPU cycles it takes to render images below the limit provided.
I think it's worth implementing as you are trading your little bit of CPU usage to save precious bandwidth, meanwhile still loading the smaller images.
This comes under controlled minimisation of data.
Updated by Soren Stoutner 8 months ago
- Priority changed from 3.x to 4.x
I think the CPU savings would be minimal, or it might even increase CPU usage, because the checking of each image size might end up consuming more cycles than just displaying them.
Also, because this would require making a separate HEAD request before each image GET request, it could also end up consuming more bandwidth rather than less if a website has a lot of small images that end up getting loaded anyway.
In any case, accurately detecting the loading of individual images would require waiting until the 4.x series as stock WebView doesn't provide that functionality.