Active
Project:
WebP
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 Mar 2020 at 10:26 UTC
Updated:
4 Apr 2021 at 14:46 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
yorder.be commentedFor the GD-toolkit, I have the following suggestion:
This way we prevent broken images on servers that don't support webp.
Comment #3
alexmoreno commentedfeel free to submit a patch @yoram.derumeaux
Comment #4
grimreaperComment #5
grimreaperHere is the patch.
Thanks for the review.
Comment #6
alexmoreno commentedHi,
thanks a lot for your contribution.
I'm not convinced about this. If GD does not support webp, then it should be flagged on install, and maybe even block said install. Otherwise this could confuse the user as he would be expecting to see a webp image, but instead there would be none?
This is probably related as well:
https://www.drupal.org/project/webp/issues/3126853
Thanks again
Comment #7
alexmoreno commentedComment #8
alexmoreno commentedComment #9
pietermouton commentedHi Alex,
Maybe not: in our case, we have the issue in switching between local/live environments.
Local, we don't use webp. Live, we do use it.
Maybe is adding it as config option (or setting a variable in settings.php) the best option to get around this.
Comment #10
joshua1234511In settings file the following config can be used.
$config['toolkit'] = 'gd';
Comment #11
alexmoreno commentedIMHO, not having configured this in all environments would lead to problems to replicate and missing bugs. I like #10 for a more custom approach if needed
Comment #12
andypostAs core added support for webp it could be handy to keep support of php-imagick as fallback option yo GD option