Opened 6 years ago
Closed 2 months ago
#50256 closed defect (bug) (invalid)
Inconsistent image handling in wp_create_image_subsizes.
| Reported by: | ddur | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Media | Version: | 5.3 |
| Severity: | major | Keywords: | reporter-feedback close |
| Cc: | Focuses: |
Description
New "big image handling" uses $editor->resize() which will not only resize, but also loosely compress JPEG image (degrade image quality) by invoking $editor->thumbnail_image() inside $editor->resize().
Rotating image below "big image handling", about line 322 in image.php uses $editor->maybe_exif_rotate(), which will not further degrade image quality.
Until WP version 5.3, media editor page was always starting with original/upload image quality, which is not case after WP 5.3+ "big image handling" is triggered.
IMHO, media editor page should never get "thumbnalized" image as starting point for further editing by user.
Change History (3)
This ticket was mentioned in Slack in #core-media by antpb. View the logs.
4 years ago
#3
@
2 months ago
- Keywords close added
- Resolution → invalid
- Status new → closed
I dont think this is an issue. The thumbnails are not created from the scaled image (though they arguably should be, by default, to significantly reduce processing). They are created from the original image.
The original image is also stored still, alongside the -scaled image.
Given this, and the lack of follow-up for 6 years, I'm closing this. Feel free to re-open if there's some extra information that you can share!
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Hello @ddur thank you for your ticket ! Can you give us a reproduction outline step by step? (maybe some example files too!)
I'm trying to understand what the bug is you are seeing and the expected results. Some reproduction steps with an example file would be very helpful! Thank you!