Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make commitStyles use computed values instead of resolved values #22452

Merged
merged 1 commit into from May 5, 2020

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Mar 25, 2020

Add new CSSAnimationUtils class with a static method
KeyframeValueFromComputedStyle() which returns the true computed value
for all properties. This mostly calls CSSValueForComputedStyle() without
a LayoutObject, but the cases where this does not return the computed
value (line-height and transform) are handles separately, similarly
to the implementation of ComputedStyleMap.

This method does take a LayoutObject, but it is only used to resolve
matrix interpolation of box-size-dependent transform values, which
produces a deferred compilation which cannot be serialized directly in
the current spec.

Make Animation.commitStyles() use this new function instead of
committing the resolved value using CSSValueFromComputedStyle().

Add additional WPT tests for commitStyles() adding tests for
special-case properties and splitting the logical properties case.

Bug: 1056197, 1057307
Change-Id: Ic823f96f257d4c6b010dfee758d4ac0b5cd4148c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2118765
Commit-Queue: George Steel <gtsteel@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765297}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2118765 branch 3 times, most recently from de6e384 to 841b0da Compare March 30, 2020 20:06
@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2118765 branch 6 times, most recently from 3982069 to b62120e Compare April 9, 2020 00:43
@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2118765 branch 3 times, most recently from 75e6aa1 to fe518c1 Compare May 4, 2020 21:01
Add new CSSAnimationUtils class with a static method
KeyframeValueFromComputedStyle() which returns the true computed value
for all properties. This mostly calls CSSValueForComputedStyle() without
a LayoutObject, but the cases where this does not return the computed
value (line-height and transform) are handles separately, similarly
to the implementation of ComputedStyleMap.

This method does take a LayoutObject, but it is only used to resolve
matrix interpolation of box-size-dependent transform values, which
produces a deferred compilation which cannot be serialized directly in
the current spec.

Make Animation.commitStyles() use this new function instead of
committing the resolved value using CSSValueFromComputedStyle().

Add additional WPT tests for commitStyles() adding tests for
special-case properties and splitting the logical properties case.

Bug: 1056197, 1057307
Change-Id: Ic823f96f257d4c6b010dfee758d4ac0b5cd4148c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2118765
Commit-Queue: George Steel <gtsteel@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#765297}
@KyleJu KyleJu closed this May 5, 2020
@KyleJu KyleJu reopened this May 5, 2020
@chromium-wpt-export-bot chromium-wpt-export-bot merged commit c7c25c1 into master May 5, 2020
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-2118765 branch May 5, 2020 01:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants