[webkit-dev] Unprefixing requestAnimationFrame
darin at chromium.org
Thu Oct 11 21:59:34 PDT 2012
I agree with what Adam wrote in
https://bugs.webkit.org/show_bug.cgi?id=99116#c5. Even if a lot of sites
will magically failover to the unprefixed API, we can't know for sure that
this change won't break sites. We need to give them a chance to update.
(I don't know if one Chrome release cycle will be enough.)
Why not be conservative here?
On Thu, Oct 11, 2012 at 5:29 PM, James Simonsen <simonjam at chromium.org>wrote:
> I've posted a patch to remove the "webkit" prefix from
> requestAnimationFrame.  The question is whether or not to continue to
> support the prefixed version. I propose dropping it for the following
> 1. We're changing the callback semantics to match the spec. 
> 2. IE10 is shipping with this unprefixed. 
> 3. Toolkits already use the unprefixed version. 
> 4. The advice on the internet recommends everyone use the polyfill
> technique. 
> I'm curious what everyone else thinks.
>  https://bugs.webkit.org/show_bug.cgi?id=99116
>  https://bugs.webkit.org/show_bug.cgi?id=66683
>  http://caniuse.com/#feat=requestanimationframe
>  https://gist.github.com/1579671
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev