Bug 89849 - Use InterpolationLow on chromium-android
Summary: Use InterpolationLow on chromium-android
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Adam Barth
URL:
Keywords:
Depends on:
Blocks: 66687
  Show dependency treegraph
 
Reported: 2012-06-24 21:55 PDT by Adam Barth
Modified: 2012-06-25 15:01 PDT (History)
4 users (show)

See Also:


Attachments
Patch (2.87 KB, patch)
2012-06-24 21:56 PDT, Adam Barth
no flags Details | Formatted Diff | Diff
Patch (2.85 KB, patch)
2012-06-25 10:12 PDT, Adam Barth
no flags Details | Formatted Diff | Diff
Patch for landing (2.86 KB, patch)
2012-06-25 10:22 PDT, Adam Barth
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Barth 2012-06-24 21:55:05 PDT
Use InterpolationMedium on chromium-android
Comment 1 Adam Barth 2012-06-24 21:56:32 PDT
Created attachment 149236 [details]
Patch
Comment 2 Min Qin 2012-06-24 22:39:05 PDT
LGTM.
Thanks for the patch
Comment 3 Stephen White 2012-06-25 09:18:42 PDT
Comment on attachment 149236 [details]
Patch

Medium and Low both map to bilinear interpolation on the Skia path.  While this path is fast, it does generate some pretty ugly aliasing, especially noticeable when downsampling (e.g., twinkling during animation).  This decision should really be looked at by a person on the Chrome/Android team (unless Min Qin is, I'm not sure from the ChangeLog).
Comment 4 Adam Barth 2012-06-25 09:21:13 PDT
Yeah, Min Qin is works on chromium-android and originally made this change to the chromium-android branch.  I can't speak to whether this is a good idea, but it is what's currently happening on the chromium-android branch.
Comment 5 Min Qin 2012-06-25 09:41:51 PDT
On chrome on android, we noticed that there are lots of white blocks when scrolling image heavy sites. The problem is caused by slow image decoding and resampling. Changing to bilinear interpolation greatly increase the resampling speed (almost unnoticeable).
The display for android devices is comparatively small (4'-10') compared to that of 20'-30' desktop. Decent image quality degration is tolerable on such small screens.
Comment 6 Stephen White 2012-06-25 09:55:11 PDT
(In reply to comment #5)
> On chrome on android, we noticed that there are lots of white blocks when scrolling image heavy sites. The problem is caused by slow image decoding and resampling. Changing to bilinear interpolation greatly increase the resampling speed (almost unnoticeable).
> The display for android devices is comparatively small (4'-10') compared to that of 20'-30' desktop. Decent image quality degration is tolerable on such small screens.

OK, cool.  In that case, could I ask that you use Low rather than Medium?  Although they currently both do linear, I have some plans to implement a new resampling method and map Medium to it.
Comment 7 Min Qin 2012-06-25 10:03:14 PDT
Thanks for the update.
Adam, would you please make the corresponding change in upstream?
Comment 8 Adam Barth 2012-06-25 10:12:01 PDT
Created attachment 149313 [details]
Patch
Comment 9 Adam Barth 2012-06-25 10:12:18 PDT
Done.
Comment 10 Daniel Bates 2012-06-25 10:20:25 PDT
Comment on attachment 149313 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=149313&action=review

OK

> Source/WebCore/ChangeLog:15
> +          non-noticable on the trace.

Nit: noticable => noticable [sic]

(since the word noticeable is misspelled)
Comment 11 Adam Barth 2012-06-25 10:22:10 PDT
Created attachment 149316 [details]
Patch for landing
Comment 12 WebKit Review Bot 2012-06-25 15:01:43 PDT
Comment on attachment 149316 [details]
Patch for landing

Clearing flags on attachment: 149316

Committed r121184: <http://trac.webkit.org/changeset/121184>
Comment 13 WebKit Review Bot 2012-06-25 15:01:57 PDT
All reviewed patches have been landed.  Closing bug.