Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(228)

Side by Side Diff: polymer_0.5.4/bower_components/web-animations-js/README.md

Issue 895523005: Added Polymer 0.5.4 (Closed) Base URL: https://chromium.googlesource.com/infra/third_party/npm_modules.git@master
Patch Set: Created 5 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 1
2 Quick Start 2 Quick Start
3 ----------- 3 -----------
4 4
5 To provide native Chrome Web Animation features (`Element.animate` and Playback 5 To provide native Chrome Web Animation features (`Element.animate` and Playback
6 Control) in other browsers, use `web-animations.min.js`. To explore all of the 6 Control) in other browsers, use `web-animations.min.js`. To explore all of the
7 proposed Web Animations API, use `web-animations-next.min.js`. 7 proposed Web Animations API, use `web-animations-next.min.js`.
8 8
9 What is Web Animations? 9 What is Web Animations?
10 ----------------------- 10 -----------------------
(...skipping 97 matching lines...) Expand 10 before | Expand all | Expand 10 after
108 108
109 ### Inline Style 109 ### Inline Style
110 110
111 Inline style modification is the mechanism used by the polyfill to animate 111 Inline style modification is the mechanism used by the polyfill to animate
112 properties. Both web-animations and web-animations-next incorporate a module 112 properties. Both web-animations and web-animations-next incorporate a module
113 that emulates a vanilla inline style object, so that style modification from 113 that emulates a vanilla inline style object, so that style modification from
114 JavaScript can still work in the presence of animations. However, to keep the 114 JavaScript can still work in the presence of animations. However, to keep the
115 size of web-animations-next-lite as small as possible, the style emulation 115 size of web-animations-next-lite as small as possible, the style emulation
116 module is not included. When using this version of the polyfill, JavaScript 116 module is not included. When using this version of the polyfill, JavaScript
117 inline style modification will be overwritten by animations. 117 inline style modification will be overwritten by animations.
118 Due to browser constraints inline style modification is not supported on iOS 7
119 or Safari 6 (or earlier versions).
118 120
119 ### Prefix handling 121 ### Prefix handling
120 122
121 The polyfill will automatically detect the correctly prefixed name to use when 123 The polyfill will automatically detect the correctly prefixed name to use when
122 writing animated properties back to the platform. Where possible, the polyfill 124 writing animated properties back to the platform. Where possible, the polyfill
123 will only accept unprefixed versions of experimental features. For example: 125 will only accept unprefixed versions of experimental features. For example:
124 126
125 var animation = new Animation(elem, {"transform": "translate(100px, 100px)"} , 2000); 127 var animation = new Animation(elem, {"transform": "translate(100px, 100px)"} , 2000);
126 128
127 will work in all browsers that implement a conforming version of transform, but 129 will work in all browsers that implement a conforming version of transform, but
(...skipping 12 matching lines...) Expand all
140 142
141 Polyfill Issues 143 Polyfill Issues
142 --------------- 144 ---------------
143 145
144 Report any issues with this implementation on GitHub: 146 Report any issues with this implementation on GitHub:
145 <https://github.com/web-animations/web-animations-next/issues/new>. 147 <https://github.com/web-animations/web-animations-next/issues/new>.
146 148
147 Breaking changes 149 Breaking changes
148 ---------------- 150 ----------------
149 151
150 When we make a potentially breaking change to the polyfill's API surface (like 152 When we make a potentially breaking change to the polyfill's API
151 a rename) we'll continue supporting the old version, deprecated, for three 153 surface (like a rename) where possible we will continue supporting the
152 months, and ensure that there are console warnings to indicate that a change is 154 old version, deprecated, for three months, and ensure that there are
153 pending. After three months, the old version of the API surface (e.g. the old 155 console warnings to indicate that a change is pending. After three
154 version of a function name) will be removed. If you see deprecation warnings 156 months, the old version of the API surface (e.g. the old version of a
155 you can't avoid it by not updating. 157 function name) will be removed. *If you see deprecation warnings you
158 can't avoid it by not updating*.
156 159
157 We also announce anything that isn't a bug fix on 160 We also announce anything that isn't a bug fix on
158 [web-animations-changes@googlegroups.com](https://groups.google.com/forum/#!foru m/web-animations-changes). 161 [web-animations-changes@googlegroups.com](https://groups.google.com/forum/#!foru m/web-animations-changes).
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698