Bug 68775 – -webkit-optimize-contrast: a need of behaviour rethought?

• Component: New Bugs
• Status: RESOLVED INVALID

[asiekierka]

I've been trying to develop a website using -webkit-optimize-contrast for nearest-neighbour scaling, and I noticed a major behavioural difference:

Firefox (and possibly IE): Changing the scaling to nearest-neighbour affects the image with any width and height, and zooming the page in/out also uses nearest-neighbour.
WebKit (in this case, Chromium 13 with WebKit 535.1 and Google Chrome 15 with WebKit 535.2): Changing the scaling to nearest-neighbour requires you to specify the width and height EXPLICITLY, on top of that zooming the page in/out keeps using bilinear/whatever is default.

My question is, as this brings a lot of confusion: Why was this behaviour chosen? And, if there is no good reason, is there a chance this could be changed?

Example: http://i.imgur.com/3dvyF.png

[asiekierka]

(Note: http://guyspin.64pixels.org is a test site. It upscales images from 40x56 to 80x112. The screenshots are a result of visiting that site and zooming it in.)

[asiekierka]

(In reply to comment #1)
> (Note: http://guyspin.64pixels.org is a test site. It upscales images from 40x56 to 80x112. The screenshots are a result of visiting that site and zooming it in.)

Dammit! I forgot that the images ARE already 80x112, so the normal upscaling is pretty much useless.

[asiekierka]

(In reply to comment #2)
> (In reply to comment #1)
> > (Note: http://guyspin.64pixels.org is a test site. It upscales images from 40x56 to 80x112. The screenshots are a result of visiting that site and zooming it in.)
> 
> Dammit! I forgot that the images ARE already 80x112, so the normal upscaling is pretty much useless.

Set the bug as INVALID as the non-crisp edges are merely an aestethic thing.