[css-tables] Fragmentation: accomodated layout tables

Author: FremyCompany

css-tables-3/Overview.bs

@@ -2376,26 +2376,38 @@ spec:css21; type:property; text:max-width
 
 		<p>
 			When fragmenting a table, user agents must attempt 
-				to preserve table cells unfragmented.
+				to preserve the table rows unfragmented
+				if their height is at least twice smaller than the table width.
+			Other rows are said <dfn id="freely-fragmentable">freely fragmentable</dfn>.
 
 		<p>
 			When a table doesn't fit entirely in a fragmentainer,
+				and the first row that does not fit in the fragmentainer is not <a>freely fragmentable</a>.
 				the user agent has to insert some vertical gap 
 				between the rows located before and at the overflow point
 				such that the two rows end up separated in sibling fragmentainers.
+			Cells spanning across those two rows are 
+				divided into two fragments (one in each fragmentainer),
+				whose height is kept equal to the rows they span in each of these fragments, and 
+				their content is fragmented among those two fragments, in parallel.
 
-		<p class="issue">
-			Add a figure clarifying this.	
+		<figure>
+			<img src="./images/CSS-Tables-Fragmentation-1.svg" style="width:100%; max-width: 500px;" />
+			<figcaption>Expected rendering of table fragmented across two pages</figcaption>
+		</figure>
 
 		<p>
-			When there is no row fitting entirely in the current fragmentainer,
-				user agents must split each cell of the row among the two fragmentainers
-				so that all fragments in the same fragmentainer preserve the same height.
+			When there is no row fitting entirely in the current fragmentainer
+			or when the first row that does not fit in the fragmentainer is <a>freely fragmentable</a>,
+				user agents must split each cell of the row in two fragments (one in each fragmentainer)
+				so that all fragments in the same fragmentainer continue to share the same height.
 			Then, the user agent must fragment the content of each cell 
-				among its two fragments in parallel. 
+				among its two fragments, in parallel. 
 
-		<p class="issue">
-			Add a figure clarifying this.
+		<figure>
+			<img src="./images/CSS-Tables-Fragmentation-2.svg" style="width:100%; max-width: 500px;" />
+			<figcaption>Expected rendering of table containing a tall row fragmented across two pages</figcaption>
+		</figure>
 
 		<p>
 			When 'break-before' or 'break-after' is applied 
@@ -2420,6 +2432,11 @@ spec:css21; type:property; text:max-width
 				leave room and if needed render the table top border.
 			The same applies for footer rows and the table bottom border.
 
+		<figure>
+			<img src="./images/CSS-Tables-Repeating-Headers.svg" style="width:100%; max-width: 500px;" />
+			<figcaption>Expected rendering of table with headers and footers fragmented across two pages</figcaption>
+		</figure>
+			
 		<p>
 			When doing so doesn't leave enough space to insert at least one content row,
 				users agents must drop the repeated footer.