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

WordPress Trac noreply at wordpress.org
Wed Jul 20 23:41:50 UTC 2022

#55443: Create WebP sub-sizes and use for output
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Media                                |     Version:  6.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note needs-docs needs-user-docs commit         |  performance

Comment (by feastdesignco):

 It's extremely clear from the community that this feature is not wanted.
 The response to this has been unanimously negative.

 Suggesting we should "open a ticket" after this is ''forced out'' despite
 near total rejection is ham-fisted and demonstrates how little the
 community feedback actually means to WordPress.

 Whether there should be opt-in or opt-out - and how that's implemented -
 is core to managing this, **before** it's released, not after.

 Suggesting it gets de-coupled is a cheap tactic to force the release of
 this rather than building it properly in the first place.

 This is not ready for production in its current form.

 Replying to [comment:62 adamsilverstein]:
 > Hey Andrew thanks for your feedback and your continued tracking of this
 > > Making these new features opt-in instead of opt-out would be the best
 way to be cautious about potential impacts.
 > The feature will have widespread benefits for users by opting in core
 sizes (to start) - if it were entirely opt-in it would have little impact
 - or benefit.
 > > There have been many requests for this to be opt-in (as well as some
 asking for a setting on the Media page, rather than only a filter for
 developers). So far there hasn't been any open conversation about why
 that's not being taken into consideration.
 > > Perhaps there could be a proposal/conversation to solicit feedback
 from the community about the best way to roll this out?
 > We have discussed both suggestions in chats and issues with mixed
 responses. Project [https://wordpress.org/about/philosophy/ philosophy] is
 regularly mentioned as aligning with the current approach.
 > I would suggest opening a trac ticket to propose adding a UI element
 after the feature has landed which would be a good place to discuss and
 mock up what the UI would look like.
 > Similarly I would decouple the conversation around opt in (or what the
 "default" should be instead of all core image sizes) since that is a
 separate question from whether there should be a UI in core. Open a
 separate ticket to discuss that if you feel that the default should be

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

More information about the wp-trac mailing list