CSS Motion Path: New names for properties

third_party/WebKit/LayoutTests/css3/motion-path/path-establishes-stacking-context.html

Index: third_party/WebKit/LayoutTests/css3/motion-path/path-establishes-stacking-context.html
diff --git a/third_party/WebKit/LayoutTests/css3/motion-path/path-establishes-stacking-context.html b/third_party/WebKit/LayoutTests/css3/motion-path/path-establishes-stacking-context.html
index e9b024eb91ac304e047851781bede687b106d34f..07dfd6099af9cceb6e6a7d1935aefdccdcde9f0e 100644
--- a/third_party/WebKit/LayoutTests/css3/motion-path/path-establishes-stacking-context.html
+++ b/third_party/WebKit/LayoutTests/css3/motion-path/path-establishes-stacking-context.html
@@ -36,11 +36,11 @@ span {
 }
 
 #div1 {
-  motion-path: path('M400,0');
+  offset-path: path('M400,0');

[suzyh_UTC10 (ex-contributor), 2016/09/19 03:32:30]

If adding offset-path to hasPropertyThatCreatesStackingContext was a bug fix
that changed behaviour, why was this test (which I expect, based on the name, is
related) unaffected? Does this test actually test what it's supposed to test?

[Eric Willigers, 2016/09/19 04:46:14]

hasPropertyThatCreatesStackingContext is about will-change.

https://dev.opera.com/articles/css-will-change-property/
https://developer.mozilla.org/en/docs/Web/CSS/will-change
https://drafts.csswg.org/css-will-change/
If any non-initial value of a property would create a stacking context on the
element, specifying that property in will-change must create a stacking context
on the element.


The idea is that 

div1 {
  will-change: offset-path;
  offset-path: none;
}

should create a stacking context.



As for this test's effectiveness, I've included the question in crbug.com/648113

In this CL, we are simply migrating the existing test to the new name.

 }
 
 #div2 {
-  motion-path: none;
+  offset-path: none;
 }
 
 </style>