[css-values] Several new units

css-animations/Overview.bs

@@ -51,6 +51,8 @@ urlPrefix: https://html.spec.whatwg.org/multipage/infrastructure.html; type: dfn
 <pre class="link-defaults">
 spec:cssom-1; type:interface; text:CSSRule
 spec:html; type:dfn; text:case-sensitive
+spec:css-backgrounds-3; type:property; text:background-image
+spec:css2; type:property; text:display
 </pre>
 
 <h2 id="intro">
@@ -787,19 +789,19 @@ The 'animation-fill-mode' property</h3>
 			is an integer greater than zero, the values applied will be those for the end of the last
 			completed iteration of the animation (rather than the values for the start of the iteration
 			that would be next). When 'animation-iteration-count' is zero, the values applied will be
-			those that would start the first iteration (just as when 'animation-fill-mode' is ''backwards'').
+			those that would start the first iteration (just as when 'animation-fill-mode' is ''animation-fill-mode/backwards'').
 
 		<dt><dfn>backwards</dfn>
 		<dd>
 			During the period defined by 'animation-delay', the animation will apply the property values
 			defined in the keyframe that will start the first iteration of the animation.
-			These are either the values of the ''from'' keyframe (when 'animation-direction' is ''normal''
-			or ''alternate'') or those of the ''to'' keyframe (when 'animation-direction' is ''reverse''
-			or ''alternate-reverse'').
+			These are either the values of the ''from'' keyframe (when 'animation-direction' is ''animation-direction/normal''
+			or ''animation-direction/alternate'') or those of the ''to'' keyframe (when 'animation-direction' is ''animation-direction/reverse''
+			or ''animation-direction/alternate-reverse'').
 
 		<dt><dfn>both</dfn>
 		<dd>
-			The effects of both ''forwards'' and ''backwards'' fill apply.
+			The effects of both ''animation-fill-mode/forwards'' and ''animation-fill-mode/backwards'' fill apply.
 	</dl>
 
 <h3 id="animation">

css-break/Overview.bs

@@ -1076,7 +1076,8 @@ Transforms, Positioning, and Pagination</h3>
     (The origin of an overflow-only fragment is determined
     as if that content were overflowing an empty box with zero margins/borders/padding
     at the start of the fragmentainer.)
-    However, the separation and transfer of page boxes <em>should</em> occur last;
+    However, in order to reduce dataloss when printing,
+    the separation and transfer of page boxes <em>should</em> occur last;
     thus a transformed fragment that spans pages <em>should</em>
     be sliced at the page breaks and print in its entirety
     rather than being clipped by its originating page.
@@ -1093,11 +1094,13 @@ Transforms, Positioning, and Pagination</h3>
   <p>
     Absolute positioning affects layout and thus interacts with fragmentation.
     Both the coordinate system and absolutely-positioned boxes belonging to a containing block
-    will fragment across pages in the same fragmentation flow as the containing block.
+    will fragment across fragmentainers in the same fragmentation flow as the containing block.
 
   <p>
     UAs are not required to correctly position boxes that span a <i>fragmentation break</i>
     and whose <i>block-start</i> edge position depends on where the box's content fragments.
+
+  <p>
     UAs with memory constraints that prevent them from manipulating an entire document in memory
     are not required to correctly position absolutely-positioned elements
     that end up on a previously-rendered page.