Context Navigation

Changes between Version 10 and Version 122 of Ticket #55443

Ticket #55443
- Property Keywords needs-docs needs-user-docs needs-patch 2nd-opinion added; has-patch removed
- Property Milestone changed from 6.0 to 6.1

v10	v122
2	2	This ticket introduces core support for generating and using additional mime types for sub-sized image uploads, with a focus on the WebP format. In addition, it filters frontend content to use the modern format when available for an image. After this change, WordPress will generate and use WebP sub sizes by default when available.
3	3
4		Currently, when users upload images in a supported mime type like JPEG or WebP, WordPress creates sub-sized images of the same type for use on the front end ~~(WordPress does not currently create sub-sized images for TIFF, GIF or PNG images)~~. In WordPress 5.8 we introduced the `image_editor_output_format` filter to enable filtering the mime type used to save images.
	4	Currently, when users upload images in a supported mime type like JPEG or WebP, WordPress creates sub-sized images of the same type for use on the front end. In WordPress 5.8 we introduced the `image_editor_output_format` filter to enable filtering the mime type used to save images.
5	5
6	6	This ticket introduces the capability to generate more than a single mime type. For example, when users upload JPEG images, WordPress can automatically generate both WebP and JPEG sub-sized images. Then WordPress can use the WebP images when serving up the front end. JPEG images are still being generated by default, to support other use-cases outside of common web browsers (e.g. email newsletters) where WebP may not be supported yet.