[Webkit-unassigned] [Bug 86724] New: Animation of quantized CSS properties (e.g. z-index) creates different results in Chrome Vs. Safari

[bugzilla-daemon at webkit.org]

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

           Summary: Animation of quantized CSS properties (e.g. z-index)
                    creates different results in Chrome Vs. Safari
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh
               URL: http://dabblet.com/gist/2718711
        OS/Version: Mac OS X 10.6
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: CSS
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: williamhtrice at gmail.com


Chrome Version: 19.0.1084.46 Vs. Safari Version: 5.1.7 (6534.57.2)
OS Version: OS X 10.6.8
URL: http://dabblet.com/gist/2718711

What steps will reproduce the problem?

1. Visit http://dabblet.com/gist/2718711 in Chrome
2. Visit http://dabblet.com/gist/2718711 in Safari +/ Firefox
3. Compare the different way in which quantised CSS properties (e.g. z-index) are animated by each browser

What is the expected result?

All browsers behave the same.

What happens instead?

In the provided demo, the browser has been asked to animate from z-index 10 to z-index 14. Both Safari and Firefox animate in equal segments from 10 to 14, momentarily arriving at 14 at the very end of the animation. By contrast Chrome animates from 10.5 to 14.5 (rounded to the nearest integer). I'm not entirely sure which developers are doing this right... but I sure know that everyone needs to end up doing it the same. So I'm drawing attention to this disparity between developers in the hope that W3C might firm up the specification and cause everyone to fall in line on this detail of the CSS3 spec.

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