[wp-trac] [WordPress Trac] #21668: WordPress still does not save jpeg as progressive jpeg

WordPress Trac noreply at wordpress.org
Mon Sep 16 01:14:41 UTC 2013

#21668: WordPress still does not save jpeg as progressive jpeg
 Reporter:  _ck_                               |       Owner:
     Type:  enhancement                        |      Status:  new
 Priority:  normal                             |   Milestone:  3.7
Component:  Media                              |     Version:  3.4.1
 Severity:  normal                             |  Resolution:
 Keywords:  has-patch 3.7-early needs-testing  |

Comment (by pmeenan):

 Replying to [comment:22 nacin]:
 > While progressive JPEGs can be smaller, they are not always desired from
 an aesthetics standpoint.
 > I am not inclined to support [attachment:21668.5.patch] as it appears to
 change functionality, and/or increase the requirements for GD or Imagick
 to be used. Please correct me if I am mistaken on these points.

 It doesn't change the requirements for GD or Imagick.  The only change is
 to set the progressive flag in cases where GD or Imagick were already
 being used to save JPEGs (resize or edit).

 As far as the asthetics go, I can't really say because I'm not aware of
 any studies that have been done to evaluate end-user's perception of
 either baseline (top-down rendering) or progressive.  I do know lots of
 individual developers have strong opinions one way or another and there
 are plenty in both camps but I'm not aware of any data either way.

 I do have data backing the faster visual experience (not just of the
 blurry initial passes) but that doesn't really address user perceptions
 and asthetics.

Ticket URL: <http://core.trac.wordpress.org/ticket/21668#comment:23>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list