File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -256,8 +256,9 @@ Hinting at Future Behavior: the 'will-change' property</h2>
256256 It is still <em> safe</em> to specify them, though;
257257 it'll simply have no effect.
258258
259- Specifying a <a>custom property</a> must have no effect,
260- including the "side-effect" management detailed below.
259+ Specifying a custom property must have no effect,
260+ which means that effects that happen through custom properties
261+ do not count for the rules below that are conditioned on any non-initial value of a property causing something.
261262
262263 <p class='example'>
263264 For example, browsers often handle elements with 'transform' set to a non-initial value very differently from normal elements,
@@ -277,7 +278,7 @@ Hinting at Future Behavior: the 'will-change' property</h2>
277278 If any non-initial value of a property would cause the element to generate a containing block for fixed positioned elements,
278279 specifying that property in 'will-change' must cause the element to generate a containing block for fixed positioned elements.
279280
280- If a non-initial value of a property would cause rendering differences on the element
281+ If any non-initial value of a property would cause rendering differences on the element
281282 (such as using a different anti-aliasing strategy for text),
282283 the user agent should use that alternate rendering when the property is specified in 'will-change' ,
283284 to avoid sudden rendering differences when the property is eventually changed.
You can’t perform that action at this time.
0 commit comments