Will try and keep an updated list of features that I am skipping during development to potentially add later ("currently unsupported"):
frame upscaling (section 9.1). not sure if its worth supporting this since I don't think many images would use it. maybe it should just be ignored and the image returned at the encoded resolution, if the user knows there is upscaling (maybe through API? but unlikely. keeping API small) they can upscale themselves using their own method that would probably be faster and better quality than whatever I could come up with.
filter adjustments (section 9.4). I can't seem to get cwebp to generate them anyway
data partitions (section 9.5). There is a way to force cwebp to do it and on initial look it may do it automatically if the file is too large, TODO: add large image test
Coefficient skipping (section 11.1). Should be easy to support just lazy and my test image doesn't have it
Will try and keep an updated list of features that I am skipping during development to potentially add later ("currently unsupported"):
cwebpto generate them anywaycwebpto do it and on initial look it may do it automatically if the file is too large, TODO: add large image test