tree 55424c40923864ccaa49a0a126c5545f369302cd
parent b6e1dafe78b2875ebe1837508e28c8dce2693b19
author Doris Liu <tianliu@google.com> 1460579318 -0700
committer Doris Liu <tianliu@google.com> 1460579865 -0700

Add api check to guard AnimatorSet behavior change

For pre-N, we have inconsistent behavior between ValueAnimator and
AnimatorSet in the case of calling end() when already ended:
ValueAnimator would start() and immediately end, whereas AnimatorSet
would be no-op. We made a decision to be consistent within Animation
Framework from N forward, which means that AnimatorSet will have the
new behavior of starting and immediately ending just like
ValueAnimator. This new behavior will be guarded by an API check.

Bug: 25601129
Change-Id: I2d952a93d8521c547ec8cde173c80d1d8ead0639