[wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and use for output

WordPress Trac noreply at wordpress.org
Wed Aug 31 16:54:06 UTC 2022


#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.1
Component:  Media                                |     Version:  6.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-docs needs-user-docs 2nd-opinion needs-  |  performance
  testing changes-requested                      |
-------------------------------------------------+-------------------------

Comment (by eatingrules):

 Also, the [https://make.wordpress.org/core/2022/04/12/follow-up-on-webp-
 by-default-proposal/ April 12 "Follow up on WebP by Default Proposal" blog
 post ] said:

 >Once we’ve completed our investigation and determined next steps on these
 two issues, we will work with the community to reassess two other concerns
 that were raised:
 >
 >1. Having the feature on/off by default
 >2. Having a UI-based control to turn the feature on/off


 I've tried to have a substantive discussion on both of these issues
 (including opening #56263, as @adamsilverstein suggested, which was
 promptly closed and directed back here). Each time the issue has been
 raised, it's been summarily dismissed with, effectively, "we know best" or
 "decisions not options."

 But from what I've seen on this ticket, on the other proposal blog posts,
 and in Github issues, **many** people have been calling for this to be
 opt-in and to have a UI control, and those comments are being ignored as
 well.  It seems the only people pushing against it are on the performance
 team (though perhaps I've missed comments from others who are in favor of
 keeping this hidden from end users?).

 It's time for that follow up blog post to solicit more community feedback
 on these two questions.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:156>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list