-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*.jpg
is not generated for scaled full size image.
#122
Comments
*.jpeg
is not generated for full size image.
*.jpeg
is not generated for full size image.*.jpg
is not generated for full size image.
*.jpg
is not generated for full size image.*.jpg
is not generated for scaled full size image.
Thanks so much for the report! The original full size uploaded image (in JPEG) should still be there (as is listed in the meta under "original image"). My understanding is that the intent is for WebP to be the primary format when that module is enabled, so this sounds to me like the intended behavior. It sounds like the behavior is inconsistent, though, between uploading an image larger/smaller than the @adamsilverstein What do you think? |
That's correct, full-size image is still uploaded as specified on the meta but is the full-size image tho not the scaled version with the maximum dimensions set by WordPress. Additionally, I think using the original image as a fallback does not provide a performance benefit, on the contrary, it loads a nonoptimized image in terms of size and quality to a device where modern images are not supported and instead a more appropriate size should be loaded as a fallback instead. |
Fixed in #143 |
Related with the following core ticket: |
Steps to replicate
2560
orbig_image_size_threshold
(Use attached image)*webp
extension for the full size image.Image meta data stored in WordPress
Metadata of the image.
This happens due to the new "full size" being scaled down to match the threshold from WordPress and prevents having a fallback
*.jpg
for thescaled
size (full size).Image used for testing this behavior.
The text was updated successfully, but these errors were encountered: