[Webkit-unassigned] [Bug 68775] New: -webkit-optimize-contrast: a need of behaviour rethought?

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=68775

           Summary: -webkit-optimize-contrast: a need of behaviour
                    rethought?
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Enhancement
          Priority: P3
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: asiekierka at gmail.com


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

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.