Support the KeyframeEffectReadOnly composite property
Previously we associated the 'composite' property with the Keyframe,
including the default 'replace' value. However the spec differentiates
between the KeyframeEffectReadOnly composite property and additional
keyframe-specific composite properties. This CL updates the code to
properly track these two concepts. Keyframe now has an optional
keyframe-specific composite operation, and the final composite operation
is determined when creating the property-specific keyframes.
Unfortunately due to the way the code is structured this change was
non-trivial. Major changes:
* KeyframeEffectReadOnly and InertEffect now store a
KeyframeEffectModelBase rather than an EffectModel, due to the
need to store and retrieve the 'composite' value.
* The KeyframeEffectModelBase on KeyframeEffectReadOnly is now
non-nullable. Previously a null model indicated that a
KeyframeEffectReadOnly had no keyframes; this is now tracked
explicitly in the model.
Bug: 785526
Change-Id: I9b4967bf11c010bbd1f61f2d5ced1159fc0dd0c4
Reviewed-on: https://chromium-review.googlesource.com/786292
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by:
Jeremy Roman <jbroman@chromium.org>
Reviewed-by:
Andrey Kosyakov <caseq@chromium.org>
Reviewed-by:
Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#520224}
Showing
This diff is collapsed.
This diff is collapsed.
Please register or sign in to comment