suzyh_UTC10 (ex-contributor)
2016/09/19 03:32:30
If adding offset-path to hasPropertyThatCreatesSta
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 wil
On 2016/09/19 03:32:30, suzyh wrote:
> 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?
hasPropertyThatCreatesStackingContext is about will-change.
https://dev.opera.com/articles/css-will-change-property/https://developer.mozilla.org/en/docs/Web/CSS/will-changehttps://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.
Issue 2241993002: CSS Motion Path: New names for properties
(Closed)
Created 4 years, 4 months ago by Eric Willigers
Modified 4 years, 3 months ago
Reviewers: jochen (gone - plz use gerrit), alancutter (OOO until 2018), dstockwell, Mark P, sashab, sof, suzyh_UTC10 (ex-contributor), Timothy Loh
Base URL: https://chromium.googlesource.com/chromium/src.git@master
Comments: 20