@@ -3311,7 +3311,8 @@ result.
3311
3311
this algorithm.
3312
3312
3313
3313
This algorithm implies that property values specified in keyframes can
3314
- establish order dependencies. When <a>computing a property value</a> , the
3314
+ establish order dependencies.
3315
+ When [=compute a property value|computing a property value=] , the
3315
3316
<a>computed values</a> of dependencies held by <var> value</var> must be
3316
3317
calculated <em> first</em> .
3317
3318
@@ -3327,8 +3328,8 @@ In this example, in order to <a>compute a property value</a> for
3327
3328
<code> 10em</code> , we must know the <a>computed value</a> of
3328
3329
'font-size' on the <a>target element</a> , which in turn is determined
3329
3330
by the <a>effect value</a> for 'font-size' , which in turn requires that we
3330
- compute property values for 'font-size' . Hence, computing property
3331
- values are subject to ordering constraints.
3331
+ compute property values for 'font-size' .
3332
+ Hence, computing property values are subject to ordering constraints.
3332
3333
</div>
3333
3334
3334
3335
</div>
@@ -3606,8 +3607,9 @@ Note: this procedure permits overlapping <a>keyframes</a>.
3606
3607
<a>keyframe</a> in <var> keyframes</var> respectively.
3607
3608
3608
3609
<div class="note">
3609
- Note that <a>computed keyframes</a> are "live": user-agents must behave
3610
- as if they are recreated every time the <a>effect value</a> is calculated.
3610
+ Note that <a>computed keyframes</a> are "live":
3611
+ user-agents must behave as if they are recreated every time the
3612
+ <a>effect value</a> is calculated.
3611
3613
3612
3614
For example, if there is an ongoing transition on the 'font-size' property
3613
3615
from <code> 10px</code> to <code> 20px</code> , a property value specified as
0 commit comments