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
historical.html
<!doctype html>
<title>Historical Web Audio API features</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script>
[
"webkitAudioContext",
"webkitAudioPannerNode",
"webkitOfflineAudioContext",
].forEach(name => {
test(function() {
assert_false(name in window);
}, name + " interface should not exist");
});
</script>
Computing file changes ...
