<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>41233</bug_id>
          
          <creation_ts>2010-06-25 16:22:29 -0700</creation_ts>
          <short_desc>REGRESSION: r61173-r61351 - Aliasing of scaled images on resize</short_desc>
          <delta_ts>2010-06-27 14:45:52 -0700</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>Images</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>Mac</rep_platform>
          <op_sys>OS X 10.5</op_sys>
          <bug_status>UNCONFIRMED</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc>http://development.rhubarbproductions.com/scale/The+Losties+HD.jpg</bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords>Regression</keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>0</everconfirmed>
          <reporter name="Kevin M. Dean">kevin</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>hyatt</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>243245</commentid>
    <comment_count>0</comment_count>
    <who name="Kevin M. Dean">kevin</who>
    <bug_when>2010-06-25 16:22:29 -0700</bug_when>
    <thetext>Spin-off of Bug 40904

Resize your browser window to small and load the above link. Aliasing of image occurs when resizing the window which didn&apos;t occur before.

I&apos;ve been told that this is now expected behavior - &quot;An image that is rapidly resizing will use a lower quality interpolation setting until it finishes resizing, at which point it will use a higher quality interpolation.  Performing high-quality interpolation on a resizing image hurts performance.&quot;

A couple of points of contention with that statement.

1. This doesn&apos;t just happen with rapidly resizing, it&apos;s happening with all resizing even if I resize slowly.

2. Low quality until it finishes resizing seems to mean when I release the mouse button, because it doesn&apos;t clean up until after the mouse is released, not when the resizing has settled.

3. Performance wasn&apos;t hurt before on my PPC Mac a few nightlies back, so why sacrifice smoothness and elegance for everyone to cater to the lowest common denominator.

Shouldn&apos;t the low-quality interpolation only kick in when it&apos;s on a low performance device and not for everyone even if they&apos;re on a well performing computer? Could it at least be tiered to detect when it&apos;s below a certain speed in image updates to detect when it should switch to low quality or something like that. There&apos;s got to be a better way than just turning it off.

Firefox doesn&apos;t do it, and Safari didn&apos;t used to do it. It just seems a step back in quality. It also affects javascript-based resizing where it didn&apos;t before.

Go to http://shadowbox-js.com/ and scroll down and click on the Tiger image and the resize your browser to smaller than the tiger picture. Before it was a beautiful thing, scaling smoothly and cleanly as you resized the window. Now it&apos;s just a chunky uglier version of itself, when performance-wise there was no problem before. Just a step back in quality in my opinion. It just seems as we&apos;re moving further into an era where javascript and css manipulations of graphics are becoming more prevalent to throw out quality that was already in place and feature-matched or exceeded the quality of other browsers.

Thoughts?</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>