chore($$raf) Remove support for moz prefixed requestAnimationFrame

[realityking]

According to can I use this would drop support for the following browsers:

• Firefox 22
• Chrome 23
• Safari 6
• iOS 6.1

Note, they don't have data on Blackberry 10.1 (where it's prefixed) and 10.2 (where it's unprefixed).

This is also the same level of support as provided by jQuery.

[realityking]

According to #6526 and c839f78 Android 4.3 would still need a vendor prefix. Outside of AngularJS issues/commits I could find no evidence that Android 4.3 even supports rAF. Does anyone have access to a device running that version who could check?

[Traxmaxx]

@realityking Checked on a Android 4.2.2 device inside the WebView through Cordova 3.5.0-0.2.7:
$window.webkitRequestAnimationFrame and $window.webkitCancelRequestAnimationFrame are defined. Will check with Android 4.3 tomorrow.

Update: WebView on Android 4.3 has $window.webkitRequestAnimationFrame and $window.webkitCancelRequestAnimationFrame defined too.

[realityking]

Well that sucks. Thank you very much @Traxmaxx.

I've modified the commit to only remove support for the moz prefix, not sure if that's worth it.

[realityking]

Could someone review or close this?

[googlebot]

CLAs look good, thanks!

[caitp]

@matsko what do you think? FF22 was never an ESR release, so there aren't likely to be any large pools of users on it

[caitp]

@realityking do you think you could find the mozilla bug where the prefix was dropped? it would be good to include that in the commit message to help justify this

[caitp]

https://bugzilla.mozilla.org/show_bug.cgi?id=909154 I guess I misread this bug, the prefix is not dropped yet, but they want to remove it --- so we probably should land this

[matsko]

LGTM