On 7/16/15 19:08, Boris Zbarsky wrote:
Web compat impact for mozRequestAnimationFrame/mozCancelAnimationFrame: Not known for sure, but expected to be small to none. Pretty much any real-life web code that uses this API will also used the unprefixed version or at worst fall back to setTimeout/setInterval. Unfortunately, a use counter would not help much here because of web sites that prefer using the prefixed version to the unprefixed one.
Will we ever run into the same problems with unprefixing rAF raised on blink-dev[1]?
I see 932322 was partially backed out and 943958 seems to describe the `var requestAnimationFrame = window.requestAnimationFrame` problem.
[1] <https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/5S7qeLSXT5Q/aN01cHXbVg8J>
-- Mike Taylor Web Compat, Mozilla _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
