Revision 2d56cd126920b614514b2c094b15cc783acc03c2 authored by Darren Shen on 19 March 2018, 05:47:13 UTC, committed by Chromium WPT Sync on 19 March 2018, 05:47:13 UTC
This patch adds support for motion path properties. We had to modify
the computed style computation for <position> values. Previously, we
parse a <position> value as a CSSValuePair, but compute them to a
CSSValueList containing two items. This is very strange, so we just
compute to a CSSValuePair. Since both serialize to the same string,
this has no behavioural changes on CSSOM.
Bug: 820299
Change-Id: I2131055dad0785eb47ea2d2d89f00229f4376bae
Reviewed-on: https://chromium-review.googlesource.com/967915
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543975}
1 parent 10c525d
exampleTarget.json
{
"$schema": "http://json-schema.org/draft-04/schema#",
"title": "Check if target feature implemented",
"description": "'There must be 1 or more target relationships associated with an Annotation.' (Section 3.1)",
"assertionType": "must",
"expectedResult": "valid",
"errorMessage": "Error: Annotation has no target relationships - at least 1 is required. (Section 3.1)",
"type": "object",
"properties": {
"target": { "type": ["string", "array", "object"] }
},
"required": ["target"]
}
Computing file changes ...
