How does it know if the image is just going to be displayed and can therefore be recompressed vs when the image is used for data? For example many WebGL apps have data in PNGs because they are normal maps or heighmaps. Mucking with the data will mess them up.
Other apps store data in their PNGs. For example Monoco encodes its saved game files as screenshot PNGs and stores the save data in the lower order bits of each pixel. Mucking with the data would make it impossible to load saved games.
Is there a way for a page to opt out for these cases?
AFAIK there's no way to specify a header from standard HTML and it's highly unlikely that most people will have access to the servers that serve their content to set these headers on a per file basis
Other apps store data in their PNGs. For example Monoco encodes its saved game files as screenshot PNGs and stores the save data in the lower order bits of each pixel. Mucking with the data would make it impossible to load saved games.
Is there a way for a page to opt out for these cases?