- Issue created by @mstrelan
- π¦πΊAustralia mstrelan
Quick PoC of an image effect with fallback format. Setting to NR for feedback on the approach, please don't send it back for tests/lint/CR etc.
- π¦πΊAustralia mstrelan
Added a test for when AVIF is supported and another test for the fallback. Added a draft CR. This is ready for review.
- πΊπΈUnited States smustgrave
Could the IS get some love. Wouldn't this be considered an API change?
Wonder if a CR is required?
- π¦πΊAustralia mstrelan
Updated the IS to hopefully make it clearer. There is already a CR, are you suggesting it might not be necessary? I think it is useful.
- π¦πΊAustralia mstrelan
Re #5:
Wouldn't this be considered an API change?
It's a new plugin, not a change to an existing one, so no breakage here. You could argue the change to the protected function in GDToolkit is a BC break, but plugins are considered internal and it's a protected method as well, so I don't think it's an issue.
- π«π·France andypost
I find it good/handy feature with CR)
Moreover AVIF is specifically good for big sizes with fallback
- π¬π§United Kingdom catch
Moreover AVIF is specifically good for big sizes with fallback
Not necessarily in this issue, could maybe be a follow-up, would we want to consider some kind of configurable filesize threshold where below a certain point we always skip AVIF and use webp instead? Have seen various discussions that decoding AVIF in the browser is a lot more expensive than webp, which can undo the bandwidth savings with smaller images.
- πΊπΈUnited States smustgrave
Opened up π Consider falling back to webp based on filesize Active for that discussion.