OLD | NEW |
(Empty) | |
| 1 ### 1.0.5 - *January 6 2015* |
| 2 |
| 3 * Fix loading the polyfill in an SVG document |
| 4 * Fix a problem where groups didn't take effect in their first frame |
| 5 * Don't rely on performance.now |
| 6 |
| 7 ### 1.0.4 - *December 8 2014* |
| 8 |
| 9 * Fix a critical bug where deprecation logic wasn't being loaded |
| 10 when `web-animations-next` and `web-animations-next-lite` were |
| 11 executed on top of a native `element.animate`. |
| 12 |
| 13 ### 1.0.3 - *December 4 2014* |
| 14 |
| 15 * Fix a critical bug on iOS 7 and Safari <= 6. Due to limitations, |
| 16 inline style patching is not supported on these platforms. |
| 17 |
| 18 ### 1.0.2 - *November 28 2014* |
| 19 |
| 20 * Deprecated `AnimationTiming.playbackRate`. |
| 21 |
| 22 For example, this is no longer supported: |
| 23 |
| 24 var player = element.animate( |
| 25 keyframes, |
| 26 {duration: 1000, playbackRate: 2}); |
| 27 |
| 28 Use `AnimationPlayer.playbackRate` instead: |
| 29 |
| 30 var player = element.animate( |
| 31 keyframes, |
| 32 {duration: 1000}); |
| 33 player.playbackRate = 2; |
| 34 |
| 35 If you have any feedback on this change, please start a discussion |
| 36 on the public-fx mailing list: |
| 37 http://lists.w3.org/Archives/Public/public-fx/ |
| 38 |
| 39 Or file an issue against the specification on GitHub: |
| 40 https://github.com/w3c/web-animations/issues/new |
| 41 |
| 42 ### 1.0.1 - *November 26 2014* |
| 43 |
| 44 * Players should be constructed in idle state |
| 45 * `play()` and `reverse()` should not force a start times |
| 46 * Add `requestAnimationFrame` ids and `cancelAnimationFrame` |
| 47 |
| 48 ### 1.0.0 — *November 21 2014* |
| 49 |
| 50 The web-animations-js hackers are pleased to announce the release of |
| 51 a new codebase for the Web Animations Polyfill: |
| 52 https://github.com/web-animations/web-animations-js |
| 53 |
| 54 The previous polyfill has been moved to: |
| 55 https://github.com/web-animations/web-animations-js-legacy |
| 56 |
| 57 The new codebase is focused on code-size -- our smallest target is |
| 58 now only 33kb or 11kb after gzip. |
| 59 |
| 60 We've implemented native fallback. If the target browser provides |
| 61 Web Animations features natively, the Polyfill will use them. |
| 62 |
| 63 We now provide three different build targets: |
| 64 |
| 65 `web-animations.min.js` - Tracks the Web Animations features that |
| 66 are supported natively in browsers. Today that means Element.animate |
| 67 and Playback Control in Chrome. If you’re not sure what features you |
| 68 will need, start with this. |
| 69 |
| 70 `web-animations-next.min.js` - All of web-animations.min.js plus |
| 71 features that are still undergoing discussion or have yet to be |
| 72 implemented natively. |
| 73 |
| 74 `web-animations-next-lite.min.js` - A cut down version of |
| 75 web-animations-next, removes several lesser used property handlers |
| 76 and some of the larger and less used features such as matrix |
| 77 interpolation/decomposition. |
| 78 |
| 79 Not all features of the previous polyfill have been ported to the |
| 80 new codebase; most notably mutation of Animations and Groups and |
| 81 Additive Animations are not yet supported. These features are still |
| 82 important and will be implemented in the coming weeks. |
OLD | NEW |