Silently convert unsupported composite values to kCompositeReplace
This consolidates Chrome's behavior to be consistent everywhere CompositeOperations are parsed, and to match Firefox. When a CompositeOperation is found that we don't support, it is silently replaced with kCompositeReplace. When running without WebAnimationsAPI, developers should only expect to have kCompositeReplace animations. When running with WebAnimationsAPI, developers can detect which composite is in use by either querying: effect.composite; OR effect.getKeyframes(); // Check each keyframe for a keyframe-specific composite value. Intent thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/wRsafuGKr5w Bug: 806139 Change-Id: I80fefff3fc833b62787c57d22cbec656365ec374 Reviewed-on: https://chromium-review.googlesource.com/896807 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by:Robert Flack <flackr@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#537300}
Showing
Please register or sign in to comment