Bug 107097 - Can't change image scaling algorithm from optimize-contrast
Summary: Can't change image scaling algorithm from optimize-contrast
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Images (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Minor
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-16 23:05 PST by Arturo Torres Sánchez
Modified: 2013-02-21 03:23 PST (History)
1 user (show)

See Also:


Attachments
Comparison: Midori left, Chromium right (868.12 KB, image/png)
2013-01-16 23:05 PST, Arturo Torres Sánchez
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arturo Torres Sánchez 2013-01-16 23:05:07 PST
Created attachment 183127 [details]
Comparison: Midori left, Chromium right

I'm doing some test with Apple emoji. I've got images at 160px, but I need them smaller. Since I still don't know how smaller will they be, I didn't use an image editor to resize them.

When I tested images downscaled at 24px in Chromium, they showed fine and smooth. However, testing them in Midori (which uses WebKit), shows them aliased, as if using the optimize-contrast algorithm. So, I opened the Inspector to change the image-rendering property. The only values accepted are “-webkit-optimize-contrast” and “auto”. Trying “optimizeQuality” (which the Inspector autocompleted) showed an “Invalid property value” error, so I'm stuck with jaggy images.

What I'm really curious about is if Chromium also uses WebKit, why does it scale images correctly but WebKit itself doesn't?

I'm using Ubuntu 12.04, with WebKitGTK+ 1.8.3 (which doesn't seem to correspond to any of the versions suggested by Bugzilla).