Name: flow-into
-		Value: none | <> [element | content]?
+		Value: none | <> [element | content]?
 		Initial: none
 		Applies To: All elements, but not pseudo-elements such as ::first-line, ::first-letter, ::before or ::after.
 		Inherited: no
@@ -389,8 +389,8 @@ The 'flow-into' property
 		Animation type: not animatable
 	

-

none

+

+

none

The element is not moved @@ -398,7 +398,7 @@ The 'flow-into' property and normal CSS processing takes place.

-

<ident>

+

<> [ element | content ]?

If the keyword element is present @@ -406,7 +406,7 @@ The 'flow-into' property then the element is taken out of its parent's flow and placed into the flow - with the name '<ident>'. + with the name '<>'. If the keyword content is present, then only the element's contents are placed into the named flow. @@ -468,7 +468,7 @@ The 'flow-into' property Each CSS Region in a region chain establishes a containing block for absolutely positioned - elements in the named flow (see [[!CSS21]]). + elements in the named flow (see [[!CSS2]]). That first CSS Region in a region chain establishes the initial containing block for such absolutely positioned elements. @@ -569,7 +569,7 @@ The 'flow-from' property

 		Name: flow-from
-		Value: <> | none
+		Value: <> | none
 		Initial: none
 		Applies To: Non-replaced block containers. 
 This might be expanded in future versions of the specification to allow other types of containers to receive flow content.
 		Inherited: no
@@ -577,30 +577,29 @@ The 'flow-from' property
 		Animation type: not animatable
 	

-

-

none

+

+

none

The block container is not a CSS Region.

-

<ident>

+

<>

The block container becomes a CSS Region (except as detailed in the text below), and is ordered in a region chain according to its document order. - The content from the flow - with the <ident> + The content from the flow with the + <> name will be broken into fragments and visually formatted in the principal boxes of the regions in the region chain. -
- If there is no flow with name - <ident>, + + If there is no flow with name <>, then the block container does not format any content visually.

@@ -626,11 +625,11 @@ The 'flow-from' property Block container pseudo-elements where the value of 'flow-from' computes to an - <ident> + <> and the value of 'content' computes to ''content/none'' are generated as CSS Regions, which is an update to the behavior - described in [[!CSS21]]. + described in [[!CSS2]]. If an element has style containment (See [[!CSS-CONTAIN-1]]), then the 'flow-from' property must be scoped to that element. @@ -639,7 +638,7 @@ The 'flow-from' property A block container becomes a CSS Region when its 'flow-from' property is set - to a valid <ident> value, + to a valid <> value, even if there is no content contributing to the referenced flow. For example: @@ -739,8 +738,7 @@ The 'flow-from' property Cycle Detection named flows containing elements - where the value of 'flow-from' computes to an - <ident> + where the value of 'flow-from' computes to a <> can produce nonsensical circular relationships, such as a named flow containing CSS Regions @@ -755,25 +753,20 @@ Cycle Detection

• Every named flow depends on its elements - where the value of 'flow-from' computes to an - <ident>. + where the value of 'flow-from' computes to a <>.
• Every element in a named flow - where the value of 'flow-from' computes to an - <ident> + where the value of 'flow-from' computes to a <> depends on the named flow with the - <ident> - name. + <> name.

If the graph contains a cycle, any elements where the value of 'flow-from' - computes to an - <ident> - participating in the cycle - do not become CSS Regions. + computes to a <> participating + in the cycle do not become CSS Regions.

Note @@ -979,7 +972,7 @@ The region-fragment property on the last line, the 'overflow' property controls the visibility of the overflowing content. - See the 'overflow' property definition ([[CSS21]]). + See the 'overflow' property definition ([[CSS2]]).

@@ -1610,7 +1603,7 @@ The Region Flow Content Box (RFCB)

- + @@ -1631,7 +1624,7 @@ RFCB 'width' resolution At various points in the visual formatting of documents containing regions, the used 'width' of RFCBs and regions need to be resolved. In all cases, the resolution is done following the rules for - calculating widths and margins (see [[!CSS21]]). + calculating widths and margins (see [[!CSS2]]). Sometimes, resolving the used 'width' value requires measuring the content's min-content and max-content values @@ -1674,7 +1667,7 @@ Regions visual formatting steps

- + @@ -1904,7 +1897,7 @@ Step 1 - Phase 1: Laying out RFCBs with used height of zero Conceptually, this produces the layout illustrated below.

- + @@ -1941,7 +1934,7 @@ Step 1 - Phase 2: Layout flow to compute the RFCBs' flow fragments heights This results in a resolved flow fragment height: FH-C.

- + @@ -1973,7 +1966,7 @@ Step 2: Layout document and regions without named flows FH-C becomes rC's used 'height'.

- + @@ -2004,7 +1997,7 @@ Step 3: named flows layout computed in Step 1 Phase 2.

- +