Mercurial > drafts / changeset

     1.1 --- a/css-2015/Overview.bs	Fri May 29 16:46:00 2015 -0700
     1.2 +++ b/css-2015/Overview.bs	Fri May 29 16:46:19 2015 -0700
     1.3 @@ -4,6 +4,7 @@
     1.4  Level: 1
     1.5  Status: NOTE
     1.6  Group: CSSWG
     1.7 +Work Status: Exploring
     1.8  URL: https://dev.w3.org/csswg/css-2015/
     1.9  Editor: Tab Atkins Jr., Google, http://xanthir.com/
    1.10  Abstract: This snapshot summarizes the specs that are "stable" and broadly usable in CSS, as of 2015.

     2.1 --- a/css-align/Overview.bs	Fri May 29 16:46:00 2015 -0700
     2.2 +++ b/css-align/Overview.bs	Fri May 29 16:46:19 2015 -0700
     2.3 @@ -5,6 +5,7 @@
     2.4  Level: 3
     2.5  Group: csswg
     2.6  Status: WD
     2.7 +Work Status: Revising
     2.8  Date: 2014-12-18
     2.9  ED: http://dev.w3.org/csswg/css-align/
    2.10  TR: http://www.w3.org/TR/css-align-3/

     3.1 --- a/css-animations-2/Overview.bs	Fri May 29 16:46:00 2015 -0700
     3.2 +++ b/css-animations-2/Overview.bs	Fri May 29 16:46:19 2015 -0700
     3.3 @@ -2,6 +2,7 @@
     3.4  
     3.5  <pre class='metadata'>
     3.6  Status: ED
     3.7 +Work Status: Exploring
     3.8  Shortname: css-animations-2
     3.9  Level: 2
    3.10  Group: csswg

     4.1 --- a/css-animations/Overview.bs	Fri May 29 16:46:00 2015 -0700
     4.2 +++ b/css-animations/Overview.bs	Fri May 29 16:46:19 2015 -0700
     4.3 @@ -2,6 +2,7 @@
     4.4  
     4.5  <pre class='metadata'>
     4.6  Status: ED
     4.7 +Work Status: Refining
     4.8  Shortname: css-animations
     4.9  Level: 1
    4.10  Group: csswg
    4.11 @@ -90,29 +91,29 @@
    4.12  
    4.13  	While running, the animation computes the value of those properties
    4.14  	it animates. Other values may take precedence over the animated value
    4.15 -	according to the CSS cascade ([[!CSS3CASCADE]]). 
    4.16 +	according to the CSS cascade ([[!CSS3CASCADE]]).
    4.17  
    4.18  	The start time of an animation is the time at which the style applying
    4.19  	the animation and the corresponding @keyframes rule are both resolved.
    4.20  	If an animation is specified for an element but the corresponding
    4.21 -	@keyframes rule does not yet exist, the animation cannot start; the 
    4.22 -	animation will start from the beginning as soon as a matching @keyframes 
    4.23 -	rule can be resolved. An animation specified by dynamically modifying the 
    4.24 -	element's style will start when this style is resolved; that may be 
    4.25 -	immediately in the case of a pseudo style rule such as hover, or may be 
    4.26 -	when the scripting engine returns control to the browser (in the case of 
    4.27 -	style applied by script). Note that dynamically updating keyframe style 
    4.28 +	@keyframes rule does not yet exist, the animation cannot start; the
    4.29 +	animation will start from the beginning as soon as a matching @keyframes
    4.30 +	rule can be resolved. An animation specified by dynamically modifying the
    4.31 +	element's style will start when this style is resolved; that may be
    4.32 +	immediately in the case of a pseudo style rule such as hover, or may be
    4.33 +	when the scripting engine returns control to the browser (in the case of
    4.34 +	style applied by script). Note that dynamically updating keyframe style
    4.35  	rules does not start or restart an animation.
    4.36 -	 
    4.37 +
    4.38  
    4.39  	An animation applies to an element if its name appears as one of the
    4.40  	identifiers in the computed value of the 'animation-name' property and the
    4.41  	animation uses a valid @keyframes rule. Once an
    4.42  	animation has started it continues until it ends or the 'animation-name' is
    4.43  	removed. Changing the values of animation properties while the animation
    4.44 -	is running has no effect on the amount of time that has elapsed since the 
    4.45 -	animation started running i.e. once the animation is running, updates to 
    4.46 -	'animation-delay' have no effect. The remainder of the animation runs 
    4.47 +	is running has no effect on the amount of time that has elapsed since the
    4.48 +	animation started running i.e. once the animation is running, updates to
    4.49 +	'animation-delay' have no effect. The remainder of the animation runs
    4.50  	according to the new animation property values.
    4.51  
    4.52  	Note also that changing the value
    4.53 @@ -200,7 +201,7 @@
    4.54  	declarations qualified with !important are ignored.
    4.55  
    4.56  	The @keyframes rule that is used by an animation will be the last one encountered in sorted rules
    4.57 -	order that matches the name of the animation specified by the 'animation-name' property. 
    4.58 +	order that matches the name of the animation specified by the 'animation-name' property.
    4.59  
    4.60  	<div class='example'>
    4.61  		<pre>
    4.62 @@ -253,7 +254,7 @@
    4.63  
    4.64  	To determine the set of keyframes, all of the values in the selectors are sorted in increasing order
    4.65  	by time. The rules within the @keyframes rule then cascade; the properties of a keyframe may thus derive
    4.66 -	from more than one @keyframes rule with the same selector value. 
    4.67 +	from more than one @keyframes rule with the same selector value.
    4.68  
    4.69  	If a property is not specified for a keyframe, or is specified but invalid, the animation of that
    4.70  	property proceeds as if that keyframe did not exist. Conceptually, it is as if a set of keyframes is
    4.71 @@ -414,7 +415,7 @@
    4.72  			The animation will use the keyframes with the name specified by the <<custom-ident>>,
    4.73  			if they exist.If no such keyframes exist, there is no animation.
    4.74  
    4.75 -			The <a href="http://www.w3.org/TR/css3-values/#common-keywords">CSS-wide keywords</a> 
    4.76 +			The <a href="http://www.w3.org/TR/css3-values/#common-keywords">CSS-wide keywords</a>
    4.77  			and keywords defined by this property are not valid animation names.
    4.78  	</dl>
    4.79  
    4.80 @@ -445,15 +446,15 @@
    4.81  			If the <<time>> is ''0s'', like the initial value,
    4.82  			the keyframes of the animation have no effect,
    4.83  			but the animation itself still occurs instantaneously.
    4.84 -			Specifically, start and end events are fired; if 
    4.85 -			'animation-fill-mode' is set to ''backwards'' or 
    4.86 -			''both'', the first frame of the animation, as defined by 
    4.87 -			'animation-direction', will be displayed during the 
    4.88 -			'animation-delay'. Then the last frame of the animation, 
    4.89 -			as defined by 'animation-direction', will be displayed if 
    4.90 -			'animation-fill-mode' is set to ''forwards'' or ''both''. 
    4.91 -			If 'animation-fill-mode' is set to ''animation-fill-mode/none'' 
    4.92 -			then the animation has no visible effect. 
    4.93 +			Specifically, start and end events are fired; if
    4.94 +			'animation-fill-mode' is set to ''backwards'' or
    4.95 +			''both'', the first frame of the animation, as defined by
    4.96 +			'animation-direction', will be displayed during the
    4.97 +			'animation-delay'. Then the last frame of the animation,
    4.98 +			as defined by 'animation-direction', will be displayed if
    4.99 +			'animation-fill-mode' is set to ''forwards'' or ''both''.
   4.100 +			If 'animation-fill-mode' is set to ''animation-fill-mode/none''
   4.101 +			then the animation has no visible effect.
   4.102  	</dl>
   4.103  
   4.104  <h3 id="animation-timing-function">
   4.105 @@ -487,10 +488,10 @@
   4.106  	ease in at the start of its second iteration,
   4.107  	and ease out again as it approaches the end of the animation.
   4.108  
   4.109 -	When specified in a keyframe, 'animation-timing-function' defines the progression of the 
   4.110 +	When specified in a keyframe, 'animation-timing-function' defines the progression of the
   4.111  	animation between the current keyframe and the next keyframe that defines 'animation-timing-function'
   4.112 -	in sorted keyframe selector order (or the end of the animation if no other keyframe specifies 
   4.113 -	'animation-timing function'). The specified timing function will apply over this interval independently 
   4.114 +	in sorted keyframe selector order (or the end of the animation if no other keyframe specifies
   4.115 +	'animation-timing function'). The specified timing function will apply over this interval independently
   4.116  	of the animation's current direction.
   4.117  
   4.118  <h3 id="animation-iteration-count">
   4.119 @@ -502,9 +503,9 @@
   4.120  	'animation-direction' value of ''alternate'', which will cause the animation to play in
   4.121  	reverse on alternate cycles.
   4.122  
   4.123 -	The time window during which the animation is active 
   4.124 +	The time window during which the animation is active
   4.125  	(<code>duration</code> x <code>iteration-count</code>)
   4.126 -	is known as the <dfn>active duration</dfn>. 
   4.127 +	is known as the <dfn>active duration</dfn>.
   4.128  
   4.129  	<pre class='propdef'>
   4.130  	Name: animation-iteration-count
   4.131 @@ -524,17 +525,17 @@
   4.132  	<dl dfn-type=value dfn-for=animation-iteration-count>
   4.133  		<dt><dfn>infinite</dfn>
   4.134  		<dd>
   4.135 -			The animation will repeat forever. 
   4.136 +			The animation will repeat forever.
   4.137  
   4.138  		<dt><dfn><<number>></dfn>
   4.139  		<dd>
   4.140  			<p>The animation will repeat the specified number of times.
   4.141  			If the number is not an integer,
   4.142  			the animation will end partway through its last cycle.
   4.143 -			Negative numbers are invalid. 
   4.144 +			Negative numbers are invalid.
   4.145  
   4.146 -			<p>A value of ''0'' is valid and, similar to an 'animation-duration' 
   4.147 -			of ''0s'', causes the animation to occur instantaneously. 
   4.148 +			<p>A value of ''0'' is valid and, similar to an 'animation-duration'
   4.149 +			of ''0s'', causes the animation to occur instantaneously.
   4.150  	</dl>
   4.151  
   4.152  	If the animation has a duration of ''0s'', it will occur instantaneously for any
   4.153 @@ -661,7 +662,7 @@
   4.154  			Similar to a delay of ''0s'', it means that the animation executes immediately,
   4.155  			but is automatically progressed by the absolute value of the delay,
   4.156  			as if the animation had started the specified time in the past,
   4.157 -			and so it appears to start partway through its 
   4.158 +			and so it appears to start partway through its
   4.159  			<a href="#animation-iteration-count">active duration</a>.
   4.160  			If an animation's keyframes have an implied starting value,
   4.161  			the values are taken from the time the animation starts,
   4.162 @@ -677,7 +678,7 @@
   4.163  	element) and the time it begins execution (which is determined by the 'animation-delay'
   4.164  	property). Also, by default an animation does not affect property values after the
   4.165  	animation ends (determined by the 'animation-duration' and 'animation-iteration-count' properties).
   4.166 -	The 'animation-fill-mode' property can override this behavior. Dynamic updates to the property will 
   4.167 +	The 'animation-fill-mode' property can override this behavior. Dynamic updates to the property will
   4.168  	be reflected by property values as needed, whether during the animation delay or after the animation ends.
   4.169  
   4.170  	<pre class='propdef'>
   4.171 @@ -702,19 +703,19 @@
   4.172  
   4.173  		<dt><dfn>forwards</dfn>
   4.174  		<dd>
   4.175 -			After the animation ends (as determined by its 'animation-iteration-count'), the animation 
   4.176 -			will apply the property values for the time the animation ended. When 'animation-iteration-count' 
   4.177 -			is an integer greater than zero, the values applied will be those for the end of the last 
   4.178 -			completed iteration of the animation (rather than the values for the start of the iteration 
   4.179 -			that would be next). When 'animation-iteration-count' is zero, the values applied will be 
   4.180 +			After the animation ends (as determined by its 'animation-iteration-count'), the animation
   4.181 +			will apply the property values for the time the animation ended. When 'animation-iteration-count'
   4.182 +			is an integer greater than zero, the values applied will be those for the end of the last
   4.183 +			completed iteration of the animation (rather than the values for the start of the iteration
   4.184 +			that would be next). When 'animation-iteration-count' is zero, the values applied will be
   4.185  			those that would start the first iteration (just as when 'animation-fill-mode' is ''backwards'').
   4.186  
   4.187  		<dt><dfn>backwards</dfn>
   4.188  		<dd>
   4.189 -			During the period defined by 'animation-delay', the animation will apply the property values 
   4.190 +			During the period defined by 'animation-delay', the animation will apply the property values
   4.191  			defined in the keyframe that will start the first iteration of the animation.
   4.192 -			These are either the values of the ''from'' keyframe (when 'animation-direction' is ''normal'' 
   4.193 -			or ''alternate'') or those of the ''to'' keyframe (when 'animation-direction' is ''reverse'' 
   4.194 +			These are either the values of the ''from'' keyframe (when 'animation-direction' is ''normal''
   4.195 +			or ''alternate'') or those of the ''to'' keyframe (when 'animation-direction' is ''reverse''
   4.196  			or ''alternate-reverse'').
   4.197  
   4.198  		<dt><dfn>both</dfn>
   4.199 @@ -842,9 +843,9 @@
   4.200  	<dl dfn-type=event dfn-for=animationevent>
   4.201  		<dt><dfn>animationstart</dfn>
   4.202  		<dd>
   4.203 -			The <a idl>animationstart</a> event occurs at the start of the animation. 
   4.204 -			If there is an 'animation-delay' then this event will fire once the delay 
   4.205 -			period has expired. A negative delay will cause the event to fire with 
   4.206 +			The <a idl>animationstart</a> event occurs at the start of the animation.
   4.207 +			If there is an 'animation-delay' then this event will fire once the delay
   4.208 +			period has expired. A negative delay will cause the event to fire with
   4.209  			an elapsedTime equal to the absolute value of the delay; in this case the
   4.210  			event will fire whether 'animation-play-state' is set to ''running'' or ''paused''.
   4.211  			<ul>
   4.212 @@ -923,10 +924,10 @@
   4.213  			This attribute represents the keyframe selector as a comma-separated list of
   4.214  			percentage values. The ''from'' and ''to'' keywords map to 0% and 100%,
   4.215  			respectively.
   4.216 -            
   4.217 -            If <a attribute for="CSSKeyframeRule">keyText</a> is updated with an invalid keyframe selector, 
   4.218 +
   4.219 +            If <a attribute for="CSSKeyframeRule">keyText</a> is updated with an invalid keyframe selector,
   4.220              a <a spec="webidl">SyntaxError</a> exception must be thrown.
   4.221 - 
   4.222 +
   4.223  		<dt><dfn>style</dfn>
   4.224  		<dd>
   4.225  			This attribute represents the style associated with this keyframe.
   4.226 @@ -960,8 +961,8 @@
   4.227  		<dt><dfn>name</dfn>
   4.228  		<dd>
   4.229  			This attribute is the name of the keyframes, used by the 'animation-name' property.
   4.230 -			
   4.231 -			Setting this property to a value matching a 
   4.232 +
   4.233 +			Setting this property to a value matching a
   4.234  			<a href="http://www.w3.org/TR/css3-values/#common-keywords">CSS-wide keyword</a>
   4.235  			or any keyword defined for the 'animation-name' property will throw a <a spec="webidl">SyntaxError</a>
   4.236  			exception.
   4.237 @@ -995,8 +996,8 @@
   4.238  <h4 id="interface-csskeyframesrule-deleterule">
   4.239  The <code>deleteRule</code> method</h4>
   4.240  
   4.241 -	The <dfn method for="CSSKeyframesRule">deleteRule()</dfn> method deletes the 
   4.242 -    last declared <a idl>CSSKeyframeRule</a> matching the specified keyframe selector. 
   4.243 +	The <dfn method for="CSSKeyframesRule">deleteRule()</dfn> method deletes the
   4.244 +    last declared <a idl>CSSKeyframeRule</a> matching the specified keyframe selector.
   4.245      If no matching rule exists, the method does nothing.
   4.246  
   4.247  	Parameters:
   4.248 @@ -1018,7 +1019,7 @@
   4.249  <h4 id="interface-csskeyframesrule-findrule">
   4.250  The <code>findRule</code> method</h4>
   4.251  
   4.252 -	The <dfn method for="CSSKeyframesRule">findRule()</dfn> returns the 
   4.253 +	The <dfn method for="CSSKeyframesRule">findRule()</dfn> returns the
   4.254      last declared <a idl>CSSKeyframeRule</a> matching the specified keyframe selector.
   4.255      If no matching rule exists, the method does nothing.
   4.256  
   4.257 @@ -1045,7 +1046,7 @@
   4.258      <div class='example'>
   4.259          For example, given the following animation:
   4.260          <pre>
   4.261 -        
   4.262 +
   4.263          @keyframes colorful-diagonal-slide {
   4.264  
   4.265            from {
   4.266 @@ -1054,7 +1055,7 @@
   4.267            }
   4.268  
   4.269            10% {
   4.270 -            background-color: blue; 
   4.271 +            background-color: blue;
   4.272            }
   4.273  
   4.274            10% {

     5.1 --- a/css-backgrounds-4/Overview.bs	Fri May 29 16:46:00 2015 -0700
     5.2 +++ b/css-backgrounds-4/Overview.bs	Fri May 29 16:46:19 2015 -0700
     5.3 @@ -4,6 +4,7 @@
     5.4  Shortname: css-backgrounds
     5.5  Level: 4
     5.6  Status: ED
     5.7 +Work Status: Exploring
     5.8  Group: csswg
     5.9  TR: http://www.w3.org/TR/css-backgrounds-4/
    5.10  ED: http://dev.w3.org/csswg/css-backgrounds-4/
    5.11 @@ -11,7 +12,7 @@
    5.12  Editor: Elika J. Etemad, Invited Expert, http://fantasai.inkedblade.net/contact
    5.13  Editor: Lea Verou, Invited Expert, http://lea.verou.me/about/
    5.14  Abstract: This module contains the features of CSS relating to the borders and backgrounds of boxes on the page. It includes and extends the functionality of <a href="http://www.w3.org/TR/css3-background/">CSS Backgrounds and Borders Level&nbsp;3</a>. [[CSS3BG]] The main extensions compared to level&nbsp;3 are shaping ('corner-shape') and clipping borders ('border-clip'), logical background positions ('background-position'), and the ''extend'' ability of 'background-repeat'.
    5.15 -Ignored Terms: 
    5.16 +Ignored Terms:
    5.17  </pre>
    5.18  
    5.19  <h2 id="intro">

     6.1 --- a/css-break/Overview.bs	Fri May 29 16:46:00 2015 -0700
     6.2 +++ b/css-break/Overview.bs	Fri May 29 16:46:19 2015 -0700
     6.3 @@ -3,6 +3,7 @@
     6.4  
     6.5  <pre class='metadata'>
     6.6  Status: ED
     6.7 +Work Status: Refining
     6.8  ED: http://dev.w3.org/csswg/css-break/
     6.9  Shortname: css-break
    6.10  Group: csswg

     7.1 --- a/css-cascade-3/Overview.bs	Fri May 29 16:46:00 2015 -0700
     7.2 +++ b/css-cascade-3/Overview.bs	Fri May 29 16:46:19 2015 -0700
     7.3 @@ -4,6 +4,7 @@
     7.4  Shortname: css-cascade
     7.5  Level: 3
     7.6  Status: ED
     7.7 +Work Status: Testing
     7.8  Group: csswg
     7.9  ED: http://dev.w3.org/csswg/css-cascade-3/
    7.10  TR: http://www.w3.org/TR/css-cascade-3/

     8.1 --- a/css-cascade/Overview.bs	Fri May 29 16:46:00 2015 -0700
     8.2 +++ b/css-cascade/Overview.bs	Fri May 29 16:46:19 2015 -0700
     8.3 @@ -4,6 +4,7 @@
     8.4  Shortname: css-cascade
     8.5  Level: 4
     8.6  Status: ED
     8.7 +Work Status: Exploring
     8.8  Group: csswg
     8.9  ED: http://dev.w3.org/csswg/css-cascade/
    8.10  TR: http://www.w3.org/TR/css-cascade-4/

     9.1 --- a/css-color/Overview.bs	Fri May 29 16:46:00 2015 -0700
     9.2 +++ b/css-color/Overview.bs	Fri May 29 16:46:19 2015 -0700
     9.3 @@ -2,6 +2,7 @@
     9.4  
     9.5  <pre class=metadata>
     9.6  Status: ED
     9.7 +Work Status: Exploring
     9.8  ED: http://dev.w3.org/csswg/css-color/
     9.9  Shortname: css-color
    9.10  Group: csswg

    10.1 --- a/css-conditional/Overview.bs	Fri May 29 16:46:00 2015 -0700
    10.2 +++ b/css-conditional/Overview.bs	Fri May 29 16:46:19 2015 -0700
    10.3 @@ -4,6 +4,7 @@
    10.4  Shortname: css3-conditional
    10.5  Level: 3
    10.6  Status: ED
    10.7 +Work Status: Testing
    10.8  ED: http://dev.w3.org/csswg/css3-conditional/
    10.9  TR: http://www.w3.org/TR/css3-conditional/
   10.10  Previous Version: http://www.w3.org/TR/2013/CR-css3-conditional-20130404/

    11.1 --- a/css-containment/Overview.bs	Fri May 29 16:46:00 2015 -0700
    11.2 +++ b/css-containment/Overview.bs	Fri May 29 16:46:19 2015 -0700
    11.3 @@ -4,6 +4,7 @@
    11.4  Level: 3
    11.5  Shortname: css-containment
    11.6  Status: ED
    11.7 +Work Status: Exploring
    11.8  Group: csswg
    11.9  ED: http://dev.w3.org/csswg/css-containment/
   11.10  Editor: Tab Atkins, Google, http://xanthir.com/contact/

    12.1 --- a/css-content/Overview.bs	Fri May 29 16:46:00 2015 -0700
    12.2 +++ b/css-content/Overview.bs	Fri May 29 16:46:19 2015 -0700
    12.3 @@ -1,6 +1,7 @@
    12.4  <h1>CSS Generated Content Module Level 3</h1>
    12.5  <pre class='metadata'>
    12.6  Status: ED
    12.7 +Work Status: Exploring
    12.8  Shortname: css-content
    12.9  Level: 3
   12.10  Group: csswg

    13.1 --- a/css-counter-styles/Overview.bs	Fri May 29 16:46:00 2015 -0700
    13.2 +++ b/css-counter-styles/Overview.bs	Fri May 29 16:46:19 2015 -0700
    13.3 @@ -4,6 +4,7 @@
    13.4  Shortname: css-counter-styles
    13.5  Level: 3
    13.6  Status: CR
    13.7 +Work Status: Refining
    13.8  Group: csswg
    13.9  ED: http://dev.w3.org/csswg/css-counter-styles/
   13.10  TR: http://www.w3.org/TR/css-counter-styles-3/

    14.1 --- a/css-device-adapt/Overview.bs	Fri May 29 16:46:00 2015 -0700
    14.2 +++ b/css-device-adapt/Overview.bs	Fri May 29 16:46:19 2015 -0700
    14.3 @@ -4,6 +4,7 @@
    14.4  Shortname: css-device-adapt
    14.5  Group: CSSWG
    14.6  Status: ED
    14.7 +Work Status: Exploring
    14.8  TR: http://www.w3.org/TR/css-device-adapt/
    14.9  ED: http://dev.w3.org/csswg/css-device-adapt/
   14.10  Editor: Rune Lillesveen, Opera Software, [email protected]

    15.1 --- a/css-display/Overview.bs	Fri May 29 16:46:00 2015 -0700
    15.2 +++ b/css-display/Overview.bs	Fri May 29 16:46:19 2015 -0700
    15.3 @@ -2,6 +2,7 @@
    15.4  
    15.5  <pre class='metadata'>
    15.6  Status: WD
    15.7 +Work Status: Exploring
    15.8  Date: 2014-09-11
    15.9  ED: http://dev.w3.org/csswg/css-display/
   15.10  Shortname: css-display

    16.1 --- a/css-egg/Overview.bs	Fri May 29 16:46:00 2015 -0700
    16.2 +++ b/css-egg/Overview.bs	Fri May 29 16:46:19 2015 -0700
    16.3 @@ -4,6 +4,7 @@
    16.4  Shortname: css-egg
    16.5  Level: 1
    16.6  Status: ED
    16.7 +Work Status: Exploring
    16.8  Group: csswg
    16.9  Date: 2015-04-01
   16.10  TR: http://www.w3.org/TR/css-egg/
   16.11 @@ -93,7 +94,7 @@
   16.12  		    <td>parsec
   16.13  		    <td>1 ''pc'' = 10<sup>18</sup> ''apc''
   16.14  </table>
   16.15 -	
   16.16 +
   16.17  Note: Lightsecond was chosen instead of the more familiar lightyear
   16.18  to make sure that layouts computed during leap years
   16.19  would be unambiguously identical
   16.20 @@ -208,8 +209,8 @@
   16.21  	top: -6px;
   16.22  	transform-origin: 1px 7px;
   16.23  	-webkit-transform-origin: 1px 7px;
   16.24 -	animation-duration: 2.953s;	
   16.25 -	-webkit-animation-duration: 2.953s;	
   16.26 +	animation-duration: 2.953s;
   16.27 +	-webkit-animation-duration: 2.953s;
   16.28  	border-color: #E0E0E0;
   16.29  }
   16.30  #mars {
   16.31 @@ -235,7 +236,7 @@
   16.32  	border-radius: 50%;
   16.33  	animation: orbit linear infinite;
   16.34  	-webkit-animation: orbit linear infinite;
   16.35 -}	
   16.36 +}
   16.37  @keyframes orbit {
   16.38  	from { transform: rotate(0); }
   16.39  	to { transform: rotate(-360deg); }
   16.40 @@ -340,7 +341,7 @@
   16.41  
   16.42  <pre class="propdef partial" noexport>
   16.43      Name: voice-rate
   16.44 -    New Values: [normal | x-slow | slow | medium | fast | x-fast | <<speech-rate>>] || &lt;percentage&gt; 
   16.45 +    New Values: [normal | x-slow | slow | medium | fast | x-fast | <<speech-rate>>] || &lt;percentage&gt;
   16.46  </pre>
   16.47  
   16.48  Issue: Should negative values be allowed for <<speech-rate>> for reversed speech?
   16.49 @@ -359,14 +360,14 @@
   16.50  
   16.51  <pre>
   16.52  	<dfn>double-rainbow()</dfn> = double-rainbow(
   16.53 -		 <<position>> [, [ <<extent>> | <<length>> | <<percentage>>]]? 
   16.54 +		 <<position>> [, [ <<extent>> | <<length>> | <<percentage>>]]?
   16.55  	)
   16.56  	<dfn noexport><<extent>></dfn> = ''closest-corner'' | ''closest-side'' | ''farthest-corner'' | ''farthest-side''
   16.57  </pre>
   16.58  
   16.59  <<length>> or <<percentage>> gives the radius of the outermost circle of the double rainbow explicitly.
   16.60  Percentages values are relative to the corresponding dimension of the gradient box.
   16.61 -Negative values are invalid. 
   16.62 +Negative values are invalid.
   16.63  
   16.64  If the second argument is omitted, the default value is ''farthest-side''.
   16.65  

    17.1 --- a/css-exclusions/Overview.bs	Fri May 29 16:46:00 2015 -0700
    17.2 +++ b/css-exclusions/Overview.bs	Fri May 29 16:46:19 2015 -0700
    17.3 @@ -2,6 +2,7 @@
    17.4  
    17.5  <pre class='metadata'>
    17.6  Status: ED
    17.7 +Work Status: Exploring
    17.8  Shortname: css-exclusions
    17.9  Level: 1
   17.10  Group: csswg

    18.1 --- a/css-extensions/Overview.bs	Fri May 29 16:46:00 2015 -0700
    18.2 +++ b/css-extensions/Overview.bs	Fri May 29 16:46:19 2015 -0700
    18.3 @@ -4,6 +4,7 @@
    18.4  Shortname: css-extensions
    18.5  Level: 1
    18.6  Status: ED
    18.7 +Work Status: Exploring
    18.8  ED: http://dev.w3.org/csswg/css-extensions
    18.9  Editor: Tab Atkins, Google, http://xanthir.com/contact/
   18.10  Abstract: This specification defines methods for authors to extend and enhance various CSS features.

    19.1 --- a/css-flexbox/Overview.bs	Fri May 29 16:46:00 2015 -0700
    19.2 +++ b/css-flexbox/Overview.bs	Fri May 29 16:46:19 2015 -0700
    19.3 @@ -4,6 +4,7 @@
    19.4  Shortname: css-flexbox
    19.5  Level: 1
    19.6  Status: ED
    19.7 +Work Status: Testing
    19.8  Group: csswg
    19.9  ED: http://dev.w3.org/csswg/css-flexbox/
   19.10  TR: http://www.w3.org/TR/css-flexbox-1/

    20.1 --- a/css-font-loading/Overview.bs	Fri May 29 16:46:00 2015 -0700
    20.2 +++ b/css-font-loading/Overview.bs	Fri May 29 16:46:19 2015 -0700
    20.3 @@ -5,6 +5,7 @@
    20.4  Level: 3
    20.5  Group: csswg
    20.6  Status: ED
    20.7 +Work Status: Exploring
    20.8  ED: http://dev.w3.org/csswg/css-font-loading/
    20.9  TR: http://w3.org/TR/css-font-loading/
   20.10  Previous Version: http://www.w3.org/TR/2014/WD-css-font-loading-3-20140522/

    21.1 --- a/css-fonts-4/Overview.bs	Fri May 29 16:46:00 2015 -0700
    21.2 +++ b/css-fonts-4/Overview.bs	Fri May 29 16:46:19 2015 -0700
    21.3 @@ -3,6 +3,7 @@
    21.4  Shortname: css-fonts
    21.5  Level: 1
    21.6  Status: ED
    21.7 +Work Status: Exploring
    21.8  Group: CSSWG
    21.9  ED: https://dev.w3.org/csswg/css-fonts-4/
   21.10  No Editor: true

    22.1 --- a/css-fonts/Overview.bs	Fri May 29 16:46:00 2015 -0700
    22.2 +++ b/css-fonts/Overview.bs	Fri May 29 16:46:19 2015 -0700
    22.3 @@ -4,6 +4,7 @@
    22.4  Title: CSS Fonts Module
    22.5  Level: 3
    22.6  Status: ED
    22.7 +Work Status: Testing
    22.8  TR: http://www.w3.org/TR/css-fonts-3/
    22.9  ED: http://dev.w3.org/csswg/css-fonts/
   22.10  Editor: John Daggett, Mozilla Japan, [email protected]

    23.1 --- a/css-forms/Overview.bs	Fri May 29 16:46:00 2015 -0700
    23.2 +++ b/css-forms/Overview.bs	Fri May 29 16:46:19 2015 -0700
    23.3 @@ -3,6 +3,7 @@
    23.4  Shortname: css-forms
    23.5  Level: 1
    23.6  Status: DREAM
    23.7 +Work Status: Exploring
    23.8  ED: http://dev.w3.org/csswg/css-forms/
    23.9  No Editor: true
   23.10  Abstract: This document is currently a loosely-structured set of ideas and inspiration for CSS form styling.

    24.1 --- a/css-gcpm-4/Overview.bs	Fri May 29 16:46:00 2015 -0700
    24.2 +++ b/css-gcpm-4/Overview.bs	Fri May 29 16:46:19 2015 -0700
    24.3 @@ -1,6 +1,7 @@
    24.4  <h1>CSS Generated Content for Paged Media Module Level 4</h1>
    24.5  <pre class='metadata'>
    24.6  Status: ED
    24.7 +Work Status: Exploring
    24.8  Shortname: css-gcpm-4
    24.9  Level: 4
   24.10  Group: csswg
   24.11 @@ -9,7 +10,7 @@
   24.12  Editor: Daniel Glazman, Disruptive Innovations, [email protected]
   24.13  Abstract: Level 4 of GCPM proposes a region-based approach to footnotes and running heads.
   24.14  !Issue Tracking: <a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=CSS&component=Generated%20Content%20for%20Paged%20Media">W3C Bugzilla</a>
   24.15 -Ignored Terms: 
   24.16 +Ignored Terms:
   24.17  Warning: Not Ready
   24.18  </pre>
   24.19  
   24.20 @@ -19,22 +20,22 @@
   24.21  
   24.22  There have been many proposals for using CSS to move document content, often motivated by the desire for magazine- or book-style layout of footnotes, running heads, pull quotes, sidebars, and so on. [[CSS3GCPM]] used float: footnote and position: running(). The now-abandoned [[CSS3GENCON]] Working Draft used content: footnote. PrinceXML (and older GCPM drafts) has content: flow() and flow: static(). WHATWG CSS Books has flow: area().
   24.23  
   24.24 -This module proposes a unified approach to paginated layout based on [[CSS3-REGIONS]] and [[CSS3-PAGE-TEMPLATE]]. Additional properties will be introduced as necessary. 
   24.25 +This module proposes a unified approach to paginated layout based on [[CSS3-REGIONS]] and [[CSS3-PAGE-TEMPLATE]]. Additional properties will be introduced as necessary.
   24.26  
   24.27  
   24.28  <h2 id="running-headers-and-footers">
   24.29  	Running headers and footers
   24.30  </h2>
   24.31 -[[CSS3PAGE]] describes the sixteen page margin boxes which can be used for running headers and footers, but does not describe a mechanism for inserting content in those boxes. 
   24.32 +[[CSS3PAGE]] describes the sixteen page margin boxes which can be used for running headers and footers, but does not describe a mechanism for inserting content in those boxes.
   24.33  
   24.34 -[[CSS3GCPM]] provides for copying the string values of elements into the existing page margin boxes. 
   24.35 +[[CSS3GCPM]] provides for copying the string values of elements into the existing page margin boxes.
   24.36  
   24.37 -The existing mechanisms do not cover many use cases. 
   24.38 +The existing mechanisms do not cover many use cases.
   24.39  
   24.40  
   24.41  <h3 id="copy-into-heading">Copying a flow: the 'copy-into' property</h3>
   24.42  
   24.43 -Headers often contain document content, and it is desirable to both display that content normally (for example, as an <code>h1</code>) and to use the content in a running head. [[CSS3-REGIONS]] allows for an element to be moved to a ''named flow'', but doesn't allow for using the same content in two ways. The 'copy-into' property allows an element to be copied into a content fragment which can then be placed with the 'content' property. 
   24.44 +Headers often contain document content, and it is desirable to both display that content normally (for example, as an <code>h1</code>) and to use the content in a running head. [[CSS3-REGIONS]] allows for an element to be moved to a ''named flow'', but doesn't allow for using the same content in two ways. The 'copy-into' property allows an element to be copied into a content fragment which can then be placed with the 'content' property.
   24.45  
   24.46  <p class="note">Use cases for running heads can be found in [[LATINREQ]] http://w3c.github.io/dpub-pagination/#content</p>
   24.47  
   24.48 @@ -48,15 +49,15 @@
   24.49  Inherited: no
   24.50  Media: visual
   24.51  Computed value: as specified
   24.52 -</pre> 
   24.53 +</pre>
   24.54  
   24.55  The 'copy-into' property contains one or more pairs, each consisting of a custom identifier followed by a content-level keyword describing how to construct the value of the named content fragment.
   24.56  
   24.57 -''content-level'' expands to the following values: 
   24.58 +''content-level'' expands to the following values:
   24.59  
   24.60  <pre class="prod">
   24.61  	<dfn id="content-list">content-list</dfn> = element | content | text | attr(&lt;identifier>) | counter() | counters()
   24.62 -</pre> 
   24.63 +</pre>
   24.64  
   24.65  
   24.66  <dl>
   24.67 @@ -72,8 +73,8 @@
   24.68  
   24.69  <div class="example">
   24.70  <pre>
   24.71 -h1 { 
   24.72 -  copy-into: chapter-title element; 
   24.73 +h1 {
   24.74 +  copy-into: chapter-title element;
   24.75    font-size: 1.5em;
   24.76  }
   24.77  
   24.78 @@ -84,7 +85,7 @@
   24.79      font-variant: small-caps;
   24.80      }
   24.81  }
   24.82 -</pre> 
   24.83 +</pre>
   24.84  </div>
   24.85  
   24.86  
   24.87 @@ -102,10 +103,10 @@
   24.88  <dt><dfn>:first-of-page</dfn></dt>
   24.89  <dd>Same as :nth-of-page(n), but where n = 1 (it is the first matched element on the page).</dd>
   24.90  
   24.91 -<dt><dfn>:last-of-page</dfn></dt>      
   24.92 +<dt><dfn>:last-of-page</dfn></dt>
   24.93  <dd>The element is the last matched element on the page.</dd>
   24.94  
   24.95 -<dt><dfn>:start-of-page</dfn></dt>     
   24.96 +<dt><dfn>:start-of-page</dfn></dt>
   24.97  <dd>The element is the first matched element on the page, and neither it nor its ancestors have any previous siblings that appear on the page.</dd>
   24.98  
   24.99  </dl>
  24.100 @@ -122,13 +123,13 @@
  24.101  CSS:
  24.102  
  24.103  <pre>
  24.104 -h1::before { 
  24.105 -  content: 'Chapter 'counter(chapterNumber); 
  24.106 +h1::before {
  24.107 +  content: 'Chapter 'counter(chapterNumber);
  24.108  }
  24.109 -h1:first-of-page { 
  24.110 +h1:first-of-page {
  24.111    copy-into: headerP1 counter(chapter), headerP2;
  24.112  }
  24.113 -h1::after { 
  24.114 +h1::after {
  24.115    content: '.' copy-into: headerP3;
  24.116  }
  24.117  
  24.118 @@ -167,18 +168,18 @@
  24.119  @page {
  24.120     size: 15cm 10cm;
  24.121     margin: 1.5cm;
  24.122 -   
  24.123 +
  24.124     @top-left {
  24.125 -   content: "first: " heading1; 
  24.126 +   content: "first: " heading1;
  24.127     }
  24.128     @top-center {
  24.129 -   content: "start: " heading2; 
  24.130 +   content: "start: " heading2;
  24.131     }
  24.132      @top-right {
  24.133 -    content: "last: " heading3; 
  24.134 +    content: "last: " heading3;
  24.135     }
  24.136    }
  24.137 -  
  24.138 +
  24.139  h2:first-of-page { copy-into: heading1 }
  24.140  h2:start-of-page { copy-into: heading2 }
  24.141  h2:last-of-page { copy-into: heading3 }
  24.142 @@ -242,12 +243,12 @@
  24.143  <h2 id="footnotes">
  24.144  	Footnotes
  24.145  </h2>
  24.146 -Ancillary content may be moved to the bottom or side of a page. A footnote is created when such content moves to the bottom of the page, leaving a reference indicator. 
  24.147 +Ancillary content may be moved to the bottom or side of a page. A footnote is created when such content moves to the bottom of the page, leaving a reference indicator.
  24.148  
  24.149  
  24.150  <h3 id="footnote-terms">Terminology</h3>
  24.151  
  24.152 -Footnotes are complex objects, so it will be helpful to define some terms before proceeding. 
  24.153 +Footnotes are complex objects, so it will be helpful to define some terms before proceeding.
  24.154  
  24.155  <figure>
  24.156  
  24.157 @@ -285,11 +286,11 @@
  24.158  
  24.159  
  24.160  <div class="example">
  24.161 -HTML: 
  24.162 +HTML:
  24.163  <pre style="word-wrap: break-word; white-space: pre-wrap;">
  24.164  &lt;p>Though the body was erect, the head was thrown back so that the closed eyes were pointed towards the needle of the tell-tale that swung from a beam in the ceiling..&lt;span class="reference">&lt;span class="footnote">The cabin-compass is called the tell-tale, because without going to the compass at the helm, the Captain, while below, can inform himself of the course of the ship.&lt;/span>&lt;/span>&lt;/p>
  24.165 -</pre> 
  24.166 -CSS: 
  24.167 +</pre>
  24.168 +CSS:
  24.169  <pre>
  24.170  span.footnote {
  24.171    flow-into: footnote;
  24.172 @@ -316,11 +317,11 @@
  24.173      width: 352pt;
  24.174      height: auto;
  24.175      border-top: .25pt solid black;
  24.176 -    vertical-align: bottom; 
  24.177 +    vertical-align: bottom;
  24.178      wrap-flow: clear;
  24.179    }
  24.180  }
  24.181 -</pre> 
  24.182 +</pre>
  24.183  </div>
  24.184  
  24.185  <p class="issue">The above HTML contains two nested spans for the footnote, as CSS has no mechanism to leave a reference object where something was removed from the flow.</p>

    25.1 --- a/css-gcpm/Overview.src.html	Fri May 29 16:46:00 2015 -0700
    25.2 +++ b/css-gcpm/Overview.src.html	Fri May 29 16:46:19 2015 -0700
    25.3 @@ -1,6 +1,7 @@
    25.4  <h1>CSS Generated Content for Paged Media Module</h1>
    25.5  <pre class='metadata'>
    25.6  Status: ED
    25.7 +Work Status: Exploring
    25.8  Shortname: css-gcpm
    25.9  Level: 3
   25.10  Group: csswg

    26.1 --- a/css-grid/Overview.bs	Fri May 29 16:46:00 2015 -0700
    26.2 +++ b/css-grid/Overview.bs	Fri May 29 16:46:19 2015 -0700
    26.3 @@ -2,6 +2,7 @@
    26.4  
    26.5  <pre class='metadata'>
    26.6  Status: ED
    26.7 +Work Status: Revising
    26.8  Shortname: css-grid
    26.9  Level: 1
   26.10  Group: csswg

    27.1 --- a/css-images-4/Overview.bs	Fri May 29 16:46:00 2015 -0700
    27.2 +++ b/css-images-4/Overview.bs	Fri May 29 16:46:19 2015 -0700
    27.3 @@ -2,6 +2,7 @@
    27.4  
    27.5  <pre class='metadata'>
    27.6  Status: ED
    27.7 +Work Status: Exploring
    27.8  Shortname: css-images
    27.9  Level: 4
   27.10  Group: csswg

    28.1 --- a/css-images/Overview.bs	Fri May 29 16:46:00 2015 -0700
    28.2 +++ b/css-images/Overview.bs	Fri May 29 16:46:19 2015 -0700
    28.3 @@ -6,6 +6,7 @@
    28.4  Group: csswg
    28.5  ED: http://dev.w3.org/csswg/css-images-3/
    28.6  TR: http://www.w3.org/TR/css3-images/
    28.7 +Work Status: Testing
    28.8  Editor: Tab Atkins Jr., Google, http://xanthir.com/contact/
    28.9  Editor: fantasai, Mozilla, http://fantasai.inkedblade.net/contact
   28.10  Abstract: This module contains the features of CSS level 3 relating to the <<image>> type and replaced elements. It includes and extends the functionality of CSS level 2 [[CSS21]]. The main extensions compared to CSS2.1 are the generalization of the <<url>> type to the <<image>> type, several additions to the <<image>> type, a generic sizing algorithm for images and other replaced content in CSS, definitions for interpolating several <<image>> types, and several properties controlling the interaction of replaced elements and CSS's layout models.

    29.1 --- a/css-inline/Overview.bs	Fri May 29 16:46:00 2015 -0700
    29.2 +++ b/css-inline/Overview.bs	Fri May 29 16:46:19 2015 -0700
    29.3 @@ -9,6 +9,7 @@
    29.4  Shortname: css-inline
    29.5  Level: 3
    29.6  Status: ED
    29.7 +Work Status: Exploring
    29.8  Group: csswg
    29.9  TR: http://www.w3.org/TR/css-inline/
   29.10  ED: http://dev.w3.org/csswg/css-inline/

    30.1 --- a/css-line-grid/Overview.bs	Fri May 29 16:46:00 2015 -0700
    30.2 +++ b/css-line-grid/Overview.bs	Fri May 29 16:46:19 2015 -0700
    30.3 @@ -2,6 +2,7 @@
    30.4  
    30.5  <pre class='metadata'>
    30.6  Status: ED
    30.7 +Work Status: Exploring
    30.8  Shortname: css-line-grid
    30.9  Level: 1
   30.10  Group: csswg
   30.11 @@ -44,11 +45,11 @@
   30.12  
   30.13  <em>This section is not normative.</em>
   30.14  
   30.15 -	This specification provides features 
   30.16 -	to align lines and blocks 
   30.17 +	This specification provides features
   30.18 +	to align lines and blocks
   30.19  	to invisible grids in the document.
   30.20  
   30.21 -	Aligning lines and blocks to grids 
   30.22 +	Aligning lines and blocks to grids
   30.23  	provides the following benefits:
   30.24  
   30.25  	<ul>
   30.26 @@ -75,7 +76,7 @@
   30.27  
   30.28  	There are several types of objects in a document
   30.29  	that can break the vertical rhythm.
   30.30 -	Examples include lines with different sizes of text, 
   30.31 +	Examples include lines with different sizes of text,
   30.32  	pictures, and tables.
   30.33  
   30.34  	<div class="figure">
   30.35 @@ -95,9 +96,9 @@
   30.36  			<p class="caption">Large text wraps within line grids.</p>
   30.37  		</div>
   30.38  
   30.39 -		When a different size of text, 
   30.40 -		such as a headings wraps, 
   30.41 -		it is usually aligned to grids as a block 
   30.42 +		When a different size of text,
   30.43 +		such as a headings wraps,
   30.44 +		it is usually aligned to grids as a block
   30.45  		and the lines within the block do not align.
   30.46  
   30.47  		<br style="clear:both;"/>
   30.48 @@ -116,8 +117,8 @@
   30.49  			</div>
   30.50  			<div class="sidenote-note">
   30.51  
   30.52 -				Even if the author controls all this, 
   30.53 -				the baselines won't align. And careful 
   30.54 +				Even if the author controls all this,
   30.55 +				the baselines won't align. And careful
   30.56  				calculations can be thrown off by user stylesheets.
   30.57  			</div>
   30.58  		</div>
   30.59 @@ -125,7 +126,7 @@
   30.60  	</div>
   30.61  
   30.62  	<figure>
   30.63 -		<img src="images/sidenote-aligned.png" 
   30.64 +		<img src="images/sidenote-aligned.png"
   30.65  			alt="sidenote rendering with aligned baselines"/>
   30.66  		<figcaption>
   30.67  			Sidenote with baselines aligned to the body text.
   30.68 @@ -143,7 +144,7 @@
   30.69  
   30.70  	East Asian layouts may require grid-like features
   30.71  	in inline progression direction as well.
   30.72 -	
   30.73 +
   30.74  	It is often desirable in East Asian layouts
   30.75  	to make the line width
   30.76  	a multiple of <em>em</em> without fractions.
   30.77 @@ -159,16 +160,16 @@
   30.78  	</ul>
   30.79  
   30.80  	It is important to control these capabilities independently,
   30.81 -	so that, for example, 
   30.82 +	so that, for example,
   30.83  	aligning to grids can be turned off for tables,
   30.84 -	but can then be turned back on 
   30.85 +	but can then be turned back on
   30.86  	for aligning the following text to the grids.
   30.87  
   30.88  
   30.89  <h3 id='placement'>
   30.90  Module Interactions</h3>
   30.91  
   30.92 -	This module extends the line box model 
   30.93 +	This module extends the line box model
   30.94  	defined in [[!CSS21]] sections 9.4.2 and 10.8.
   30.95  
   30.96  <h3 id='values'>
   30.97 @@ -177,26 +178,26 @@
   30.98  	This specification follows the
   30.99  	<a href="http://www.w3.org/TR/CSS21/about.html#property-defs">
  30.100  		CSS property definition conventions
  30.101 -	</a> 
  30.102 -	from [[!CSS21]]. 
  30.103 -	Value types not defined in this specification 
  30.104 -	are defined in CSS Level 2 Revision 1 [[!CSS21]]. 
  30.105 -	Other CSS modules may expand 
  30.106 -	the definitions of these value types: 
  30.107 -	for example [[CSS3COLOR]], 
  30.108 -	when combined with this module, 
  30.109 -	expands the definition 
  30.110 -	of the &lt;color&gt; value type 
  30.111 +	</a>
  30.112 +	from [[!CSS21]].
  30.113 +	Value types not defined in this specification
  30.114 +	are defined in CSS Level 2 Revision 1 [[!CSS21]].
  30.115 +	Other CSS modules may expand
  30.116 +	the definitions of these value types:
  30.117 +	for example [[CSS3COLOR]],
  30.118 +	when combined with this module,
  30.119 +	expands the definition
  30.120 +	of the &lt;color&gt; value type
  30.121  	as used in this specification.
  30.122 -	
  30.123 -	In addition to the property-specific values 
  30.124 -	listed in their definitions, 
  30.125 -	all properties defined in this specification 
  30.126 +
  30.127 +	In addition to the property-specific values
  30.128 +	listed in their definitions,
  30.129 +	all properties defined in this specification
  30.130  	also accept the
  30.131  	<a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a>
  30.132 -	keyword as their property value. 
  30.133 +	keyword as their property value.
  30.134  	For readability it has not been repeated explicitly.
  30.135 -	
  30.136 +
  30.137  <h2 id='line-grid-property'>
  30.138  Defining a <dfn>Line Grid</dfn>: the 'line-grid' property</h2>
  30.139  
  30.140 @@ -212,12 +213,12 @@
  30.141  		Computed Value: as specified
  30.142  	</pre>
  30.143  
  30.144 -	Specifies whether this box creates 
  30.145 -	a new baseline grid for its descendants 
  30.146 -	or uses the same baseline grid as its parent. 
  30.147 -	(Each box always has an associated <a>line grid</a>. 
  30.148 -	However, whether a box or its contents snap 
  30.149 -	to a <a>line grid</a> is determined 
  30.150 +	Specifies whether this box creates
  30.151 +	a new baseline grid for its descendants
  30.152 +	or uses the same baseline grid as its parent.
  30.153 +	(Each box always has an associated <a>line grid</a>.
  30.154 +	However, whether a box or its contents snap
  30.155 +	to a <a>line grid</a> is determined
  30.156  	by 'line-snap' and 'box-snap'.)
  30.157  
  30.158  	The values of this property have the following meanings:
  30.159 @@ -227,21 +228,21 @@
  30.160  		<dd>Box assumes the <a>line grid</a> of its parent.
  30.161  
  30.162  		<dt><dfn>create</dfn>
  30.163 -		<dd>Box creates a new <a>line grid</a> 
  30.164 -			using its own font and line layout settings. 
  30.165 -			The <a>line grid</a> consists of a series 
  30.166 -			of horizontal lines corresponding 
  30.167 -			to all the baselines 
  30.168 -			(alphabetic, text-top, text-bottom, 
  30.169 -			mathematic, central, hanging, etc.) 
  30.170 -			and to the line-over and line-under edges, 
  30.171 -			positioned where they would fall 
  30.172 -			if the contents of this element consisted entirely 
  30.173 -			of line boxes filled with text (no sub-elements) 
  30.174 -			using the first available font. 
  30.175 -			If the box is paginated, 
  30.176 -			the <a>line grid</a> is restarted on each page; 
  30.177 -			since line boxes cannot be fragmented, 
  30.178 +		<dd>Box creates a new <a>line grid</a>
  30.179 +			using its own font and line layout settings.
  30.180 +			The <a>line grid</a> consists of a series
  30.181 +			of horizontal lines corresponding
  30.182 +			to all the baselines
  30.183 +			(alphabetic, text-top, text-bottom,
  30.184 +			mathematic, central, hanging, etc.)
  30.185 +			and to the line-over and line-under edges,
  30.186 +			positioned where they would fall
  30.187 +			if the contents of this element consisted entirely
  30.188 +			of line boxes filled with text (no sub-elements)
  30.189 +			using the first available font.
  30.190 +			If the box is paginated,
  30.191 +			the <a>line grid</a> is restarted on each page;
  30.192 +			since line boxes cannot be fragmented,
  30.193  			no page begins with the bottom part of a line's grid.
  30.194  	</dl>
  30.195  
  30.196 @@ -277,12 +278,12 @@
  30.197  		<pre>
  30.198  			main { line-grid: create; }
  30.199  		</pre>
  30.200 -		
  30.201 +
  30.202  		If this <a>line grid</a> is then paginated, the <a>line grid</a> will start at the top of each page area after the first.
  30.203  
  30.204  		In other cases, it's desirable for
  30.205 -		all pages of a document share a common <a>line grid</a>, 
  30.206 -		even if page margins, border and/or padding change. 
  30.207 +		all pages of a document share a common <a>line grid</a>,
  30.208 +		even if page margins, border and/or padding change.
  30.209  		The following rule will instead fill the page box area
  30.210  		<em>including</em> the page margin/padding/borders
  30.211  		with the <a>line grid</a>:
  30.212 @@ -295,36 +296,36 @@
  30.213  		(where the content would normally begin).
  30.214  	</div>
  30.215  
  30.216 -	Issue: The names of these values is currently up for debate. 
  30.217 +	Issue: The names of these values is currently up for debate.
  30.218  	Current suggestions for match-parent
  30.219 -	include match-parent and normal; 
  30.220 +	include match-parent and normal;
  30.221  	those for create include create and new.
  30.222  
  30.223  	<p class="note">The original proposal for line grids
  30.224 -	allowed an element to create a named grid. 
  30.225 +	allowed an element to create a named grid.
  30.226  	This property could still be extended to do this in the future.
  30.227 -	
  30.228 -	<p class="note">There might need to be an offset 
  30.229 -	for more complicated designs. 
  30.230 -	How to set this offset is problematic: 
  30.231 -	usually it's not a fixed length, 
  30.232 -	but the distance to clear some header content. 
  30.233 +
  30.234 +	<p class="note">There might need to be an offset
  30.235 +	for more complicated designs.
  30.236 +	How to set this offset is problematic:
  30.237 +	usually it's not a fixed length,
  30.238 +	but the distance to clear some header content.
  30.239  	This could be added to a later level of css-line-grid.
  30.240  
  30.241  <h2 id='grid-snapping'>
  30.242  Snapping to a Grid</h2>
  30.243  
  30.244 -	The 'line-snap' and 'box-snap' properties 
  30.245 -	cause line boxes and block boxes to shift position 
  30.246 +	The 'line-snap' and 'box-snap' properties
  30.247 +	cause line boxes and block boxes to shift position
  30.248  	in order to align to the <a>line grid</a>.
  30.249 -	Shifting boxes in this way affects layout – 
  30.250 +	Shifting boxes in this way affects layout –
  30.251  	it is not merely a display translation.
  30.252 -	If a line box is shifted, 
  30.253 -	then subsequent line boxes will be laid out 
  30.254 -	using the new shifted position as input 
  30.255 +	If a line box is shifted,
  30.256 +	then subsequent line boxes will be laid out
  30.257 +	using the new shifted position as input
  30.258  	to their line stacking rules.
  30.259 -	If a block box is shifted, 
  30.260 -	then subsequent boxes will be laid out 
  30.261 +	If a block box is shifted,
  30.262 +	then subsequent boxes will be laid out
  30.263  	using the new shifted position as input.
  30.264  
  30.265  <h3 id='line-snap'>
  30.266 @@ -342,17 +343,17 @@
  30.267  		Computed Value: as specified
  30.268  	</pre>
  30.269  
  30.270 -	This property applies to all the line boxes 
  30.271 -	directly contained by the element, 
  30.272 -	and, when not none, 
  30.273 -	causes each line box to shift 
  30.274 -	(usually downward, possibly by zero) 
  30.275 -	until it snaps to the <a>line grid</a> 
  30.276 -	specified by 'line-grid'. 
  30.277 -	(The unshifted position is the position that 
  30.278 -	would be determined by normal line stacking rules, 
  30.279 -	with consideration of any new controls 
  30.280 -	defined by other modules such as [[CSS3LINE]].) 
  30.281 +	This property applies to all the line boxes
  30.282 +	directly contained by the element,
  30.283 +	and, when not none,
  30.284 +	causes each line box to shift
  30.285 +	(usually downward, possibly by zero)
  30.286 +	until it snaps to the <a>line grid</a>
  30.287 +	specified by 'line-grid'.
  30.288 +	(The unshifted position is the position that
  30.289 +	would be determined by normal line stacking rules,
  30.290 +	with consideration of any new controls
  30.291 +	defined by other modules such as [[CSS3LINE]].)
  30.292  
  30.293  
  30.294  	Values have the following meanings:
  30.295 @@ -365,65 +366,65 @@
  30.296  		<a>line grid</a> applying to the element.
  30.297  	<dt><dfn>contain</dfn>
  30.298  		<dd>
  30.299 -			Two baselines are used to align the line box: 
  30.300 -			the line box is snapped 
  30.301 -			so that its <a href="http://dev.w3.org/csswg/css-inline/#central">central</a> baseline 
  30.302 -			is centered between one 
  30.303 -			of the line grid's <a href="http://dev.w3.org/csswg/css-inline/#text-over-edge">text-over-edge</a> baselines 
  30.304 -			and a subsequent (but not necessarily consecutive) 
  30.305 +			Two baselines are used to align the line box:
  30.306 +			the line box is snapped
  30.307 +			so that its <a href="http://dev.w3.org/csswg/css-inline/#central">central</a> baseline
  30.308 +			is centered between one
  30.309 +			of the line grid's <a href="http://dev.w3.org/csswg/css-inline/#text-over-edge">text-over-edge</a> baselines
  30.310 +			and a subsequent (but not necessarily consecutive)
  30.311  			<a href="http://dev.w3.org/csswg/css-inline/#text-under-edge">text-under-edge</a> baseline.
  30.312  	</dl>
  30.313  
  30.314  	<div class="example">
  30.315  
  30.316 -	Line boxes almost always shift downward 
  30.317 -	(towards the block-end direction) 
  30.318 -	when snapping to a <a>line grid</a>. 
  30.319 -	Here there are three lines 
  30.320 -	with 20px line-height 
  30.321 -	and line-snap:baseline 
  30.322 -	that should snap to a 30px <a>line grid</a>. 
  30.323 -	Each line box shifts down 
  30.324 -	so that the baselines align 
  30.325 +	Line boxes almost always shift downward
  30.326 +	(towards the block-end direction)
  30.327 +	when snapping to a <a>line grid</a>.
  30.328 +	Here there are three lines
  30.329 +	with 20px line-height
  30.330 +	and line-snap:baseline
  30.331 +	that should snap to a 30px <a>line grid</a>.
  30.332 +	Each line box shifts down
  30.333 +	so that the baselines align
  30.334  	with the grid lines.
  30.335  
  30.336  		<figure style="float:left;">
  30.337 -			<img src="images/simple-no-snap.png" 
  30.338 +			<img src="images/simple-no-snap.png"
  30.339  				alt="line positions before snapping"/>
  30.340  			<figcaption>
  30.341  				Before line snapping
  30.342  			</figcaption>
  30.343  		</figure>
  30.344  		<figure style="float:left;">
  30.345 -			<img src="images/simple-snapped.png" 
  30.346 +			<img src="images/simple-snapped.png"
  30.347  				alt="line positions after snapping"/>
  30.348  			<figcaption>
  30.349  				After line snapping
  30.350  			</figcaption>
  30.351  		</figure>
  30.352  		<p style="clear:left;">
  30.353 -			In the figures below, 
  30.354 -			there are two additional lines 
  30.355 -			from h3 elements with line-snap:none. 
  30.356 -			These lines do not shift 
  30.357 -			to align to the grid, 
  30.358 -			but their positions can change 
  30.359 -			based on the shifting of lines around them. 
  30.360 -			In this example, 
  30.361 -			lines 1 2 and 3 shift down 
  30.362 -			to snap their baselines to the grid lines, 
  30.363 -			and line B has normal line box placement 
  30.364 +			In the figures below,
  30.365 +			there are two additional lines
  30.366 +			from h3 elements with line-snap:none.
  30.367 +			These lines do not shift
  30.368 +			to align to the grid,
  30.369 +			but their positions can change
  30.370 +			based on the shifting of lines around them.
  30.371 +			In this example,
  30.372 +			lines 1 2 and 3 shift down
  30.373 +			to snap their baselines to the grid lines,
  30.374 +			and line B has normal line box placement
  30.375  			just below the line above.
  30.376  		</p>
  30.377  		<figure style="float:left;">
  30.378 -			<img src="images/top-no-snap.png" 
  30.379 +			<img src="images/top-no-snap.png"
  30.380  				alt="line positions before snapping"/>
  30.381  			<figcaption>
  30.382  				Before line snapping
  30.383  			</figcaption>
  30.384  		</figure>
  30.385  		<figure style="float:left;">
  30.386 -			<img src="images/top-snapped.png" 
  30.387 +			<img src="images/top-snapped.png"
  30.388  				alt="line positions after snapping"/>
  30.389  			<figcaption>
  30.390  				After line snapping
  30.391 @@ -434,23 +435,23 @@
  30.392  <h3 id='box-snap'>
  30.393  Snapping Block Boxes: the 'box-snap' property</h3>
  30.394  
  30.395 -	Issue: This is a rough draft of trying to solve 
  30.396 +	Issue: This is a rough draft of trying to solve
  30.397  	the box-snapping problem.
  30.398  
  30.399 -	Issue: Some optional box values 
  30.400 -	(margin-box, border-box) 
  30.401 -	could be added to the before and after values 
  30.402 -	to allow snapping various box model edges 
  30.403 +	Issue: Some optional box values
  30.404 +	(margin-box, border-box)
  30.405 +	could be added to the before and after values
  30.406 +	to allow snapping various box model edges
  30.407  	to the <a>line grid</a>.
  30.408  
  30.409 -	Issue: An auto value could be useful - 
  30.410 -	one that defaults to center, 
  30.411 -	but snaps to before if it's the first block in a fragment container, 
  30.412 +	Issue: An auto value could be useful -
  30.413 +	one that defaults to center,
  30.414 +	but snaps to before if it's the first block in a fragment container,
  30.415  	and snaps to after if it's the last block in a fragment container.
  30.416  
  30.417  	<pre class='propdef'>
  30.418  		Name: box-snap
  30.419 -		Value: none | block-start | block-end | center | baseline | last-baseline 
  30.420 +		Value: none | block-start | block-end | center | baseline | last-baseline
  30.421  		Initial: none
  30.422  		Applies to: block-level boxes and internal table elements except table cells
  30.423  		Inherited: yes
  30.424 @@ -461,7 +462,7 @@
  30.425  	</pre>
  30.426  
  30.427  	Specifies how the block is snapped to the baseline grid.
  30.428 -	
  30.429 +
  30.430  	Values have the following meanings:
  30.431  
  30.432  	<dl dfn-type="value" dfn-for="box-snap">
  30.433 @@ -481,71 +482,71 @@
  30.434  		<dd>The last line box's dominant baseline is snapped to the nearest grid line.
  30.435  	</dl>
  30.436  
  30.437 -	Snapping block boxes always uses the <a>line grid</a> of the box parent 
  30.438 +	Snapping block boxes always uses the <a>line grid</a> of the box parent
  30.439  	(a block's own <a>line grid</a> has no effect on box snapping).
  30.440 -	If the box is an empty block that could be 
  30.441 -	<a href="http://www.w3.org/TR/CSS21/box.html">collapsed through</a>, 
  30.442 +	If the box is an empty block that could be
  30.443 +	<a href="http://www.w3.org/TR/CSS21/box.html">collapsed through</a>,
  30.444  	then this property has no effect. [[!CSS21]]
  30.445  
  30.446 -	To snap a block-level element to a grid line, 
  30.447 +	To snap a block-level element to a grid line,
  30.448  	take the unsnapped result of layout
  30.449  	(including margin collapsing, clearance, etc.)
  30.450 -	as the block's initial position, 
  30.451 -	then shift the block downward 
  30.452 -	(towards the block-end direction) 
  30.453 +	as the block's initial position,
  30.454 +	then shift the block downward
  30.455 +	(towards the block-end direction)
  30.456  	until it snaps to the <a>line grid</a>.
  30.457  
  30.458 -	For the ''block-start'' and ''block-end'' values, 
  30.459 -	either the text-over-edge 
  30.460 -	or text-under-edge baseline is chosen: 
  30.461 -	whichever one is on the matching side 
  30.462 -	of the central baseline. 
  30.463 -	For example, 
  30.464 -	when snapping the block-start edge 
  30.465 -	in horizontal writing mode, 
  30.466 -	the text-over-edge is chosen. 
  30.467 -	In some cases the text-under-edge  
  30.468 -	might be used instead for the block-start edge: 
  30.469 -	for example, 
  30.470 -	when the writing mode of the <a>line grid</a> 
  30.471 -	doesn't match that of the affected element, 
  30.472 -	or when due to the 'text-orientation' settings 
  30.473 +	For the ''block-start'' and ''block-end'' values,
  30.474 +	either the text-over-edge
  30.475 +	or text-under-edge baseline is chosen:
  30.476 +	whichever one is on the matching side
  30.477 +	of the central baseline.
  30.478 +	For example,
  30.479 +	when snapping the block-start edge
  30.480 +	in horizontal writing mode,
  30.481 +	the text-over-edge is chosen.
  30.482 +	In some cases the text-under-edge
  30.483 +	might be used instead for the block-start edge:
  30.484 +	for example,
  30.485 +	when the writing mode of the <a>line grid</a>
  30.486 +	doesn't match that of the affected element,
  30.487 +	or when due to the 'text-orientation' settings
  30.488  	the text-under-edge corresponds to the block-start edge.
  30.489  
  30.490    <!--To snap an after border-box or half-border edge to a grid
  30.491 -	line, the effective content-box height is increased.--> 
  30.492 +	line, the effective content-box height is increased.-->
  30.493  
  30.494 -	When applied to table row group and table row boxes, 
  30.495 -	'box-snap' only affects the before and after edges, 
  30.496 -	and only if those edges are not 
  30.497 -	at the beginning or end of the table, respectively. 
  30.498 -	To snap a before edge on a table row or row group, 
  30.499 -	the preceding row's height is increased. 
  30.500 -	To snap an after edge on a table row or row group, 
  30.501 +	When applied to table row group and table row boxes,
  30.502 +	'box-snap' only affects the before and after edges,
  30.503 +	and only if those edges are not
  30.504 +	at the beginning or end of the table, respectively.
  30.505 +	To snap a before edge on a table row or row group,
  30.506 +	the preceding row's height is increased.
  30.507 +	To snap an after edge on a table row or row group,
  30.508  	the affected row's height is increased.
  30.509  
  30.510 -	When applied to table column group and table column boxes, 
  30.511 -	'box-snap'only affects the start and end edges, 
  30.512 -	and only if those edges are not 
  30.513 -	at the start or end of the table, respectively. 
  30.514 -	How the space is redistributed among columns 
  30.515 +	When applied to table column group and table column boxes,
  30.516 +	'box-snap'only affects the start and end edges,
  30.517 +	and only if those edges are not
  30.518 +	at the start or end of the table, respectively.
  30.519 +	How the space is redistributed among columns
  30.520  	to satisfy snapping constraints is not defined, however:
  30.521  	<ul>
  30.522  		<li>In an auto-sized table no column may be smaller than its minimum content width.
  30.523  		<li>The resulting table must not exceed its original measure if it had a non-auto measure.
  30.524  		<li>The adjusted widths must not cause the table to overflow its containing block any more than it would with ''box-snap: none''.
  30.525  	</ul>
  30.526 -	
  30.527 +
  30.528  	To satisfy these constraints, some column edges may remain unsnapped.
  30.529  
  30.530 -<!-- 
  30.531 +<!--
  30.532  	Line snapping for columns is processed from start to end: column widths
  30.533  	are increased or decreased in order to snap the column edges.
  30.534  	By preference, the widths are increased.
  30.535  	However if the table has an explicit size or is auto-sized and the resulting
  30.536  	table overflows its containing block, then columns whose widths were
  30.537  	increased must, one by one, switch their snap to decreasing the column
  30.538 -	width, until the table reaches its specified size or 
  30.539 +	width, until the table reaches its specified size or
  30.540  -->
  30.541  <!--
  30.542  	<p>For internal table elements in separated borders tables, ''margin-box''
  30.543 @@ -556,12 +557,12 @@
  30.544  -->
  30.545  
  30.546  	<div class="issue">
  30.547 -		Going forward, we could add a 2-d box-snap 
  30.548 +		Going forward, we could add a 2-d box-snap
  30.549  		with more controls
  30.550 -		and to also extend it to handle snapping 
  30.551 +		and to also extend it to handle snapping
  30.552  		to an explicit layout grid
  30.553  		(not just the baseline grid).
  30.554 -		Current thoughts are for box-snap 
  30.555 +		Current thoughts are for box-snap
  30.556  		to break out into longhands;
  30.557  		the current block-snap property should thus be a subset of its expected future values.
  30.558  		Below is an outline of the structure.
  30.559 @@ -582,9 +583,9 @@
  30.560  			        +- inline-snap-align: <<content-position>>
  30.561  			        +- inline-snap-grid: text-grid | <<custom-ident>> /* name of grid/gridlines */
  30.562  
  30.563 -			where <<shape-box>> includes 
  30.564 +			where <<shape-box>> includes
  30.565  				margin-box | border-box | half-border-box | padding-box | content-box
  30.566 -			and <<content-position>> includes 
  30.567 +			and <<content-position>> includes
  30.568  				start | end | stretch | first-baseline | last-baseline | center
  30.569  		</pre>
  30.570  	</div>
  30.571 @@ -595,11 +596,11 @@
  30.572  <h3 id='alignment-interactions'>
  30.573  Interacting with other alignments</h3>
  30.574  
  30.575 -	An element can have additional block layout constraints 
  30.576 -	(such as centering or 'box-snap') 
  30.577 -	that can complicate line snapping. 
  30.578 -	In these cases, 
  30.579 -	implementations must produce 
  30.580 +	An element can have additional block layout constraints
  30.581 +	(such as centering or 'box-snap')
  30.582 +	that can complicate line snapping.
  30.583 +	In these cases,
  30.584 +	implementations must produce
  30.585  	the same result as the steps below:
  30.586  
  30.587  	<ul>
  30.588 @@ -610,12 +611,12 @@
  30.589  			Apply the layout constraint to the block
  30.590  		</li>
  30.591  		<li>
  30.592 -			Adjust exactly one line box shift 
  30.593 -			or space at the beginning or end of the block 
  30.594 -			such that all of the snapping lines meet the <a>line grid</a> 
  30.595 -			while maintaining the block layout constraint. 
  30.596 -			The single adjustment chosen must be 
  30.597 -			the smallest shift needed to achieve the result 
  30.598 +			Adjust exactly one line box shift
  30.599 +			or space at the beginning or end of the block
  30.600 +			such that all of the snapping lines meet the <a>line grid</a>
  30.601 +			while maintaining the block layout constraint.
  30.602 +			The single adjustment chosen must be
  30.603 +			the smallest shift needed to achieve the result
  30.604  			without causing overflow.
  30.605  		</li>
  30.606  	</ul>
  30.607 @@ -623,48 +624,48 @@
  30.608  	<div class="example">
  30.609  
  30.610  		A block containing lines to snap
  30.611 -		might not be top-aligned within its container. 
  30.612 -		In the figures below, 
  30.613 -		the block containing the elements is centered. 
  30.614 -		In a centered situation, 
  30.615 -		you have to align baselines 
  30.616 -		while maintaining centering. 
  30.617 -		This can be done in two shift-and-center steps. 
  30.618 -		
  30.619 -		First, shift the snapping lines 
  30.620 -		as if the block was top-aligned  
  30.621 -		(as in figure 9 above), 
  30.622 -		then remove the shift 
  30.623 -		for the very first snapping line. 
  30.624 -		After removing the first shift, 
  30.625 -		try centering the block. 
  30.626 -		This is almost certain 
  30.627 -		to throw the baseline alignment off. 
  30.628 -		You can see one such result 
  30.629 +		might not be top-aligned within its container.
  30.630 +		In the figures below,
  30.631 +		the block containing the elements is centered.
  30.632 +		In a centered situation,
  30.633 +		you have to align baselines
  30.634 +		while maintaining centering.
  30.635 +		This can be done in two shift-and-center steps.
  30.636 +
  30.637 +		First, shift the snapping lines
  30.638 +		as if the block was top-aligned
  30.639 +		(as in figure 9 above),
  30.640 +		then remove the shift
  30.641 +		for the very first snapping line.
  30.642 +		After removing the first shift,
  30.643 +		try centering the block.
  30.644 +		This is almost certain
  30.645 +		to throw the baseline alignment off.
  30.646 +		You can see one such result
  30.647  		in the partial shifting figure below.
  30.648  
  30.649  		Second, measure the distance
  30.650 -		from the first snapped line's baseline 
  30.651 -		to the grid lines above and below, 
  30.652 -		looking for the closest grid line 
  30.653 +		from the first snapped line's baseline
  30.654 +		to the grid lines above and below,
  30.655 +		looking for the closest grid line
  30.656  		to that baseline.
  30.657  
  30.658 -		If the closest grid line 
  30.659 -		is in the block-start direction, 
  30.660 -		then add space below the last line in the block 
  30.661 -		equal to twice that distance. 
  30.662 -		Then the block is centered again, 
  30.663 +		If the closest grid line
  30.664 +		is in the block-start direction,
  30.665 +		then add space below the last line in the block
  30.666 +		equal to twice that distance.
  30.667 +		Then the block is centered again,
  30.668  		which will align all of the snapped lines to the grid.
  30.669  
  30.670  		<figure style="float:left;">
  30.671 -			<img src="images/first-center-part-snapped.png" 
  30.672 +			<img src="images/first-center-part-snapped.png"
  30.673  				alt="line positions at step 1"/>
  30.674  			<figcaption>
  30.675  				Partial shifting
  30.676  			</figcaption>
  30.677  		</figure>
  30.678  		<figure style="float:left;">
  30.679 -			<img src="images/first-center-snapped.png" 
  30.680 +			<img src="images/first-center-snapped.png"
  30.681  				alt="line positions after full snapping"/>
  30.682  			<figcaption>
  30.683  				Full line snapping
  30.684 @@ -672,22 +673,22 @@
  30.685  		</figure>
  30.686  
  30.687  		<p style="clear:left;">
  30.688 -			If the closest grid line 
  30.689 -			is in the block-end direction, 
  30.690 -			then the first snapped line is shifted downward 
  30.691 -			by twice that distance. 
  30.692 -			Then the block is centered again, 
  30.693 +			If the closest grid line
  30.694 +			is in the block-end direction,
  30.695 +			then the first snapped line is shifted downward
  30.696 +			by twice that distance.
  30.697 +			Then the block is centered again,
  30.698  			which will again align all of the snapped lines to the grid.
  30.699  		</p>
  30.700  		<figure style="float:left;">
  30.701 -			<img src="images/second-center-part-snapped.png" 
  30.702 +			<img src="images/second-center-part-snapped.png"
  30.703  				alt="line positions at step 1"/>
  30.704  			<figcaption>
  30.705  				Partial shifting
  30.706  			</figcaption>
  30.707  		</figure>
  30.708  		<figure style="float:left;">
  30.709 -			<img src="images/second-center-snapped.png" 
  30.710 +			<img src="images/second-center-snapped.png"
  30.711  				alt="line positions after full snapping"/>
  30.712  			<figcaption>
  30.713  				Full line snapping
  30.714 @@ -697,27 +698,27 @@
  30.715  
  30.716  	<div class="example">
  30.717  
  30.718 -		An end-aligned block also uses two steps, 
  30.719 +		An end-aligned block also uses two steps,
  30.720  		but is simpler than the centered case.
  30.721  
  30.722 -		First, shift the snapping lines 
  30.723 -		as if there were no end-alignment  
  30.724 -		(as in figure 9 above), 
  30.725 +		First, shift the snapping lines
  30.726 +		as if there were no end-alignment
  30.727 +		(as in figure 9 above),
  30.728  		then end-align the block.
  30.729  
  30.730 -		Second, shift the entire block contents upwards 
  30.731 -		until the last snapped line aligns to a grid line. 
  30.732 +		Second, shift the entire block contents upwards
  30.733 +		until the last snapped line aligns to a grid line.
  30.734  		In this example, the shift is very minor.
  30.735  
  30.736  		<figure style="float:left;">
  30.737 -			<img src="images/bottom-no-snap.png" 
  30.738 +			<img src="images/bottom-no-snap.png"
  30.739  				alt="line positions before snapping"/>
  30.740  			<figcaption>
  30.741  				Before snapping
  30.742  			</figcaption>
  30.743  		</figure>
  30.744  		<figure style="float:left;">
  30.745 -			<img src="images/bottom-snapped.png" 
  30.746 +			<img src="images/bottom-snapped.png"
  30.747  				alt="line positions after snapping"/>
  30.748  			<figcaption>
  30.749  				After line snapping
  30.750 @@ -728,34 +729,34 @@
  30.751  <h3 id='leading-adjustments'>
  30.752  Leading adjustments</h3>
  30.753  
  30.754 -	In some cases lines of equal line height 
  30.755 -	will not align perfectly to a baseline grid: 
  30.756 -	this happens, for example, 
  30.757 -	when fonts (of the same size) 
  30.758 -	with different baseline tables 
  30.759 -	are mixed on a line. 
  30.760 -	In these cases, 
  30.761 -	removing top half-leading can sometimes be 
  30.762 +	In some cases lines of equal line height
  30.763 +	will not align perfectly to a baseline grid:
  30.764 +	this happens, for example,
  30.765 +	when fonts (of the same size)
  30.766 +	with different baseline tables
  30.767 +	are mixed on a line.
  30.768 +	In these cases,
  30.769 +	removing top half-leading can sometimes be
  30.770  	the correct thing to do,
  30.771 -	but must be limited 
  30.772 +	but must be limited
  30.773  	to the amount of baseline discrepancy
  30.774  	so as not to trigger in other cases.
  30.775  
  30.776 -	Issue: Details to follow. 
  30.777 -	It's complicated when you have 
  30.778 -	more than one font-size or line-height 
  30.779 +	Issue: Details to follow.
  30.780 +	It's complicated when you have
  30.781 +	more than one font-size or line-height
  30.782  	in a single line box.
  30.783  
  30.784  <h2 class=no-num id='acknowledgments'>Acknowledgments</h2>
  30.785  
  30.786 -	This module was made possible by the advice and contributions of 
  30.787 -	Tab Atkins, 
  30.788 -	Dave Cramer, 
  30.789 -	Dave Hyatt, 
  30.790 -	Bem Jones-Bey, 
  30.791 -	HÃ¥kon Wium Lie, 
  30.792 -	Shinyu Murakami, 
  30.793 -	Liam Quin, 
  30.794 +	This module was made possible by the advice and contributions of
  30.795 +	Tab Atkins,
  30.796 +	Dave Cramer,
  30.797 +	Dave Hyatt,
  30.798 +	Bem Jones-Bey,
  30.799 +	HÃ¥kon Wium Lie,
  30.800 +	Shinyu Murakami,
  30.801 +	Liam Quin,
  30.802  	and the CSS Working Group members.
  30.803  
  30.804  <h2 class=no-num id='change-log'>
  30.805 @@ -780,4 +781,4 @@
  30.806  		<li>Removed grid units</li>
  30.807  		<li>Removed 2d box snapping</li>
  30.808  		<li>Removed rounding functions</li>
  30.809 -	</ul>
  30.810 \ No newline at end of file
  30.811 +	</ul>

    31.1 --- a/css-lists/Overview.bs	Fri May 29 16:46:00 2015 -0700
    31.2 +++ b/css-lists/Overview.bs	Fri May 29 16:46:19 2015 -0700
    31.3 @@ -4,6 +4,7 @@
    31.4  Level: 3
    31.5  Group: CSSWG
    31.6  Status: ED
    31.7 +Work Status: Exploring
    31.8  ED: http://dev.w3.org/csswg/css3-lists/
    31.9  TR: http://www.w3.org/TR/css3-lists/
   31.10  Editor: Tab Atkins, Google, http://xanthir.com/contact/

    32.1 --- a/css-logical-props/Overview.bs	Fri May 29 16:46:00 2015 -0700
    32.2 +++ b/css-logical-props/Overview.bs	Fri May 29 16:46:19 2015 -0700
    32.3 @@ -4,6 +4,7 @@
    32.4  Shortname: css-logical-props
    32.5  Level: 1
    32.6  Status: ED
    32.7 +Work Status: Exploring
    32.8  Group: csswg
    32.9  ED: http://dev.w3.org/csswg/css-logical-props/
   32.10  Editor: Rossen Atanassov, Microsoft, [email protected]

    33.1 --- a/css-multicol-2/Overview.bs	Fri May 29 16:46:00 2015 -0700
    33.2 +++ b/css-multicol-2/Overview.bs	Fri May 29 16:46:19 2015 -0700
    33.3 @@ -4,6 +4,7 @@
    33.4  Shortname: css-multicol
    33.5  Level: 2
    33.6  Status: ED
    33.7 +Work Status: Exploring
    33.8  ED: http://dev.w3.org/csswg/css-multicol-2/
    33.9  Editor: Florian Rivoal, Invited Expert, [email protected], http://florian.rivoal.net/
   33.10  Abstract: This specification describes multi-column layouts in CSS, a style sheet language for the web. Using functionality described in the specification, content can be flowed into multiple columns with a gap and a rule between them.

    34.1 --- a/css-multicol/Overview.bs	Fri May 29 16:46:00 2015 -0700
    34.2 +++ b/css-multicol/Overview.bs	Fri May 29 16:46:19 2015 -0700
    34.3 @@ -4,6 +4,7 @@
    34.4  Shortname: css-multicol
    34.5  Level: 1
    34.6  Status: ED
    34.7 +Work Status: Testing
    34.8  ED: http://dev.w3.org/csswg/css-multicol/
    34.9  TR: http://www.w3.org/TR/css3-multicol/
   34.10  Previous Version: http://www.w3.org/TR/2011/CR-css3-multicol-20110412/

    35.1 --- a/css-namespaces/Overview.bs	Fri May 29 16:46:00 2015 -0700
    35.2 +++ b/css-namespaces/Overview.bs	Fri May 29 16:46:19 2015 -0700
    35.3 @@ -4,6 +4,7 @@
    35.4  Shortname: css-namespace
    35.5  Level: 3
    35.6  Status: ED
    35.7 +Work Status: Completed
    35.8  ED: http://dev.w3.org/csswg/css-namespaces/
    35.9  TR: http://www.w3.org/TR/css3-namespace/
   35.10  Test Suite: http://test.csswg.org/suites/css3-namespace/20090210/

    36.1 --- a/css-overflow/Overview.bs	Fri May 29 16:46:00 2015 -0700
    36.2 +++ b/css-overflow/Overview.bs	Fri May 29 16:46:19 2015 -0700
    36.3 @@ -1,6 +1,7 @@
    36.4  <h1>CSS Overflow Module Level 3</h1>
    36.5  <pre class="metadata">
    36.6  Status: ED
    36.7 +Work Status: Exploring
    36.8  ED: http://dev.w3.org/csswg/css-overflow/
    36.9  Shortname: css-overflow
   36.10  Group: csswg
   36.11 @@ -449,7 +450,7 @@
   36.12  		which still allows programmatic scrolling,
   36.13  		''overflow: clip'' forbids scrolling entirely,
   36.14  		through any mechanism.
   36.15 -		
   36.16 +
   36.17  		Issue: Mozilla implements -moz-hidden-unscrollable,
   36.18  		which is similar to ''clip'',
   36.19  		except that it does not cause the element to establish a BFC.
   36.20 @@ -463,14 +464,14 @@
   36.21  		This avoids any problem with scrollbars appearing
   36.22  		and disappearing in a dynamic environment.
   36.23  		When this value is specified and the target medium is ''print'',
   36.24 -		overflowing content may be printed. 
   36.25 +		overflowing content may be printed.
   36.26  		<dt><dfn>auto</dfn>
   36.27  		<dd>The behavior of the ''overflow/auto'' value is user agent-dependent,
   36.28 -		but should cause a scrolling mechanism to be provided for overflowing boxes. 
   36.29 +		but should cause a scrolling mechanism to be provided for overflowing boxes.
   36.30  	</dl>
   36.31  
   36.32  	Even if 'overflow' is set to ''overflow/visible'',
   36.33 -	content may be clipped to a UA's document window by the native operating environment. 
   36.34 +	content may be clipped to a UA's document window by the native operating environment.
   36.35  
   36.36  	If the computed value of 'overflow' is not ''overflow/visible'',
   36.37  	the element creates a block formatting context.
   36.38 @@ -490,7 +491,7 @@
   36.39  	and the outer padding edge.
   36.40  	Any space taken up by the scrollbars should be
   36.41  	taken out of (subtracted from the dimensions of)
   36.42 -	the containing block formed by the element with the scrollbars. 
   36.43 +	the containing block formed by the element with the scrollbars.
   36.44  
   36.45  	Issue: import examples from [[CSS3-BOX]].
   36.46  

    37.1 --- a/css-page-floats/Overview.bs	Fri May 29 16:46:00 2015 -0700
    37.2 +++ b/css-page-floats/Overview.bs	Fri May 29 16:46:19 2015 -0700
    37.3 @@ -5,6 +5,7 @@
    37.4  Level: 3
    37.5  Group: csswg
    37.6  Status: ED
    37.7 +Work Status: Exploring
    37.8  ED: http://dev.w3.org/csswg/css-page-floats/
    37.9  Previous Version: https://hg.csswg.org/drafts/raw-file/108d7e3ff204/css-page-floats/Overview.html
   37.10  Editor: Johannes Wilm, Vivliostyle, [email protected]

    38.1 --- a/css-page/Overview.bs	Fri May 29 16:46:00 2015 -0700
    38.2 +++ b/css-page/Overview.bs	Fri May 29 16:46:19 2015 -0700
    38.3 @@ -4,6 +4,7 @@
    38.4  Shortname: css-page
    38.5  Level: 3
    38.6  Status: ED
    38.7 +Work Status: Revising
    38.8  Group: csswg
    38.9  ED: http://dev.w3.org/csswg/css-page/
   38.10  TR: http://www.w3.org/TR/css3-page/

    39.1 --- a/css-position/Overview.bs	Fri May 29 16:46:00 2015 -0700
    39.2 +++ b/css-position/Overview.bs	Fri May 29 16:46:19 2015 -0700
    39.3 @@ -2,6 +2,7 @@
    39.4  
    39.5  <pre class='metadata'>
    39.6  Status: ED
    39.7 +Work Status: Exploring
    39.8  Shortname: css-position
    39.9  Level: 1
   39.10  Group: csswg

    40.1 --- a/css-pseudo/Overview.bs	Fri May 29 16:46:00 2015 -0700
    40.2 +++ b/css-pseudo/Overview.bs	Fri May 29 16:46:19 2015 -0700
    40.3 @@ -4,6 +4,7 @@
    40.4  Shortname: css-pseudo
    40.5  Level: 4
    40.6  Status: FPWD
    40.7 +Work Status: Exploring
    40.8  Date: 2015-01-15
    40.9  Group: csswg
   40.10  ED: http://dev.w3.org/csswg/css-pseudo-4/

    41.1 --- a/css-regions/Overview.src.html	Fri May 29 16:46:00 2015 -0700
    41.2 +++ b/css-regions/Overview.src.html	Fri May 29 16:46:19 2015 -0700
    41.3 @@ -2,6 +2,7 @@
    41.4  
    41.5  <pre class='metadata'>
    41.6  Status: ED
    41.7 +Work Status: Exploring
    41.8  Shortname: css-regions
    41.9  Level: 1
   41.10  Group: csswg
   41.11 @@ -22,9 +23,9 @@
   41.12  
   41.13  <em>This section is non-normative.</em>
   41.14  
   41.15 -	The core concept behind CSS Regions 
   41.16 -	is the ability to say, 
   41.17 -	"Display <em>this</em> content (a <a>named flow</a>) 
   41.18 +	The core concept behind CSS Regions
   41.19 +	is the ability to say,
   41.20 +	"Display <em>this</em> content (a <a>named flow</a>)
   41.21  	over <em>there</em> (a <a>region chain</a>)."
   41.22  	The simplest example is:
   41.23  
   41.24 @@ -40,29 +41,29 @@
   41.25  		</code></pre>
   41.26  	</div>
   41.27  
   41.28 -	These two declarations will take 
   41.29 -	the element that matches <code>#this</code>, 
   41.30 -	put it into a flow named "my-flow", 
   41.31 -	and display the contents of "my-flow" 
   41.32 -	in the box from the element that matches <code>#there</code>. 
   41.33 -	This example has a single content source for the <a>named flow</a>, 
   41.34 -	and a single box for the <a>region chain</a>. 
   41.35 -	<a>Named flows</a> can also have multiple sources 
   41.36 +	These two declarations will take
   41.37 +	the element that matches <code>#this</code>,
   41.38 +	put it into a flow named "my-flow",
   41.39 +	and display the contents of "my-flow"
   41.40 +	in the box from the element that matches <code>#there</code>.
   41.41 +	This example has a single content source for the <a>named flow</a>,
   41.42 +	and a single box for the <a>region chain</a>.
   41.43 +	<a>Named flows</a> can also have multiple sources
   41.44  	and use multiple boxes for the <a>region chain</a>.
   41.45  
   41.46 -	The <a>named flow</a> mechanism can be used 
   41.47 -	in several different ways - 
   41.48 -	some of which are 
   41.49 -	custom overflow handling, 
   41.50 -	aggregating content, 
   41.51 -	linked display boxes, 
   41.52 -	magazine-style layout, 
   41.53 +	The <a>named flow</a> mechanism can be used
   41.54 +	in several different ways -
   41.55 +	some of which are
   41.56 +	custom overflow handling,
   41.57 +	aggregating content,
   41.58 +	linked display boxes,
   41.59 +	magazine-style layout,
   41.60  	and flowing content through areas in a paginated view.
   41.61  
   41.62  	<div class="example">
   41.63 -		Linked display boxes can be created 
   41.64 -		to display article content above and below 
   41.65 -		other content on a page. 
   41.66 +		Linked display boxes can be created
   41.67 +		to display article content above and below
   41.68 +		other content on a page.
   41.69  		Given markup like this:
   41.70  
   41.71  		<pre><code class="html">
   41.72 @@ -70,17 +71,17 @@
   41.73  			&lt;aside&gt; ad or image content &lt;/aside&gt;
   41.74  		</code></pre>
   41.75  
   41.76 -		The &lt;aside&gt; content will be displayed 
   41.77 -		below all of the article content. 
   41.78 -		On a large screen the page might display without scrolling, 
   41.79 -		but on a small screen the &lt;aside&gt; content 
   41.80 -		might not be visible until the view scrolls. 
   41.81 -		If it's important to show at least some 
   41.82 -		of the &lt;aside&gt; content in the initial view, 
   41.83 -		CSS Regions can fragment the article content across two boxes - 
   41.84 +		The &lt;aside&gt; content will be displayed
   41.85 +		below all of the article content.
   41.86 +		On a large screen the page might display without scrolling,
   41.87 +		but on a small screen the &lt;aside&gt; content
   41.88 +		might not be visible until the view scrolls.
   41.89 +		If it's important to show at least some
   41.90 +		of the &lt;aside&gt; content in the initial view,
   41.91 +		CSS Regions can fragment the article content across two boxes -
   41.92  		one above the &lt;aside&gt; and one below.
   41.93  
   41.94 -		In this example (for simplicity's sake) 
   41.95 +		In this example (for simplicity's sake)
   41.96  		we create the boxes with additional elements:
   41.97  
   41.98  		<pre><code class="html">
   41.99 @@ -103,10 +104,10 @@
  41.100  			}
  41.101  		</code></pre>
  41.102  
  41.103 -		So the top box in the <a>region chain</a> 
  41.104 -		is limited to 80% of the viewport height. 
  41.105 -		If the article content doesn't fit in that box, 
  41.106 -		the article will continue 
  41.107 +		So the top box in the <a>region chain</a>
  41.108 +		is limited to 80% of the viewport height.
  41.109 +		If the article content doesn't fit in that box,
  41.110 +		the article will continue
  41.111  		in the second box after the &lt;aside&gt; content.
  41.112  
  41.113  		<figure style="float:left; margin:1em;">
  41.114 @@ -125,13 +126,13 @@
  41.115  			</figcaption>
  41.116  		</figure>
  41.117  
  41.118 -		<p style="clear:left;">In the images above, 
  41.119 -			the gray area represents  
  41.120 -			the content below the screen edge 
  41.121 +		<p style="clear:left;">In the images above,
  41.122 +			the gray area represents
  41.123 +			the content below the screen edge
  41.124  			in the initial view.
  41.125  
  41.126 -		This example links just two boxes together, 
  41.127 -		but more boxes could be added to the <a>region chain</a> 
  41.128 +		This example links just two boxes together,
  41.129 +		but more boxes could be added to the <a>region chain</a>
  41.130  		to regularly interleave other content with the article.
  41.131  	</div>
  41.132  
  41.133 @@ -214,12 +215,12 @@
  41.134  
  41.135  		<strong><a>CSS Regions</a> are independent from layout</strong>
  41.136  
  41.137 -		Any of the CSS layout facilities can be used 
  41.138 -		to create, position and size boxes that can become <a>CSS Regions</a>. 
  41.139 +		Any of the CSS layout facilities can be used
  41.140 +		to create, position and size boxes that can become <a>CSS Regions</a>.
  41.141  
  41.142 -		The CSS Regions module does not 
  41.143 -		define a layout mechanism 
  41.144 -		and is meant to integrate 
  41.145 +		The CSS Regions module does not
  41.146 +		define a layout mechanism
  41.147 +		and is meant to integrate
  41.148  		with existing and future CSS layout facilities.
  41.149  	</div>
  41.150  
  41.151 @@ -227,24 +228,24 @@
  41.152  
  41.153  		<strong><a>CSS Regions</a> do not have to be elements</strong>
  41.154  
  41.155 -		The CSS Regions module is independent 
  41.156 -		of the layout of boxes and 
  41.157 +		The CSS Regions module is independent
  41.158 +		of the layout of boxes and
  41.159  		the mechanisms used to create them.
  41.160  
  41.161  		For simplicity,
  41.162  		our examples tend to
  41.163 -		use elements to define the boxes. 
  41.164 -		Any other mechanism available 
  41.165 -		in markup or style 
  41.166 -		to create stylable boxes could be used instead, 
  41.167 -		such as pseudo-elements 
  41.168 -		or the @slot rule proposed 
  41.169 +		use elements to define the boxes.
  41.170 +		Any other mechanism available
  41.171 +		in markup or style
  41.172 +		to create stylable boxes could be used instead,
  41.173 +		such as pseudo-elements
  41.174 +		or the @slot rule proposed
  41.175  		by the CSS Page Template Module [[CSS3-PAGE-TEMPLATE]].
  41.176  
  41.177  
  41.178 -		The only requirement 
  41.179 +		The only requirement
  41.180  		for box to become a <a>CSS Region</a>
  41.181 -		is that the 'flow-from' property applies to the box. 
  41.182 +		is that the 'flow-from' property applies to the box.
  41.183  	</div>
  41.184  
  41.185  <h2 id="css-regions-concepts">
  41.186 @@ -253,84 +254,84 @@
  41.187  <h3 id="regions">
  41.188  Regions</h3>
  41.189  
  41.190 -	A <dfn>CSS Region</dfn> 
  41.191 -	is a block container 
  41.192 -	that has an associated 
  41.193 -	<em><a>named flow</a></em> 
  41.194 +	A <dfn>CSS Region</dfn>
  41.195 +	is a block container
  41.196 +	that has an associated
  41.197 +	<em><a>named flow</a></em>
  41.198  	(see the 'flow-from' property).
  41.199  
  41.200  <h3 id="region-chain-section">
  41.201  Region chain</h3>
  41.202  
  41.203 -	A <dfn>region chain</dfn> 
  41.204 -	is the sequence of regions 
  41.205 -	that are associated with 
  41.206 -	a <a>named flow</a>. 
  41.207 -	<a>CSS Regions</a> in a 
  41.208 -	<a>region chain</a> receive content from the 
  41.209 -	<a>named flow</a> following their order in the chain. 
  41.210 -	<a>CSS Regions</a> are organized 
  41.211 -	into a <a>region chain</a> 
  41.212 +	A <dfn>region chain</dfn>
  41.213 +	is the sequence of regions
  41.214 +	that are associated with
  41.215 +	a <a>named flow</a>.
  41.216 +	<a>CSS Regions</a> in a
  41.217 +	<a>region chain</a> receive content from the
  41.218 +	<a>named flow</a> following their order in the chain.
  41.219 +	<a>CSS Regions</a> are organized
  41.220 +	into a <a>region chain</a>
  41.221  	according to the document order.
  41.222  
  41.223  <h3 id="named-flow-section">
  41.224  Named flows</h3>
  41.225  
  41.226 -	A <dfn>named flow</dfn> is the ordered sequence of content	
  41.227 -	associated with a flow with a given identifier. 
  41.228 +	A <dfn>named flow</dfn> is the ordered sequence of content
  41.229 +	associated with a flow with a given identifier.
  41.230  	Contents in a <a>named flow</a> are ordered
  41.231  	according to the document order.
  41.232  
  41.233 -	Content is placed into a <a>named flow</a> 
  41.234 -	with the 'flow-into' property. 
  41.235 -	The content in a <a>named flow</a> is laid out 
  41.236 -	in the <a>region chain</a> 
  41.237 -	that is associated with this <a>named flow</a> 
  41.238 +	Content is placed into a <a>named flow</a>
  41.239 +	with the 'flow-into' property.
  41.240 +	The content in a <a>named flow</a> is laid out
  41.241 +	in the <a>region chain</a>
  41.242 +	that is associated with this <a>named flow</a>
  41.243  	using the 'flow-from' property.
  41.244  
  41.245 -	Content from a <a>named flow</a> 
  41.246 -	is broken up between regions 
  41.247 +	Content from a <a>named flow</a>
  41.248 +	is broken up between regions
  41.249  	according to the regions flow breaking rules.
  41.250  
  41.251 -	A <a>named flow</a> is created when 
  41.252 -	some content is moved 
  41.253 -	into the flow with the given identifier 
  41.254 -	or when at least one <a>CSS Region</a> 
  41.255 +	A <a>named flow</a> is created when
  41.256 +	some content is moved
  41.257 +	into the flow with the given identifier
  41.258 +	or when at least one <a>CSS Region</a>
  41.259  	requests content from that flow.
  41.260  
  41.261  <h3 id="regions-flow-breaking-rules">
  41.262  Regions flow breaking rules</h3>
  41.263  
  41.264 -	Breaking a <a>named flow</a> across a <a>region chain</a> 
  41.265 -	is similar to breaking a document's content across pages 
  41.266 -	(see [[CSS3PAGE]]) 
  41.267 -	or a multi-column element's content across column boxes 
  41.268 -	(see [[CSS3COL]]). 
  41.269 -	One difference is that page boxes are generated 
  41.270 -	based on the available content 
  41.271 -	whereas a <a>region chain</a> is a set of recipient boxes 
  41.272 -	for the <a>named flow</a> content 
  41.273 -	whose dynamic generation is not in the scope 
  41.274 +	Breaking a <a>named flow</a> across a <a>region chain</a>
  41.275 +	is similar to breaking a document's content across pages
  41.276 +	(see [[CSS3PAGE]])
  41.277 +	or a multi-column element's content across column boxes
  41.278 +	(see [[CSS3COL]]).
  41.279 +	One difference is that page boxes are generated
  41.280 +	based on the available content
  41.281 +	whereas a <a>region chain</a> is a set of recipient boxes
  41.282 +	for the <a>named flow</a> content
  41.283 +	whose dynamic generation is not in the scope
  41.284  	of this specification.
  41.285  
  41.286 -	Each <a>CSS Region</a> in turn 
  41.287 -	consumes content from its associated <a>named flow</a>. 
  41.288 -	The <a>named flow</a> content is positioned 
  41.289 -	in the current region 
  41.290 -	until a natural or forced region break occurs, 
  41.291 -	at which point the next region 
  41.292 -	in the <a>region chain</a> 
  41.293 -	becomes the current region. 
  41.294 -	If there are no more <a>CSS Regions</a> 
  41.295 -	in the <a>region chain</a> 
  41.296 -	and there is still content in the flow, 
  41.297 -	the positioning of the remaining content 
  41.298 -	is controlled by the 'region-fragment' property 
  41.299 +	Each <a>CSS Region</a> in turn
  41.300 +	consumes content from its associated <a>named flow</a>.
  41.301 +	The <a>named flow</a> content is positioned
  41.302 +	in the current region
  41.303 +	until a natural or forced region break occurs,
  41.304 +	at which point the next region
  41.305 +	in the <a>region chain</a>
  41.306 +	becomes the current region.
  41.307 +	If there are no more <a>CSS Regions</a>
  41.308 +	in the <a>region chain</a>
  41.309 +	and there is still content in the flow,
  41.310 +	the positioning of the remaining content
  41.311 +	is controlled by the 'region-fragment' property
  41.312  	on the last <a>CSS Region</a> in the chain.
  41.313  
  41.314 -	The CSS regions module follows 
  41.315 -	the fragmentation rules defined 
  41.316 -	in the CSS Fragmentation Module Level 3 
  41.317 +	The CSS regions module follows
  41.318 +	the fragmentation rules defined
  41.319 +	in the CSS Fragmentation Module Level 3
  41.320  	(see [[!CSS3-BREAK]]).
  41.321  
  41.322  
  41.323 @@ -349,11 +350,11 @@
  41.324  	</div>
  41.325  	</div>
  41.326  
  41.327 -	The ‘flow-into’ property can place an element 
  41.328 -	or its contents 
  41.329 -	into a <a>named flow</a>. 
  41.330 -	Content that belongs to the same flow 
  41.331 -	is laid out in the <a>region chain</a> 
  41.332 +	The ‘flow-into’ property can place an element
  41.333 +	or its contents
  41.334 +	into a <a>named flow</a>.
  41.335 +	Content that belongs to the same flow
  41.336 +	is laid out in the <a>region chain</a>
  41.337  	associated with that flow.
  41.338  
  41.339  	<pre class='propdef'>
  41.340 @@ -370,146 +371,146 @@
  41.341  		<dt>none</dt>
  41.342  
  41.343  		<dd>
  41.344 -			The element is not moved 
  41.345 -			to a <a>named flow</a> 
  41.346 +			The element is not moved
  41.347 +			to a <a>named flow</a>
  41.348  			and normal CSS processing takes place.
  41.349  		</dd>
  41.350  
  41.351  		<dt><a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a></dt>
  41.352  
  41.353  		<dd>
  41.354 -			If the keyword <dfn>element</dfn> is present 
  41.355 -			or neither keyword is present, 
  41.356 -			then the element is taken out 
  41.357 +			If the keyword <dfn>element</dfn> is present
  41.358 +			or neither keyword is present,
  41.359 +			then the element is taken out
  41.360  			of its parent's flow
  41.361 -			and placed into the flow 
  41.362 -			with the name '<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>'. 
  41.363 -			If the keyword <dfn>content</dfn> is present, 
  41.364 -			then only the element's contents 
  41.365 -			are placed into the named flow. 
  41.366 -			The element or content is said to have 
  41.367 -			a <dfn id="specified-flow">specified flow</dfn>. 
  41.368 +			and placed into the flow
  41.369 +			with the name '<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>'.
  41.370 +			If the keyword <dfn>content</dfn> is present,
  41.371 +			then only the element's contents
  41.372 +			are placed into the named flow.
  41.373 +			The element or content is said to have
  41.374 +			a <dfn id="specified-flow">specified flow</dfn>.
  41.375  			The values ''none'', ''inherit'', ''default'', ''auto'' and ''initial''
  41.376  			are invalid flow names.
  41.377  		</dd>
  41.378  	</dl>
  41.379  
  41.380 -	The 'flow-into' property affects 
  41.381 -	the visual formatting of elements or contents 
  41.382 -	placed into a <a>named flow</a> 
  41.383 -	and of the <a>region chain</a> laying out content 
  41.384 -	from a <a>named flow</a>. 
  41.385 -	The 'flow-into' property does not affect 
  41.386 -	the CSS cascade and inheritance 
  41.387 -	for the elements on which it is specified. 
  41.388 -	The 'flow-into' property does not affect the 
  41.389 -	<a href="http://www.w3.org/TR/2012/WD-dom-20120405/#introduction-to-the-dom">DOM</a> 
  41.390 -	[[!DOM]] position of an element or its contents. 
  41.391 -	The 'flow-into' property does not affect ordering 
  41.392 -	in non-visual media 
  41.393 -	(such as <a href="http://www.w3.org/TR/css3-speech/">speech</a>). 
  41.394 -	Likewise, 'flow-into' does not affect 
  41.395 -	the default traversal order 
  41.396 -	of sequential navigation modes 
  41.397 -	(such as cycling through links, 
  41.398 -	see e.g. 'nav-index' [[CSS3UI]] 
  41.399 +	The 'flow-into' property affects
  41.400 +	the visual formatting of elements or contents
  41.401 +	placed into a <a>named flow</a>
  41.402 +	and of the <a>region chain</a> laying out content
  41.403 +	from a <a>named flow</a>.
  41.404 +	The 'flow-into' property does not affect
  41.405 +	the CSS cascade and inheritance
  41.406 +	for the elements on which it is specified.
  41.407 +	The 'flow-into' property does not affect the
  41.408 +	<a href="http://www.w3.org/TR/2012/WD-dom-20120405/#introduction-to-the-dom">DOM</a>
  41.409 +	[[!DOM]] position of an element or its contents.
  41.410 +	The 'flow-into' property does not affect ordering
  41.411 +	in non-visual media
  41.412 +	(such as <a href="http://www.w3.org/TR/css3-speech/">speech</a>).
  41.413 +	Likewise, 'flow-into' does not affect
  41.414 +	the default traversal order
  41.415 +	of sequential navigation modes
  41.416 +	(such as cycling through links,
  41.417 +	see e.g. 'nav-index' [[CSS3UI]]
  41.418  	or <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html#sequential-focus-navigation-and-the-tabindex-attribute"><code>tabindex</code></a> [[HTML40]]).
  41.419  
  41.420 -	A <a>named flow</a> needs to be associated 
  41.421 -	with a <a>region chain</a> 
  41.422 -	(one or more <a>CSS Regions</a>) 
  41.423 -	for its content to be visually formatted. 
  41.424 -	If no <a>region chain</a> is associated 
  41.425 -	with a given <a>named flow</a>, 
  41.426 -	the content in the <a>named flow</a> 
  41.427 -	is not rendered: 
  41.428 -	it does not generate boxes 
  41.429 +	A <a>named flow</a> needs to be associated
  41.430 +	with a <a>region chain</a>
  41.431 +	(one or more <a>CSS Regions</a>)
  41.432 +	for its content to be visually formatted.
  41.433 +	If no <a>region chain</a> is associated
  41.434 +	with a given <a>named flow</a>,
  41.435 +	the content in the <a>named flow</a>
  41.436 +	is not rendered:
  41.437 +	it does not generate boxes
  41.438  	and is not displayed.
  41.439  
  41.440 -	The children of an element or content 
  41.441 -	with a specified flow 
  41.442 -	may themselves have a specified flow, 
  41.443 -	in which case they become 
  41.444 -	the next sibling of the latest element 
  41.445 -	or content collected in that flow. 
  41.446 -	In some cases, 
  41.447 -	the child can become the next sibling 
  41.448 +	The children of an element or content
  41.449 +	with a specified flow
  41.450 +	may themselves have a specified flow,
  41.451 +	in which case they become
  41.452 +	the next sibling of the latest element
  41.453 +	or content collected in that flow.
  41.454 +	In some cases,
  41.455 +	the child can become the next sibling
  41.456  	for one of its ancestors in the same flow.
  41.457  
  41.458 -	Content in a <a>named flow</a> 
  41.459 -	is sequenced in document order. 
  41.460 -	The visual formatting model 
  41.461 -	uses the relationships between content 
  41.462 -	in the named flow as input, 
  41.463 -	rather than the contents&rsquo; position 
  41.464 +	Content in a <a>named flow</a>
  41.465 +	is sequenced in document order.
  41.466 +	The visual formatting model
  41.467 +	uses the relationships between content
  41.468 +	in the named flow as input,
  41.469 +	rather than the contents&rsquo; position
  41.470  	in the DOM.
  41.471  
  41.472 -	Each <a>CSS Region</a> in a <a>region chain</a> 
  41.473 -	establishes a containing block for absolutely positioned 
  41.474 +	Each <a>CSS Region</a> in a <a>region chain</a>
  41.475 +	establishes a containing block for absolutely positioned
  41.476  	elements in the <a>named flow</a> (see [[!CSS21]]).
  41.477  	That first <a>CSS Region</a> in a <a>region chain</a>
  41.478  	establishes the initial containing block for such absolutely
  41.479 -	positioned elements. 
  41.480 -	<span>Regions</span> don't establish a containing block for 
  41.481 +	positioned elements.
  41.482 +	<span>Regions</span> don't establish a containing block for
  41.483  	fixed positioned elements in the <a>named flow</a>.
  41.484 -	Such fixed positioned elements are still positioned relative 
  41.485 -	to the viewport or the page area even if they have been 
  41.486 +	Such fixed positioned elements are still positioned relative
  41.487 +	to the viewport or the page area even if they have been
  41.488  	redirected into a named flow
  41.489  
  41.490 -	The first region defines the principal 
  41.491 -	<a href="http://www.w3.org/TR/css3-writing-modes/#writing-mode">writing mode</a> 
  41.492 -	for the entire flow. 
  41.493 -	The writing mode 
  41.494 +	The first region defines the principal
  41.495 +	<a href="http://www.w3.org/TR/css3-writing-modes/#writing-mode">writing mode</a>
  41.496 +	for the entire flow.
  41.497 +	The writing mode
  41.498  	on subsequent regions is ignored.
  41.499  
  41.500  	<div class="note"><span class="note-prefix">Note </span>
  41.501  
  41.502 -		The 'flow-into' property moves an element into the flow 
  41.503 +		The 'flow-into' property moves an element into the flow
  41.504  		and the interplay with selectors should be considered carefully.
  41.505  
  41.506  		For example,
  41.507  
  41.508  		<pre>table {flow-into: table-content}</pre>
  41.509  
  41.510 -		will move all tables in the "table-content" 
  41.511 -		<a>named flow</a>. 
  41.512 +		will move all tables in the "table-content"
  41.513 +		<a>named flow</a>.
  41.514  		However, the
  41.515  
  41.516  		<pre>table &gt; * {flow-into: table-content} ...</pre>
  41.517  
  41.518 -		selector will move all immediate children 
  41.519 -		of all table elements 
  41.520 -		into the "table-content" <a>named flow</a> 
  41.521 -		(which may be useful as it will usually result, 
  41.522 -		if the immediate children are rows, 
  41.523 -		in merging rows of multiple tables), 
  41.524 +		selector will move all immediate children
  41.525 +		of all table elements
  41.526 +		into the "table-content" <a>named flow</a>
  41.527 +		(which may be useful as it will usually result,
  41.528 +		if the immediate children are rows,
  41.529 +		in merging rows of multiple tables),
  41.530  		but the
  41.531  
  41.532  		<pre>table * {flow-into: table-content}</pre>
  41.533  
  41.534 -		selector will move all descendants 
  41.535 -		of table elements into the "table-content" <a>named flow</a>, 
  41.536 -		transforming the element tree 
  41.537 -		into a flat list in order of opening tags 
  41.538 -		(which is probably not intentional). 
  41.539 -		This will make all the descendants 
  41.540 -		of table elements siblings 
  41.541 -		in the <a>named flow</a>. 
  41.542 -		Having the descendants become siblings 
  41.543 -		in the <a>named flow</a> 
  41.544 -		results in a different processing 
  41.545 -		(see <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/tables.html#anonymous-boxes">CSS 2.1's anonymous table objects</a>). 
  41.546 -		This note illustrates how authors must exercise caution 
  41.547 -		when choosing a particular selector 
  41.548 -		for setting the 'flow-into' property 
  41.549 +		selector will move all descendants
  41.550 +		of table elements into the "table-content" <a>named flow</a>,
  41.551 +		transforming the element tree
  41.552 +		into a flat list in order of opening tags
  41.553 +		(which is probably not intentional).
  41.554 +		This will make all the descendants
  41.555 +		of table elements siblings
  41.556 +		in the <a>named flow</a>.
  41.557 +		Having the descendants become siblings
  41.558 +		in the <a>named flow</a>
  41.559 +		results in a different processing
  41.560 +		(see <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/tables.html#anonymous-boxes">CSS 2.1's anonymous table objects</a>).
  41.561 +		This note illustrates how authors must exercise caution
  41.562 +		when choosing a particular selector
  41.563 +		for setting the 'flow-into' property
  41.564  		to avoid unintended results.
  41.565  	</div>
  41.566  
  41.567  	<div class="note"><span class="note-prefix">Note </span>
  41.568  
  41.569 -		Another consequence of moving elements 
  41.570 -		into <a>named flows</a> is that surrounding whitespace 
  41.571 -		is not moved into the named flow. 
  41.572 +		Another consequence of moving elements
  41.573 +		into <a>named flows</a> is that surrounding whitespace
  41.574 +		is not moved into the named flow.
  41.575  		If you have code like this:
  41.576  
  41.577  		<pre>
  41.578 @@ -518,28 +519,28 @@
  41.579  		&lt;span&gt;two&lt;/span&gt;
  41.580  		</pre>
  41.581  
  41.582 -		Then the "span-content" named flow contents 
  41.583 -		will contain this: 
  41.584 +		Then the "span-content" named flow contents
  41.585 +		will contain this:
  41.586  
  41.587  		<pre>
  41.588  		&lt;span&gt;one&lt;/span&gt;&lt;span&gt;two&lt;/span&gt;
  41.589  		</pre>
  41.590  
  41.591 -		Which will change the display 
  41.592 +		Which will change the display
  41.593  		from "one two" to "onetwo".
  41.594 -		If whitespace is significant, 
  41.595 -		then moving the parent 
  41.596 -		that contains the whitespace 
  41.597 -		to the named flow 
  41.598 +		If whitespace is significant,
  41.599 +		then moving the parent
  41.600 +		that contains the whitespace
  41.601 +		to the named flow
  41.602  		is required.
  41.603  	</div>
  41.604  
  41.605  <h3 id="flow-from">
  41.606  The 'flow-from' property</h3>
  41.607  
  41.608 -	The 'flow-from' property makes 
  41.609 -	a block container a region 
  41.610 -	and associates it with 
  41.611 +	The 'flow-from' property makes
  41.612 +	a block container a region
  41.613 +	and associates it with
  41.614  	a <a>named flow</a>.
  41.615  
  41.616  	<pre class='propdef'>
  41.617 @@ -562,57 +563,57 @@
  41.618  		<dt><strong><a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a></strong></dt>
  41.619  
  41.620  		<dd>
  41.621 -			The block container becomes a <a>CSS Region</a> 
  41.622 -			(except as detailed in the text below), 
  41.623 -			and is ordered in a <a>region chain</a> 
  41.624 -			according to its document order. 
  41.625 -			The content from the flow 
  41.626 +			The block container becomes a <a>CSS Region</a>
  41.627 +			(except as detailed in the text below),
  41.628 +			and is ordered in a <a>region chain</a>
  41.629 +			according to its document order.
  41.630 +			The content from the flow
  41.631  			with the <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>
  41.632 -			name will be <a href="#region-flow-break">broken 
  41.633 -			into fragments</a> and visually formatted in the 
  41.634 -			<a href="http://www.w3.org/TR/CSS21/visuren.html#principal-box">principal boxes</a> 
  41.635 -			of the <span>regions</span> 
  41.636 -			in the <a>region chain</a>. 
  41.637 +			name will be <a href="#region-flow-break">broken
  41.638 +			into fragments</a> and visually formatted in the
  41.639 +			<a href="http://www.w3.org/TR/CSS21/visuren.html#principal-box">principal boxes</a>
  41.640 +			of the <span>regions</span>
  41.641 +			in the <a>region chain</a>.
  41.642  			<br/>
  41.643 -			If there is no flow with name 
  41.644 -			<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>, 
  41.645 -			then the block container does not 
  41.646 -			format any content visually. 
  41.647 +			If there is no flow with name
  41.648 +			<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>,
  41.649 +			then the block container does not
  41.650 +			format any content visually.
  41.651  		</dd>
  41.652  	</dl>
  41.653  
  41.654 -	If the 'content' property computes 
  41.655 -	to something else than ''normal'' 
  41.656 -	(or ''none'' for a pseudo-element), 
  41.657 -	the block container does not become 
  41.658 -	a <a>CSS Region</a>. 
  41.659 -	If the 'display' property 
  41.660 -	of the block container 
  41.661 -	or one of its ancestors 
  41.662 -	computes to ''none'', 
  41.663 -	the block container does not become 
  41.664 +	If the 'content' property computes
  41.665 +	to something else than ''normal''
  41.666 +	(or ''none'' for a pseudo-element),
  41.667 +	the block container does not become
  41.668 +	a <a>CSS Region</a>.
  41.669 +	If the 'display' property
  41.670 +	of the block container
  41.671 +	or one of its ancestors
  41.672 +	computes to ''none'',
  41.673 +	the block container does not become
  41.674  	a <a>CSS Region</a>.
  41.675  
  41.676 -	A <a>CSS Region</a>&rsquo;s document children 
  41.677 -	are not visually formatted 
  41.678 -	unless they are directed 
  41.679 -	to a <a>named flow</a> 
  41.680 +	A <a>CSS Region</a>&rsquo;s document children
  41.681 +	are not visually formatted
  41.682 +	unless they are directed
  41.683 +	to a <a>named flow</a>
  41.684  	with an associated <a>region chain</a>.
  41.685  
  41.686 -	Block container pseudo-elements where 
  41.687 -	the value of 'flow-from' computes to an 
  41.688 -	<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a> 
  41.689 -	and the value of 'content' computes to ''none'' 
  41.690 -	are generated as <a>CSS Regions</a>, 
  41.691 -	which is an update to the behavior 
  41.692 +	Block container pseudo-elements where
  41.693 +	the value of 'flow-from' computes to an
  41.694 +	<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>
  41.695 +	and the value of 'content' computes to ''none''
  41.696 +	are generated as <a>CSS Regions</a>,
  41.697 +	which is an update to the behavior
  41.698  	described in [[!CSS21]].
  41.699  
  41.700  	<div class="note"><span class="note-prefix">Note </span>
  41.701  
  41.702 -		A block container becomes a <a>CSS Region</a> 
  41.703 -		when its 'flow-from' property is set 
  41.704 -		to a valid <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a> value, 
  41.705 -		even if there is no content contributing 
  41.706 +		A block container becomes a <a>CSS Region</a>
  41.707 +		when its 'flow-from' property is set
  41.708 +		to a valid <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a> value,
  41.709 +		even if there is no content contributing
  41.710  		to the referenced flow.
  41.711  		For example:
  41.712  
  41.713 @@ -632,15 +633,15 @@
  41.714  		&lt;/html&gt;
  41.715  		</pre>
  41.716  
  41.717 -		There is no element matching 
  41.718 -		the <code>.article</code> selector 
  41.719 -		and therefore no content 
  41.720 -		in the <code>thread</code> flow. 
  41.721 -		However, the block container matching 
  41.722 -		the <code>.region</code> selector 
  41.723 -		is still associated with 
  41.724 -		that empty <a>named flow</a> 
  41.725 -		and, consequently, 
  41.726 +		There is no element matching
  41.727 +		the <code>.article</code> selector
  41.728 +		and therefore no content
  41.729 +		in the <code>thread</code> flow.
  41.730 +		However, the block container matching
  41.731 +		the <code>.region</code> selector
  41.732 +		is still associated with
  41.733 +		that empty <a>named flow</a>
  41.734 +		and, consequently,
  41.735  		its children are not formatted visually.
  41.736  	</div>
  41.737  
  41.738 @@ -659,92 +660,92 @@
  41.739  		does not result in a <a>CSS Region</a>.
  41.740  	</div>
  41.741  
  41.742 -	<a>CSS Regions</a> 
  41.743 -	create a new 
  41.744 -	<a href="http://www.w3.org/TR/CSS2/visuren.html#z-index">stacking context</a>. 
  41.745 -	<a>CSS Regions</a> 
  41.746 -	establish a new 
  41.747 -	<a href="http://www.w3.org/TR/CSS2/visuren.html#block-formatting">block formatting Context</a>. 
  41.748 -	Exclusions (see [[CSS3-EXCLUSIONS]]) 
  41.749 -	potentially impact the content 
  41.750 -	laid out in <a>region chains</a>, 
  41.751 +	<a>CSS Regions</a>
  41.752 +	create a new
  41.753 +	<a href="http://www.w3.org/TR/CSS2/visuren.html#z-index">stacking context</a>.
  41.754 +	<a>CSS Regions</a>
  41.755 +	establish a new
  41.756 +	<a href="http://www.w3.org/TR/CSS2/visuren.html#block-formatting">block formatting Context</a>.
  41.757 +	Exclusions (see [[CSS3-EXCLUSIONS]])
  41.758 +	potentially impact the content
  41.759 +	laid out in <a>region chains</a>,
  41.760  	just as for non-regions.
  41.761  
  41.762  	<div class="note"><span class="note-prefix">Note </span>
  41.763  
  41.764 -		With <a>region chains</a>, 
  41.765 -		an element may be split across multiple boxes 
  41.766 -		and these boxes may overlap 
  41.767 -		(for example if they are absolutely positioned). 
  41.768 -		So fragments of the same element 
  41.769 -		can overlap each other. 
  41.770 -		Since each element has a single z-index, 
  41.771 -		it would be required to find another mechanism 
  41.772 -		to decide in which order 
  41.773 -		the fragments are rendered. 
  41.774 -		Since each <a>CSS Region</a> creates 
  41.775 -		a new stacking context, 
  41.776 -		it is clear that each fragment is rendered separately 
  41.777 -		and their rendering order follows 
  41.778 +		With <a>region chains</a>,
  41.779 +		an element may be split across multiple boxes
  41.780 +		and these boxes may overlap
  41.781 +		(for example if they are absolutely positioned).
  41.782 +		So fragments of the same element
  41.783 +		can overlap each other.
  41.784 +		Since each element has a single z-index,
  41.785 +		it would be required to find another mechanism
  41.786 +		to decide in which order
  41.787 +		the fragments are rendered.
  41.788 +		Since each <a>CSS Region</a> creates
  41.789 +		a new stacking context,
  41.790 +		it is clear that each fragment is rendered separately
  41.791 +		and their rendering order follows
  41.792  		the regular CSS rendering model.
  41.793  
  41.794 -		Fragments rendering separately 
  41.795 -		is also relevant to elements that might normally 
  41.796 -		be rendered as a unit 
  41.797 -		(for example, 
  41.798 -		an element with its own stacking context, 
  41.799 -		or with transparency). 
  41.800 -		Each fragment of these elements 
  41.801 -		is separately contained in the stacking context 
  41.802 -		created by the <a>CSS Region</a>, 
  41.803 -		so each fragment of these elements 
  41.804 +		Fragments rendering separately
  41.805 +		is also relevant to elements that might normally
  41.806 +		be rendered as a unit
  41.807 +		(for example,
  41.808 +		an element with its own stacking context,
  41.809 +		or with transparency).
  41.810 +		Each fragment of these elements
  41.811 +		is separately contained in the stacking context
  41.812 +		created by the <a>CSS Region</a>,
  41.813 +		so each fragment of these elements
  41.814  		is rendered separately.
  41.815  	</div>
  41.816  
  41.817 -	See the 
  41.818 -	<a href="#regions-visual-formatting-details">regions visual formatting details</a> 
  41.819 -	section for a description of how 
  41.820 -	'width' and 'height' values are resolved 
  41.821 +	See the
  41.822 +	<a href="#regions-visual-formatting-details">regions visual formatting details</a>
  41.823 +	section for a description of how
  41.824 +	'width' and 'height' values are resolved
  41.825  	for <a>CSS Region</a> boxes.
  41.826  
  41.827  <h4 id="circular-dependencies">
  41.828  Cycle Detection</h4>
  41.829  
  41.830 -	<a>named flows</a> containing elements 
  41.831 -	where the value of 'flow-from' computes to an 
  41.832 -	<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a> 
  41.833 +	<a>named flows</a> containing elements
  41.834 +	where the value of 'flow-from' computes to an
  41.835 +	<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>
  41.836  	can produce nonsensical circular relationships,
  41.837 -	such as a <a>named flow</a> 
  41.838 -	containing <a>CSS Regions</a> 
  41.839 -	in its own <a>region chain</a>. 
  41.840 -	These relationships can be easily 
  41.841 -	and reliably detected and resolved, however, 
  41.842 -	by keeping track of a dependency graph 
  41.843 +	such as a <a>named flow</a>
  41.844 +	containing <a>CSS Regions</a>
  41.845 +	in its own <a>region chain</a>.
  41.846 +	These relationships can be easily
  41.847 +	and reliably detected and resolved, however,
  41.848 +	by keeping track of a dependency graph
  41.849  	and using common cycle-detection algorithms.
  41.850  
  41.851  	The dependency graph consists of edges such that:
  41.852  
  41.853  <ul>
  41.854  	<li>
  41.855 -		Every <a>named flow</a> depends on its elements 
  41.856 -		where the value of 'flow-from' computes to an 
  41.857 +		Every <a>named flow</a> depends on its elements
  41.858 +		where the value of 'flow-from' computes to an
  41.859  		<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>.
  41.860  	</li>
  41.861  	<li>
  41.862 -		Every element in a <a>named flow</a> 
  41.863 -		where the value of 'flow-from' computes to an 
  41.864 -		<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a> 
  41.865 -		depends on the <a>named flow</a> with the 
  41.866 -		<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a> 
  41.867 +		Every element in a <a>named flow</a>
  41.868 +		where the value of 'flow-from' computes to an
  41.869 +		<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>
  41.870 +		depends on the <a>named flow</a> with the
  41.871 +		<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>
  41.872  		name.
  41.873  	</li>
  41.874  </ul>
  41.875  
  41.876 -	If the graph contains a cycle, 
  41.877 -	any elements where the value of 'flow-from' 
  41.878 -	computes to an 
  41.879 -	<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a> 
  41.880 -	participating in the cycle 
  41.881 +	If the graph contains a cycle,
  41.882 +	any elements where the value of 'flow-from'
  41.883 +	computes to an
  41.884 +	<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>
  41.885 +	participating in the cycle
  41.886  	do not become <a>CSS Regions</a>.
  41.887  
  41.888  	<div class="note"><span class="note-prefix">Note </span>
  41.889 @@ -758,11 +759,11 @@
  41.890  		}
  41.891  		</pre>
  41.892  
  41.893 -		would move the <code>#id</code> element to a "foolish" <a>named flow</a>, 
  41.894 -		and try to make the <code>#id</code> element 
  41.895 -		a <a>CSS Region</a> for the "foolish" <a>named flow</a>. 
  41.896 -		The "foolish" <a>named flow</a> would then contain its own region, 
  41.897 -		creating a cycle. 
  41.898 +		would move the <code>#id</code> element to a "foolish" <a>named flow</a>,
  41.899 +		and try to make the <code>#id</code> element
  41.900 +		a <a>CSS Region</a> for the "foolish" <a>named flow</a>.
  41.901 +		The "foolish" <a>named flow</a> would then contain its own region,
  41.902 +		creating a cycle.
  41.903  		So the <code>#id</code> element does not become a <a>CSS Region</a>.
  41.904  	</div>
  41.905  
  41.906 @@ -783,33 +784,33 @@
  41.907  <h4 id="fragmenting-regions">
  41.908  Nested fragmentation contexts</h4>
  41.909  
  41.910 -	A <a>CSS Region</a> that contains 
  41.911 -	a fragment of a <a>named flow</a> 
  41.912 -	can itself be fragmented if it is nested 
  41.913 -	within a fragmentation context [[!CSS3-BREAK]], 
  41.914 -	such as when a layout 
  41.915 -	using a <a>region chain</a> is printed. 
  41.916 -	In these cases break opportunities 
  41.917 -	in the named flow fragment 
  41.918 -	contained by the <a>CSS Region</a> 
  41.919 -	are determined using the standard 
  41.920 -	<a href="http://www.w3.org/TR/css3-break/">fragmentation rules</a>. 
  41.921 -	In other words, 
  41.922 -	each region box and its associated fragment 
  41.923 -	should break as if it were a simple div 
  41.924 -	containing the fragment contents. 
  41.925 -	This can be controlled by using 
  41.926 -	an avoid break value on the <a>CSS Region</a>, 
  41.927 +	A <a>CSS Region</a> that contains
  41.928 +	a fragment of a <a>named flow</a>
  41.929 +	can itself be fragmented if it is nested
  41.930 +	within a fragmentation context [[!CSS3-BREAK]],
  41.931 +	such as when a layout
  41.932 +	using a <a>region chain</a> is printed.
  41.933 +	In these cases break opportunities
  41.934 +	in the named flow fragment
  41.935 +	contained by the <a>CSS Region</a>
  41.936 +	are determined using the standard
  41.937 +	<a href="http://www.w3.org/TR/css3-break/">fragmentation rules</a>.
  41.938 +	In other words,
  41.939 +	each region box and its associated fragment
  41.940 +	should break as if it were a simple div
  41.941 +	containing the fragment contents.
  41.942 +	This can be controlled by using
  41.943 +	an avoid break value on the <a>CSS Region</a>,
  41.944  	if that is desired.
  41.945  
  41.946 -	A <a>CSS Region</a> can be part 
  41.947 -	of the contents of a separate named flow, 
  41.948 -	as long as there are no cycles broken 
  41.949 -	by the <a href="#circular-dependencies">Cycle Detection</a> 
  41.950 -	described above. 
  41.951 -	This case is a <dfn>nested region context</dfn>, 
  41.952 -	which has an effect 
  41.953 -	on the <a href="#regions-visual-formatting-steps">Visual Formatting Steps</a> 
  41.954 +	A <a>CSS Region</a> can be part
  41.955 +	of the contents of a separate named flow,
  41.956 +	as long as there are no cycles broken
  41.957 +	by the <a href="#circular-dependencies">Cycle Detection</a>
  41.958 +	described above.
  41.959 +	This case is a <dfn>nested region context</dfn>,
  41.960 +	which has an effect
  41.961 +	on the <a href="#regions-visual-formatting-steps">Visual Formatting Steps</a>
  41.962  	described below.
  41.963  
  41.964  <h3 id="region-flow-break">
  41.965 @@ -817,26 +818,26 @@
  41.966  
  41.967  <div class="note"><span class="note-prefix">Note </span>
  41.968  
  41.969 -	This section is also defined in [[!CSS3-BREAK]]. 
  41.970 -	If that specification moves to last call 
  41.971 -	with the region values, 
  41.972 +	This section is also defined in [[!CSS3-BREAK]].
  41.973 +	If that specification moves to last call
  41.974 +	with the region values,
  41.975  	the section here can be replaced by a reference.
  41.976  </div>
  41.977  
  41.978 -	User agents laying out content in multiple regions 
  41.979 -	must determine where content breaks occur. 
  41.980 -	The problem of breaking content into fragments fitting in regions 
  41.981 +	User agents laying out content in multiple regions
  41.982 +	must determine where content breaks occur.
  41.983 +	The problem of breaking content into fragments fitting in regions
  41.984  	is similar to breaking content into pages or columns.
  41.985  
  41.986 -	Each break ends layout in the current region 
  41.987 -	and causes remaining pieces of content 
  41.988 -	from the <a>named flow</a> to be visually formatted 
  41.989 -	in the following region in the <a>region chain</a>, 
  41.990 +	Each break ends layout in the current region
  41.991 +	and causes remaining pieces of content
  41.992 +	from the <a>named flow</a> to be visually formatted
  41.993 +	in the following region in the <a>region chain</a>,
  41.994  	if there is one.
  41.995  
  41.996 -	The following extends 
  41.997 -	the 'break-before', 'break-after' and 'break-inside' properties 
  41.998 -	from the [[!CSS3COL]] specification to account for regions. 
  41.999 +	The following extends
 41.1000 +	the 'break-before', 'break-after' and 'break-inside' properties
 41.1001 +	from the [[!CSS3COL]] specification to account for regions.
 41.1002  	The additional values are described below.
 41.1003  
 41.1004  	<pre class='propdef'>
 41.1005 @@ -885,8 +886,8 @@
 41.1006  		<dd>Avoid a region break before (after, inside) the generated box.</dd>
 41.1007  	</dl>
 41.1008  
 41.1009 -	The behavior of region breaks with regards to regions 
 41.1010 -	is identical to the behavior of page breaks with regards to pages, 
 41.1011 +	The behavior of region breaks with regards to regions
 41.1012 +	is identical to the behavior of page breaks with regards to pages,
 41.1013  	as defined in the [[!CSS21]].
 41.1014  
 41.1015  <h3 id="the-region-fragment-property">
 41.1016 @@ -902,19 +903,19 @@
 41.1017  		Media: visual
 41.1018  	</pre>
 41.1019  
 41.1020 -	The 'region-fragment' property controls the behavior 
 41.1021 -	of the <em id="last-region">last region</em> 
 41.1022 +	The 'region-fragment' property controls the behavior
 41.1023 +	of the <em id="last-region">last region</em>
 41.1024  	associated with a <a>named flow</a>.
 41.1025  
 41.1026  	<dl>
 41.1027  		<dt>auto</dt>
 41.1028  
 41.1029  		<dd>
 41.1030 -			Content flows as it would in a regular content box. 
 41.1031 -			If the content exceeds the container box, 
 41.1032 -			it is subject to the 
 41.1033 -			<a href= "http://www.w3.org/TR/CSS21/visufx.html#propdef-overflow">overflow</a> 
 41.1034 -			property's computed value on the <a>CSS Region</a>. 
 41.1035 +			Content flows as it would in a regular content box.
 41.1036 +			If the content exceeds the container box,
 41.1037 +			it is subject to the
 41.1038 +			<a href= "http://www.w3.org/TR/CSS21/visufx.html#propdef-overflow">overflow</a>
 41.1039 +			property's computed value on the <a>CSS Region</a>.
 41.1040  			Region breaks must be ignored on the last region.
 41.1041  		</dd>
 41.1042  
 41.1043 @@ -922,21 +923,21 @@
 41.1044  
 41.1045  		<dd>
 41.1046  
 41.1047 -			If the content fits within the <a>CSS Region</a>, 
 41.1048 -			then this property has no effect. 
 41.1049 -			If the content does not fit within the <a>CSS Region</a>, 
 41.1050 -			the content breaks as if flow was going to continue in a subsequent region. 
 41.1051 -			See the <a href= "#regions-flow-breaking-rules">breaking rules</a> section. 
 41.1052 +			If the content fits within the <a>CSS Region</a>,
 41.1053 +			then this property has no effect.
 41.1054 +			If the content does not fit within the <a>CSS Region</a>,
 41.1055 +			the content breaks as if flow was going to continue in a subsequent region.
 41.1056 +			See the <a href= "#regions-flow-breaking-rules">breaking rules</a> section.
 41.1057  			A forced region break takes precedence over a natural break point.
 41.1058  
 41.1059  			Flow content that follows the last break in the last region is not rendered.
 41.1060  		</dd>
 41.1061  	</dl>
 41.1062  
 41.1063 -	The 'region-fragment' property does not influence 
 41.1064 +	The 'region-fragment' property does not influence
 41.1065  	the size of the region it applies to.
 41.1066  
 41.1067 -	The following code sample illustrates 
 41.1068 +	The following code sample illustrates
 41.1069  	the usage of the 'region-fragment' property.
 41.1070  
 41.1071  	<div class="example">
 41.1072 @@ -1009,40 +1010,40 @@
 41.1073  
 41.1074  	<div class="note"><span class="note-prefix">Note </span>
 41.1075  
 41.1076 -		The 'overflow' property is honored on a region: 
 41.1077 -		if region content overflows, 
 41.1078 -		such as the borders of elements 
 41.1079 -		on the last line, 
 41.1080 -		the 'overflow' property controls 
 41.1081 -		the visibility of the overflowing content. 
 41.1082 +		The 'overflow' property is honored on a region:
 41.1083 +		if region content overflows,
 41.1084 +		such as the borders of elements
 41.1085 +		on the last line,
 41.1086 +		the 'overflow' property controls
 41.1087 +		the visibility of the overflowing content.
 41.1088  		See the 'overflow' property definition ([[CSS21]]).
 41.1089  	</div>
 41.1090  
 41.1091  <h2 id="cssom_view_and_css_regions">
 41.1092  CSSOM</h2>
 41.1093  
 41.1094 -	Since content may flow into multiple regions, 
 41.1095 -	authors need a way to determine if there are enough regions 
 41.1096 -	to flow all the content from a named flow. 
 41.1097 -	This is especially important considering that the size of regions 
 41.1098 -	or the size of the content may change depending on the display context. 
 41.1099 -	For example, 
 41.1100 -	flowing the same content on a mobile phone with a small screen 
 41.1101 -	may require more regions than on a large desktop display. 
 41.1102 -	Another example is the user changing 
 41.1103 -	the font size of text flowing through regions. 
 41.1104 -	Depending on the change, 
 41.1105 -	new regions may be needed to accommodate for the additional space required 
 41.1106 +	Since content may flow into multiple regions,
 41.1107 +	authors need a way to determine if there are enough regions
 41.1108 +	to flow all the content from a named flow.
 41.1109 +	This is especially important considering that the size of regions
 41.1110 +	or the size of the content may change depending on the display context.
 41.1111 +	For example,
 41.1112 +	flowing the same content on a mobile phone with a small screen
 41.1113 +	may require more regions than on a large desktop display.
 41.1114 +	Another example is the user changing
 41.1115 +	the font size of text flowing through regions.
 41.1116 +	Depending on the change,
 41.1117 +	new regions may be needed to accommodate for the additional space required
 41.1118  	to fit the larger text or some regions may need to be removed for smaller text.
 41.1119  
 41.1120  <h3 id="the-namedflow-interface">
 41.1121  The NamedFlow interface</h3>
 41.1122  
 41.1123 -	The following APIs allow scripts 
 41.1124 -	to reference a <a idl>NamedFlow</a> 
 41.1125 +	The following APIs allow scripts
 41.1126 +	to reference a <a idl>NamedFlow</a>
 41.1127  	object representation of a <a>named flow</a>.
 41.1128  
 41.1129 -	An additional attribute on the 
 41.1130 +	An additional attribute on the
 41.1131  	<a href= "http://www.w3.org/TR/dom/#interface-document">
 41.1132  		<code class= "idl">Document</code></a>
 41.1133  	interface provide access to <a>named flows</a>.
 41.1134 @@ -1053,29 +1054,29 @@
 41.1135  		};
 41.1136  	</pre>
 41.1137  
 41.1138 -	The 
 41.1139 -	<dfn id="document-namedflows"><code class="idl">namedFlows</code></dfn> 
 41.1140 -	attribute on the 
 41.1141 +	The
 41.1142 +	<dfn id="document-namedflows"><code class="idl">namedFlows</code></dfn>
 41.1143 +	attribute on the
 41.1144  	<a href= "http://www.w3.org/TR/dom/#interface-document">
 41.1145  		<code class= "idl">Document</code>
 41.1146 -	</a> 
 41.1147 -	interface returns a static snapshot 
 41.1148 -	of all the current <a>named flows</a> 
 41.1149 -	in the document. 
 41.1150 +	</a>
 41.1151 +	interface returns a static snapshot
 41.1152 +	of all the current <a>named flows</a>
 41.1153 +	in the document.
 41.1154  
 41.1155  	The <dfn attribute for="Document"><code class="idl">namedFlows</code></dfn>
 41.1156 -	map must include all <a>named flows</a> 
 41.1157 -	that are currently in the <code>CREATED</code> state. 
 41.1158 -	The list must not include <a>named flows</a> 
 41.1159 -	that are in the <code>NULL</code> state. 
 41.1160 +	map must include all <a>named flows</a>
 41.1161 +	that are currently in the <code>CREATED</code> state.
 41.1162 +	The list must not include <a>named flows</a>
 41.1163 +	that are in the <code>NULL</code> state.
 41.1164  
 41.1165 -	The 
 41.1166 +	The
 41.1167  	<dfn interface><code class="idl">NamedFlowMap</code></dfn>
 41.1168 -	interface provides a map of current 
 41.1169 -	<a idl>NamedFlow</a> instances 
 41.1170 -	in the document. 
 41.1171 -	The <a idl>NamedFlowMap</a> object 
 41.1172 -	is a snapshot of the data, 
 41.1173 +	interface provides a map of current
 41.1174 +	<a idl>NamedFlow</a> instances
 41.1175 +	in the document.
 41.1176 +	The <a idl>NamedFlowMap</a> object
 41.1177 +	is a snapshot of the data,
 41.1178  	and is read-only.
 41.1179  
 41.1180  	<pre class="idl">
 41.1181 @@ -1087,41 +1088,41 @@
 41.1182  		};
 41.1183  	</pre>
 41.1184  
 41.1185 -	The map entries in a 
 41.1186 -	<a idl>NamedFlowMap</a> object 
 41.1187 +	The map entries in a
 41.1188 +	<a idl>NamedFlowMap</a> object
 41.1189  	are the named flow idents
 41.1190 -	paired with their 
 41.1191 -	<a idl>NamedFlow</a> objects. 
 41.1192 -	The <dfn method for="NamedFlowMap">get()</dfn> 
 41.1193 -	and <dfn method for="NamedFlowMap">has()</dfn> 
 41.1194 +	paired with their
 41.1195 +	<a idl>NamedFlow</a> objects.
 41.1196 +	The <dfn method for="NamedFlowMap">get()</dfn>
 41.1197 +	and <dfn method for="NamedFlowMap">has()</dfn>
 41.1198  	methods return null and false respectively
 41.1199 -	if there is no <a idl>NamedFlow</a> 
 41.1200 -	with the given ident. 
 41.1201 -	The <dfn method for="NamedFlowMap">set()</dfn> 
 41.1202 -	and <dfn method for="NamedFlowMap">delete()</dfn> 
 41.1203 +	if there is no <a idl>NamedFlow</a>
 41.1204 +	with the given ident.
 41.1205 +	The <dfn method for="NamedFlowMap">set()</dfn>
 41.1206 +	and <dfn method for="NamedFlowMap">delete()</dfn>
 41.1207  	methods always throw an
 41.1208 -	<code>InvalidAccessError</code> exception, 
 41.1209 -	as this map is read-only. 
 41.1210 -	The <a idl>NamedFlowMap</a> interface 
 41.1211 -	uses the rest of the default map 
 41.1212 +	<code>InvalidAccessError</code> exception,
 41.1213 +	as this map is read-only.
 41.1214 +	The <a idl>NamedFlowMap</a> interface
 41.1215 +	uses the rest of the default map
 41.1216  	<a href="http://dev.w3.org/2006/webapi/WebIDL/#es-map-members">class methods</a>.
 41.1217  
 41.1218 -	The <dfn interface><code class="idl">NamedFlow</code></dfn> 
 41.1219 -	interface offers a representation 
 41.1220 +	The <dfn interface><code class="idl">NamedFlow</code></dfn>
 41.1221 +	interface offers a representation
 41.1222  	of a <a>named flow</a> instance.
 41.1223  
 41.1224 -	The <a idl>NamedFlow</a> interface 
 41.1225 -	can be used for different purposes. 
 41.1226 -	For example, the <code>getRegionsByContent()</code> method 
 41.1227 -	can help navigate by bookmark: 
 41.1228 -	a script can find the <a>CSS Regions</a> 
 41.1229 -	that display a particular anchor 
 41.1230 +	The <a idl>NamedFlow</a> interface
 41.1231 +	can be used for different purposes.
 41.1232 +	For example, the <code>getRegionsByContent()</code> method
 41.1233 +	can help navigate by bookmark:
 41.1234 +	a script can find the <a>CSS Regions</a>
 41.1235 +	that display a particular anchor
 41.1236  	and bring them to view.
 41.1237  
 41.1238 -	Likewise, the interface allows authors 
 41.1239 -	to check if all content has been fitted 
 41.1240 -	into existing regions. 
 41.1241 -	If it has, the <a idl>overset</a> attribute 
 41.1242 +	Likewise, the interface allows authors
 41.1243 +	to check if all content has been fitted
 41.1244 +	into existing regions.
 41.1245 +	If it has, the <a idl>overset</a> attribute
 41.1246  	would be false.
 41.1247  
 41.1248  	<pre class="idl">
 41.1249 @@ -1138,88 +1139,88 @@
 41.1250  	The <dfn attribute for="NamedFlow"><code class="idl">name</code></dfn> attribute
 41.1251  	returns the name of the <a idl>NamedFlow</a> instance.
 41.1252  
 41.1253 -	The <dfn attribute for="NamedFlow"><code class="idl">overset</code></dfn> 
 41.1254 -	attribute returns true 
 41.1255 -	if there are <a>named flow</a> fragments 
 41.1256 -	that do not fit 
 41.1257 -	in the associated <a>region chain</a> 
 41.1258 -	(including the case where 
 41.1259 -	there are <a>named flow</a> fragments 
 41.1260 -	but no regions in the <a>region chain</a>). 
 41.1261 +	The <dfn attribute for="NamedFlow"><code class="idl">overset</code></dfn>
 41.1262 +	attribute returns true
 41.1263 +	if there are <a>named flow</a> fragments
 41.1264 +	that do not fit
 41.1265 +	in the associated <a>region chain</a>
 41.1266 +	(including the case where
 41.1267 +	there are <a>named flow</a> fragments
 41.1268 +	but no regions in the <a>region chain</a>).
 41.1269  	Otherwise, it returns false.
 41.1270  
 41.1271 -	The <dfn method for="NamedFlow"><code class="idl">getRegions()</code></dfn> 
 41.1272 -	method returns the sequence 
 41.1273 -	of regions in the <a>region chain</a> 
 41.1274 -	associated with the <a>named flow</a>. 
 41.1275 -	Note that the returned values 
 41.1276 -	is a static sequence 
 41.1277 +	The <dfn method for="NamedFlow"><code class="idl">getRegions()</code></dfn>
 41.1278 +	method returns the sequence
 41.1279 +	of regions in the <a>region chain</a>
 41.1280 +	associated with the <a>named flow</a>.
 41.1281 +	Note that the returned values
 41.1282 +	is a static sequence
 41.1283  	in document order.
 41.1284  
 41.1285 -	The <dfn attribute for="NamedFlow">firstEmptyRegionIndex</dfn> 
 41.1286 -	is the index of the first region 
 41.1287 -	in the <a>region chain</a> with the <code>regionOverset</code> attribute 
 41.1288 -	set to <code>empty</code>. 
 41.1289 -	If all regions have the <code>regionOverset</code> attribute 
 41.1290 -	set to <code>fit</code> or <code>overset</code>, 
 41.1291 -	the value for <code>firstEmptyRegionIndex</code> is <code>-1</code>. 
 41.1292 -	If there are no regions in the <a>region chain</a>, 
 41.1293 +	The <dfn attribute for="NamedFlow">firstEmptyRegionIndex</dfn>
 41.1294 +	is the index of the first region
 41.1295 +	in the <a>region chain</a> with the <code>regionOverset</code> attribute
 41.1296 +	set to <code>empty</code>.
 41.1297 +	If all regions have the <code>regionOverset</code> attribute
 41.1298 +	set to <code>fit</code> or <code>overset</code>,
 41.1299 +	the value for <code>firstEmptyRegionIndex</code> is <code>-1</code>.
 41.1300 +	If there are no regions in the <a>region chain</a>,
 41.1301  	the value is <code>-1</code> as well.
 41.1302  
 41.1303 -	The <dfn method for="NamedFlow">getContent()</dfn> 
 41.1304 -	method returns an ordered collection 
 41.1305 -	of nodes that constitute the <a>named flow</a>. 
 41.1306 -	The returned list is a static snapshot 
 41.1307 -	of the <a>named flow</a> content 
 41.1308 -	at the time the method is invoked. 
 41.1309 -	This list contains the contents	
 41.1310 -	that were moved to the <a>named flow</a> 
 41.1311 -	by the flow-into property 
 41.1312 -	but not any descendants 
 41.1313 -	(unless the descendants are themselves 
 41.1314 +	The <dfn method for="NamedFlow">getContent()</dfn>
 41.1315 +	method returns an ordered collection
 41.1316 +	of nodes that constitute the <a>named flow</a>.
 41.1317 +	The returned list is a static snapshot
 41.1318 +	of the <a>named flow</a> content
 41.1319 +	at the time the method is invoked.
 41.1320 +	This list contains the contents
 41.1321 +	that were moved to the <a>named flow</a>
 41.1322 +	by the flow-into property
 41.1323 +	but not any descendants
 41.1324 +	(unless the descendants are themselves
 41.1325  	moved to the <a>named flow</a>).
 41.1326  
 41.1327 -	The <dfn method for="NamedFlow">getRegionsByContent()</dfn> 
 41.1328 -	method returns the sequence of regions 
 41.1329 -	that contain at least part 
 41.1330 -	of the target content node 
 41.1331 -	if it belongs to the <a>named flow</a> directly 
 41.1332 -	or one of its ancestors belongs to the <a>named flow</a>. 
 41.1333 -	Otherwise, the method returns 
 41.1334 -	an empty sequence. 
 41.1335 +	The <dfn method for="NamedFlow">getRegionsByContent()</dfn>
 41.1336 +	method returns the sequence of regions
 41.1337 +	that contain at least part
 41.1338 +	of the target content node
 41.1339 +	if it belongs to the <a>named flow</a> directly
 41.1340 +	or one of its ancestors belongs to the <a>named flow</a>.
 41.1341 +	Otherwise, the method returns
 41.1342 +	an empty sequence.
 41.1343  	The returned value
 41.1344 -	is a static sequence 
 41.1345 +	is a static sequence
 41.1346  	in document order.
 41.1347  
 41.1348  	The <a>named flow</a> states are :
 41.1349  
 41.1350  	<ul>
 41.1351  		<li>
 41.1352 -			<code class="idl">NULL</code>: the <a>named flow</a> 
 41.1353 +			<code class="idl">NULL</code>: the <a>named flow</a>
 41.1354  			contains no conent and has no <a>region chain</a>.
 41.1355  		</li>
 41.1356  		<li>
 41.1357 -			<code class="idl">CREATED</code>: the <a>named flow</a> 
 41.1358 +			<code class="idl">CREATED</code>: the <a>named flow</a>
 41.1359  			either contains content or has a <a>region chain</a>.
 41.1360  		</li>
 41.1361  	</ul>
 41.1362  
 41.1363 -	A <a idl>NamedFlow</a> object is live: 
 41.1364 -	it always represents the <a>named flow</a> 
 41.1365 -	with the corresponding name even if 
 41.1366 -	that <a>named flow</a> has transitioned 
 41.1367 +	A <a idl>NamedFlow</a> object is live:
 41.1368 +	it always represents the <a>named flow</a>
 41.1369 +	with the corresponding name even if
 41.1370 +	that <a>named flow</a> has transitioned
 41.1371  	to the <code>NULL</code> state.
 41.1372  
 41.1373  <h3 id="the-region-interface">
 41.1374  The Region interface</h3>
 41.1375  
 41.1376 -	The <dfn interface><code class="idl">Region</code></dfn> 
 41.1377 -	interface is a 
 41.1378 +	The <dfn interface><code class="idl">Region</code></dfn>
 41.1379 +	interface is a
 41.1380  	<a href="http://www.w3.org/TR/WebIDL/#idl-implements-statements">supplemental interface</a>
 41.1381 -	which must be implemented by all objects 
 41.1382 +	which must be implemented by all objects
 41.1383  	(<a href="http://www.w3.org/TR/dom/#interface-element">
 41.1384 -		<code class= "idl">Elements</code></a>, 
 41.1385 -	pseudo-elements or other CSS constructs 
 41.1386 +		<code class= "idl">Elements</code></a>,
 41.1387 +	pseudo-elements or other CSS constructs
 41.1388  	such as <a href="http://dev.w3.org/csswg/css3-page-template/#templates-and-slots">slots</a>) in an implementation which can be <a>CSS Regions</a>.
 41.1389  
 41.1390  	<pre class="idl">
 41.1391 @@ -1232,44 +1233,44 @@
 41.1392  		Element implements Region;
 41.1393  	</pre>
 41.1394  
 41.1395 -	The <dfn attribute for="Region"><code class= "idl">regionOverset</code></dfn> 
 41.1396 +	The <dfn attribute for="Region"><code class= "idl">regionOverset</code></dfn>
 41.1397  	attribute returns one of the following values:
 41.1398  
 41.1399  	<dl>
 41.1400  		<dt>''overset''</dt>
 41.1401  
 41.1402  		<dd>
 41.1403 -			The region is the last one in the 
 41.1404 -			<a>region chain</a> and 
 41.1405 +			The region is the last one in the
 41.1406 +			<a>region chain</a> and
 41.1407  			not able to fit the remaining content from the <a>named flow</a>.
 41.1408 -			Note that the region's 
 41.1409 +			Note that the region's
 41.1410  			<a href= "http://www.w3.org/TR/CSS21/visufx.html#overflow">
 41.1411 -				<code class= "idl">overflow</code></a> 
 41.1412 -			property value can be used to control the 
 41.1413 -			visibility of the overflowing content and the 
 41.1414 -			'region-fragment' property controls whether or not fragmentation happens 
 41.1415 +				<code class= "idl">overflow</code></a>
 41.1416 +			property value can be used to control the
 41.1417 +			visibility of the overflowing content and the
 41.1418 +			'region-fragment' property controls whether or not fragmentation happens
 41.1419  			on the content that overflows the last region.
 41.1420  		</dd>
 41.1421  
 41.1422  		<dt>''fit''</dt>
 41.1423  
 41.1424  		<dd>
 41.1425 -			The region's flow fragment content 
 41.1426 -			fits into the region's 
 41.1427 -			<a href="http://www.w3.org/TR/CSS21/box.html#box-dimensions">content box</a>. 
 41.1428 -			If the region is the last one 
 41.1429 -			in the <a>region chain</a>, 
 41.1430 -			it means that the content 
 41.1431 +			The region's flow fragment content
 41.1432 +			fits into the region's
 41.1433 +			<a href="http://www.w3.org/TR/CSS21/box.html#box-dimensions">content box</a>.
 41.1434 +			If the region is the last one
 41.1435 +			in the <a>region chain</a>,
 41.1436 +			it means that the content
 41.1437  			fits without overflowing.
 41.1438 -			If the region is not the last one 
 41.1439 -			in the <a>region chain</a>, 
 41.1440 -			that means the <a>named flow</a> content 
 41.1441 -			may be further fitted in subsequent regions. 
 41.1442 -			In this last case, 
 41.1443 -			note that the <a>named flow</a> fragment may be empty 
 41.1444 -			(for example if the region is too small 
 41.1445 -			to accommodate any content). 
 41.1446 -			This value is returned if the <a idl>Region</a> object 
 41.1447 +			If the region is not the last one
 41.1448 +			in the <a>region chain</a>,
 41.1449 +			that means the <a>named flow</a> content
 41.1450 +			may be further fitted in subsequent regions.
 41.1451 +			In this last case,
 41.1452 +			note that the <a>named flow</a> fragment may be empty
 41.1453 +			(for example if the region is too small
 41.1454 +			to accommodate any content).
 41.1455 +			This value is returned if the <a idl>Region</a> object
 41.1456  			is not (or no longer) a region.
 41.1457  		</dd>
 41.1458  
 41.1459 @@ -1281,80 +1282,80 @@
 41.1460  
 41.1461  	</dl>
 41.1462  
 41.1463 -	If there is no content 
 41.1464 -	in the <a>named flow</a>, 
 41.1465 -	all regions associated 
 41.1466 -	with that <a>named flow</a> 
 41.1467 -	should have their <a idl>regionOverset</a> 
 41.1468 -	attribute return ''empty''. 
 41.1469 -	If there is content in the flow 
 41.1470 -	but that content does not 
 41.1471 -	generate any box for visual formatting, 
 41.1472 -	the ''overset'' attribute on the first region 
 41.1473 -	in the <a>region chain</a> associated 
 41.1474 +	If there is no content
 41.1475 +	in the <a>named flow</a>,
 41.1476 +	all regions associated
 41.1477 +	with that <a>named flow</a>
 41.1478 +	should have their <a idl>regionOverset</a>
 41.1479 +	attribute return ''empty''.
 41.1480 +	If there is content in the flow
 41.1481 +	but that content does not
 41.1482 +	generate any box for visual formatting,
 41.1483 +	the ''overset'' attribute on the first region
 41.1484 +	in the <a>region chain</a> associated
 41.1485  	with the flow will return ''fit''.
 41.1486  
 41.1487 -	The <dfn method for="Region">getRegionFlowRanges()</dfn> method 
 41.1488 -	returns an array of <a href= "http://www.w3.org/TR/dom/#interface-range">Range</a> 
 41.1489 -	instances corresponding to fragment 
 41.1490 -	from the <a>named flow</a> 
 41.1491 -	that is laid out in the region. 
 41.1492 -	If the region has not received a fragment 
 41.1493 -	because it is too small to accommodate any, 
 41.1494 -	the method returns a single <a idl>Range</a> 
 41.1495 -	where the <code>startContainer</code> 
 41.1496 -	and <code>startOffset</code> 
 41.1497 -	have the same values as 
 41.1498 -	the <code>endContainer</code> 
 41.1499 -	and <code>endOffset</code> 
 41.1500 -	and therefore the collapsed attribute 
 41.1501 -	on the <a idl>Range</a> is true. 
 41.1502 -	In that situation, 
 41.1503 -	if the region is the first 
 41.1504 -	in the <a>region chain</a>, 
 41.1505 -	the <code>startContainer</code> 
 41.1506 -	is the first <code>Node</code> 
 41.1507 -	in the <a>named flow</a> 
 41.1508 -	and the <code>startOffset</code> is zero. 
 41.1509 -	If the region is the last region 
 41.1510 -	in the <a>region chain</a> 
 41.1511 -	(but not the first and only one), 
 41.1512 -	the <code>startContainer</code> 
 41.1513 -	and <code>startOffset</code> 
 41.1514 -	are the same values as 
 41.1515 -	the <code>endContainer</code> 
 41.1516 -	and <code>endOffset</code> 
 41.1517 -	on the previous region 
 41.1518 -	in the <a>region chain</a>. 
 41.1519 -	The method returns null 
 41.1520 -	if the <span>region</span> object 
 41.1521 +	The <dfn method for="Region">getRegionFlowRanges()</dfn> method
 41.1522 +	returns an array of <a href= "http://www.w3.org/TR/dom/#interface-range">Range</a>
 41.1523 +	instances corresponding to fragment
 41.1524 +	from the <a>named flow</a>
 41.1525 +	that is laid out in the region.
 41.1526 +	If the region has not received a fragment
 41.1527 +	because it is too small to accommodate any,
 41.1528 +	the method returns a single <a idl>Range</a>
 41.1529 +	where the <code>startContainer</code>
 41.1530 +	and <code>startOffset</code>
 41.1531 +	have the same values as
 41.1532 +	the <code>endContainer</code>
 41.1533 +	and <code>endOffset</code>
 41.1534 +	and therefore the collapsed attribute
 41.1535 +	on the <a idl>Range</a> is true.
 41.1536 +	In that situation,
 41.1537 +	if the region is the first
 41.1538 +	in the <a>region chain</a>,
 41.1539 +	the <code>startContainer</code>
 41.1540 +	is the first <code>Node</code>
 41.1541 +	in the <a>named flow</a>
 41.1542 +	and the <code>startOffset</code> is zero.
 41.1543 +	If the region is the last region
 41.1544 +	in the <a>region chain</a>
 41.1545 +	(but not the first and only one),
 41.1546 +	the <code>startContainer</code>
 41.1547 +	and <code>startOffset</code>
 41.1548 +	are the same values as
 41.1549 +	the <code>endContainer</code>
 41.1550 +	and <code>endOffset</code>
 41.1551 +	on the previous region
 41.1552 +	in the <a>region chain</a>.
 41.1553 +	The method returns null
 41.1554 +	if the <span>region</span> object
 41.1555  	is not (or no longer) a region.
 41.1556  
 41.1557 -	A <a idl>Region</a> instance 
 41.1558 -	may represent an object 
 41.1559 -	that is no longer a <span>region</span>. 
 41.1560 -	This may happen for example 
 41.1561 -	if the 'flow-from' property 
 41.1562 -	on the corresponding pseudo-element, 
 41.1563 +	A <a idl>Region</a> instance
 41.1564 +	may represent an object
 41.1565 +	that is no longer a <span>region</span>.
 41.1566 +	This may happen for example
 41.1567 +	if the 'flow-from' property
 41.1568 +	on the corresponding pseudo-element,
 41.1569  	element or other construct
 41.1570 -	becomes ''none'' 
 41.1571 -	but a script is still holding 
 41.1572 +	becomes ''none''
 41.1573 +	but a script is still holding
 41.1574  	a reference to the <a idl>Region</a> object.
 41.1575  
 41.1576  <h3 id="named-flow-events">
 41.1577  Named flow events</h3>
 41.1578  
 41.1579  	<a idl>NamedFlow</a>
 41.1580 -	objects are <a href="http://www.w3.org/TR/dom/#interface-eventtarget">EventTargets</a> 
 41.1581 -	which dispatch the following events 
 41.1582 -	for their respective triggers. 
 41.1583 -	These events are asynchronous, 
 41.1584 -	and fire at the end of the	
 41.1585 -	<a href="#named-flows-layout">regions visual formatting</a> 
 41.1586 +	objects are <a href="http://www.w3.org/TR/dom/#interface-eventtarget">EventTargets</a>
 41.1587 +	which dispatch the following events
 41.1588 +	for their respective triggers.
 41.1589 +	These events are asynchronous,
 41.1590 +	and fire at the end of the
 41.1591 +	<a href="#named-flows-layout">regions visual formatting</a>
 41.1592  	steps.
 41.1593  
 41.1594 -	The regionfragmentchange event is dispatched 
 41.1595 -	on any change to a named flow's fragmentation through its <a>region chain</a>, 
 41.1596 +	The regionfragmentchange event is dispatched
 41.1597 +	on any change to a named flow's fragmentation through its <a>region chain</a>,
 41.1598  	including changes to any overset fragment.
 41.1599  
 41.1600  	<table class="event-desc" style="border: 1px solid gray">
 41.1601 @@ -1362,12 +1363,12 @@
 41.1602  			<tr class="assert must"><th>Type</th>
 41.1603  				<td class="eventname"><strong><code>regionfragmentchange</code></strong></td>
 41.1604  			</tr>
 41.1605 -			<tr class="assert must"><th>Interface</th> 
 41.1606 +			<tr class="assert must"><th>Interface</th>
 41.1607  				<td><code><a href="http://www.w3.org/TR/DOM-Level-3-Events/#events-uievents">UIEvent</a></code> (see [[!DOM-LEVEL-3-EVENTS]])</td>
 41.1608  			</tr>
 41.1609  			<tr class="assert must"><th>Sync / Async</th> <td>Async</td></tr>
 41.1610  			<tr class="assert must"><th>Bubbles</th> <td>No</td></tr>
 41.1611 -			<tr class="assert must"><th>Target</th> 
 41.1612 +			<tr class="assert must"><th>Target</th>
 41.1613  				<td><a idl>NamedFlow</a></td>
 41.1614  			</tr>
 41.1615  			<tr class="assert must"><th>Cancelable</th> <td>Yes</td></tr>
 41.1616 @@ -1375,7 +1376,7 @@
 41.1617  			<tr class="assert must"><th>Context info</th>
 41.1618  				<td>
 41.1619  					<ul>
 41.1620 -						<li><code class="attribute-name">Event.target</code>: 
 41.1621 +						<li><code class="attribute-name">Event.target</code>:
 41.1622  							<a idl>NamedFlow</a> whose fragmentation has changed.
 41.1623  						</li>
 41.1624  					</ul>
 41.1625 @@ -1385,9 +1386,9 @@
 41.1626  	</table>
 41.1627  
 41.1628  
 41.1629 -	The regionoversetchange event is dispatched 
 41.1630 -	if any of the regionOverset values change 
 41.1631 -	in a named flow's <a>region chain</a>, 
 41.1632 +	The regionoversetchange event is dispatched
 41.1633 +	if any of the regionOverset values change
 41.1634 +	in a named flow's <a>region chain</a>,
 41.1635  	including when regions are added or removed from the chain.
 41.1636  
 41.1637  	<table class="event-desc" style="border: 1px solid gray">
 41.1638 @@ -1395,12 +1396,12 @@
 41.1639  			<tr class="assert must"><th>Type</th>
 41.1640  				<td class="eventname"><strong><code>regionoversetchange</code></strong></td>
 41.1641  			</tr>
 41.1642 -			<tr class="assert must"><th>Interface</th> 
 41.1643 +			<tr class="assert must"><th>Interface</th>
 41.1644  				<td><code><a href="http://www.w3.org/TR/DOM-Level-3-Events/#events-UIEvent">UIEvent</a></code> (see [[!DOM-LEVEL-3-EVENTS]])</td>
 41.1645  			</tr>
 41.1646  			<tr class="assert must"><th>Sync / Async</th> <td>Async</td></tr>
 41.1647  			<tr class="assert must"><th>Bubbles</th> <td>No</td></tr>
 41.1648 -			<tr class="assert must"><th>Target</th> 
 41.1649 +			<tr class="assert must"><th>Target</th>
 41.1650  				<td><a idl>NamedFlow</a></td>
 41.1651  			</tr>
 41.1652  			<tr class="assert must"><th>Cancelable</th> <td>Yes</td></tr>
 41.1653 @@ -1408,7 +1409,7 @@
 41.1654  			<tr class="assert must"><th>Context info</th>
 41.1655  				<td>
 41.1656  					<ul>
 41.1657 -						<li><code class="attribute-name">Event.target</code>: 
 41.1658 +						<li><code class="attribute-name">Event.target</code>:
 41.1659  							<a idl>NamedFlow</a> whose <a>region chain</a> has regionOverset values that have changed.
 41.1660  						</li>
 41.1661  					</ul>
 41.1662 @@ -1423,87 +1424,87 @@
 41.1663  <h4 id="cssomview-getclientrects-and-getboundingclientrect">
 41.1664  <code class="idl">getClientRects()</code> and <code>getBoundingClientRect()</code></h4>
 41.1665  
 41.1666 -	The <a href="http://www.w3.org/TR/cssom-view/">CSSOM View Module</a> 
 41.1667 -	defines how user agents compute 
 41.1668 -	the bounding client rectangle 
 41.1669 -	for an element (<code class="idl">getBoundingClientRect()</code>) 
 41.1670 +	The <a href="http://www.w3.org/TR/cssom-view/">CSSOM View Module</a>
 41.1671 +	defines how user agents compute
 41.1672 +	the bounding client rectangle
 41.1673 +	for an element (<code class="idl">getBoundingClientRect()</code>)
 41.1674  	and its generated boxes (<code class="idl">getClientRects()</code>).
 41.1675  
 41.1676 -	This definition applies to 
 41.1677 -	the (possibly) multiple boxes 
 41.1678 -	generated for an element in a named flow 
 41.1679 -	flowing through a <a>region chain</a>. 
 41.1680 -	The <code class="idl">getClientRects()</code> method 
 41.1681 -	returns the list of boxes generated 
 41.1682 -	for each of the element fragments 
 41.1683 -	laid out in different regions. 
 41.1684 -	The <code>getBoundingClientRect()</code> method 
 41.1685 -	operates as specified in the 
 41.1686 -	<a href="http://www.w3.org/TR/cssom-view/">CSSOM View Module</a> 
 41.1687 -	as well and is computed 
 41.1688 -	from the set of rectangles 
 41.1689 +	This definition applies to
 41.1690 +	the (possibly) multiple boxes
 41.1691 +	generated for an element in a named flow
 41.1692 +	flowing through a <a>region chain</a>.
 41.1693 +	The <code class="idl">getClientRects()</code> method
 41.1694 +	returns the list of boxes generated
 41.1695 +	for each of the element fragments
 41.1696 +	laid out in different regions.
 41.1697 +	The <code>getBoundingClientRect()</code> method
 41.1698 +	operates as specified in the
 41.1699 +	<a href="http://www.w3.org/TR/cssom-view/">CSSOM View Module</a>
 41.1700 +	as well and is computed
 41.1701 +	from the set of rectangles
 41.1702  	returned by <code class="idl">getClientRects()</code>.
 41.1703  
 41.1704  <h4 id="cssomview-offset-attributes">
 41.1705  <code class="idl">offsetTop</code>, <code class="idl">offsetLeft</code>,
 41.1706  <code class="idl">offsetWidth</code>, <code class="idl">offsetHeight</code> and <code class="idl">offsetParent</code></h4>
 41.1707  
 41.1708 -	The computation of the 
 41.1709 -	<a href="http://dev.w3.org/csswg/cssom-view/#extensions-to-the-htmlelement-interface">offset attributes</a> 
 41.1710 -	for elements laid out in a <a>named flow</a> follow the 
 41.1711 -	<a href="http://dev.w3.org/csswg/cssom-view/#extensions-to-the-htmlelement-interface">specification</a> 
 41.1712 -	[[!CSSOM]]. 
 41.1713 -	For the purpose of these algorithms, 
 41.1714 -	the <em>first CSS layout box</em> associated 
 41.1715 -	with an element laid out in a <a>named flow</a> 
 41.1716 -	is the first box generated for the first region the element is laid out into. 
 41.1717 -	In the offsetParent algorithm, 
 41.1718 -	the nearest ancestor search skips 
 41.1719 +	The computation of the
 41.1720 +	<a href="http://dev.w3.org/csswg/cssom-view/#extensions-to-the-htmlelement-interface">offset attributes</a>
 41.1721 +	for elements laid out in a <a>named flow</a> follow the
 41.1722 +	<a href="http://dev.w3.org/csswg/cssom-view/#extensions-to-the-htmlelement-interface">specification</a>
 41.1723 +	[[!CSSOM]].
 41.1724 +	For the purpose of these algorithms,
 41.1725 +	the <em>first CSS layout box</em> associated
 41.1726 +	with an element laid out in a <a>named flow</a>
 41.1727 +	is the first box generated for the first region the element is laid out into.
 41.1728 +	In the offsetParent algorithm,
 41.1729 +	the nearest ancestor search skips
 41.1730  	from the topmost named flow elements directly to the body element.
 41.1731  
 41.1732  <h2 id="multi-column-regions">
 41.1733  Multi-column regions</h2>
 41.1734  
 41.1735 -	A 
 41.1736 -	<a href="http://dev.w3.org/csswg/css3-multicol/#multi-column-element">multi-column</a> 
 41.1737 +	A
 41.1738 +	<a href="http://dev.w3.org/csswg/css3-multicol/#multi-column-element">multi-column</a>
 41.1739  	[[CSS3COL]]
 41.1740 -	element can be 
 41.1741 -	assigned to a <a>region chain</a>. 
 41.1742 -	The element becomes part 
 41.1743 -	of the <a>region chain</a> 
 41.1744 -	for the associated <a>named flow</a>, 
 41.1745 -	and flows its content fragments 
 41.1746 -	through columns according to 
 41.1747 -	the multi-column specification 
 41.1748 -	[[!CSS3COL]]. 
 41.1749 -	In particular, 
 41.1750 -	when computing the 
 41.1751 -	<a href="#rfcb-flow-fragment-height-resolution">flow fragment height</a> 
 41.1752 -	of a multi-column element 
 41.1753 -	that is associated with a <em><a>named flow</a></em>, 
 41.1754 +	element can be
 41.1755 +	assigned to a <a>region chain</a>.
 41.1756 +	The element becomes part
 41.1757 +	of the <a>region chain</a>
 41.1758 +	for the associated <a>named flow</a>,
 41.1759 +	and flows its content fragments
 41.1760 +	through columns according to
 41.1761 +	the multi-column specification
 41.1762 +	[[!CSS3COL]].
 41.1763 +	In particular,
 41.1764 +	when computing the
 41.1765 +	<a href="#rfcb-flow-fragment-height-resolution">flow fragment height</a>
 41.1766 +	of a multi-column element
 41.1767 +	that is associated with a <em><a>named flow</a></em>,
 41.1768  	the 'column-fill'
 41.1769  	[[!CSS3COL]]
 41.1770 -	property is honored 
 41.1771 -	to balance the fragments of content 
 41.1772 -	that would flow through 
 41.1773 +	property is honored
 41.1774 +	to balance the fragments of content
 41.1775 +	that would flow through
 41.1776  	its columns.
 41.1777  
 41.1778 -	Overflow of multicol regions 
 41.1779 -	is mostly handled 
 41.1780 -	according to the same rules 
 41.1781 -	as other <a>CSS Regions</a>. 
 41.1782 -	If the remainder of the named flow 
 41.1783 -	does not fit 
 41.1784 -	in the multicol region, 
 41.1785 -	then the rest 
 41.1786 -	of the content flows into 
 41.1787 -	the remaining <a>region chain</a>. 
 41.1788 -	However, 
 41.1789 -	if a multicol region 
 41.1790 -	is the last region 
 41.1791 -	in a <a>region chain</a>, 
 41.1792 -	then the multicol region must follow the 
 41.1793 -	<a href="http://dev.w3.org/csswg/css3-multicol/#overflow-columns">overflow column rules</a> 
 41.1794 +	Overflow of multicol regions
 41.1795 +	is mostly handled
 41.1796 +	according to the same rules
 41.1797 +	as other <a>CSS Regions</a>.
 41.1798 +	If the remainder of the named flow
 41.1799 +	does not fit
 41.1800 +	in the multicol region,
 41.1801 +	then the rest
 41.1802 +	of the content flows into
 41.1803 +	the remaining <a>region chain</a>.
 41.1804 +	However,
 41.1805 +	if a multicol region
 41.1806 +	is the last region
 41.1807 +	in a <a>region chain</a>,
 41.1808 +	then the multicol region must follow the
 41.1809 +	<a href="http://dev.w3.org/csswg/css3-multicol/#overflow-columns">overflow column rules</a>
 41.1810  	[[!CSS3COL]].
 41.1811  
 41.1812  	<div class="example">
 41.1813 @@ -1520,7 +1521,7 @@
 41.1814  					column-count: 2;
 41.1815  					flow-from: article;
 41.1816  					height: 6em;
 41.1817 -					column-gap: 1em; 
 41.1818 +					column-gap: 1em;
 41.1819  			}
 41.1820  
 41.1821  			#remainder {
 41.1822 @@ -1575,19 +1576,19 @@
 41.1823  <h2 id="pseudo_elements">
 41.1824  Pseudo-elements</h2>
 41.1825  
 41.1826 -	It can be useful 
 41.1827 -	to visually mark the content 
 41.1828 -	to highlight that a content thread 
 41.1829 -	is flowing through the <a>region chain</a>. 
 41.1830 -	For example, a marker 
 41.1831 -	such as <em>'continued below'</em> clearly indicates, 
 41.1832 -	at the end of a <a>CSS Region</a>, 
 41.1833 -	that there is more content in the flow 
 41.1834 -	which can be found by scrolling past 
 41.1835 +	It can be useful
 41.1836 +	to visually mark the content
 41.1837 +	to highlight that a content thread
 41.1838 +	is flowing through the <a>region chain</a>.
 41.1839 +	For example, a marker
 41.1840 +	such as <em>'continued below'</em> clearly indicates,
 41.1841 +	at the end of a <a>CSS Region</a>,
 41.1842 +	that there is more content in the flow
 41.1843 +	which can be found by scrolling past
 41.1844  	whatever content interrupts the <a>region chain</a>.
 41.1845  
 41.1846 -	The '::before' and '::after' pseudo-elements (see [[!SELECT]]) 
 41.1847 -	let content authors mark the beginning 
 41.1848 +	The '::before' and '::after' pseudo-elements (see [[!SELECT]])
 41.1849 +	let content authors mark the beginning
 41.1850  	and end of a region with such markers.
 41.1851  
 41.1852  <h2 id="regions-visual-formatting-details">
 41.1853 @@ -1595,39 +1596,39 @@
 41.1854  
 41.1855  	Regions are laid out by CSS and take part in the normal box model and other layout models
 41.1856  	offered by CSS modules such as flexible boxes ([[CSS3-FLEXBOX]]). However, <span>regions</span>
 41.1857 -	lay out a fragment of their <a>named flow</a> instead of laying out descendant content as happens with other 
 41.1858 +	lay out a fragment of their <a>named flow</a> instead of laying out descendant content as happens with other
 41.1859  	boxes.
 41.1860  
 41.1861 -	This section describes the model for laying out <span>regions</span> 
 41.1862 -	and for laying out <a>named flow</a> content into regions. 
 41.1863 -	The descriptions in this section are biased towards a horizontal writing mode, 
 41.1864 -	using ''width'' for logical width (or measure) 
 41.1865 -	and ''height'' for logical height (or extent) 
 41.1866 -	as <a href="http://www.w3.org/TR/css3-writing-modes/#abstract-dimensions">defined</a> 
 41.1867 -	in the CSS Writing Modes Module [[!CSS3-WRITING-MODES]]). 
 41.1868 -	To use this model in a vertical writing mode apply the principles 
 41.1869 -	<a href="http://www.w3.org/TR/css3-writing-modes/#vertical-layout">described</a> 
 41.1870 +	This section describes the model for laying out <span>regions</span>
 41.1871 +	and for laying out <a>named flow</a> content into regions.
 41.1872 +	The descriptions in this section are biased towards a horizontal writing mode,
 41.1873 +	using ''width'' for logical width (or measure)
 41.1874 +	and ''height'' for logical height (or extent)
 41.1875 +	as <a href="http://www.w3.org/TR/css3-writing-modes/#abstract-dimensions">defined</a>
 41.1876 +	in the CSS Writing Modes Module [[!CSS3-WRITING-MODES]]).
 41.1877 +	To use this model in a vertical writing mode apply the principles
 41.1878 +	<a href="http://www.w3.org/TR/css3-writing-modes/#vertical-layout">described</a>
 41.1879  	in that specification.
 41.1880  
 41.1881  <h3 id="processing-model">
 41.1882  Processing model</h3>
 41.1883  
 41.1884 -	The '::before' content is laid out 
 41.1885 -	in the region prior to 
 41.1886 +	The '::before' content is laid out
 41.1887 +	in the region prior to
 41.1888  	any other content coming from the flow.
 41.1889  
 41.1890 -	The '::after' content is laid out 
 41.1891 -	in the region after laying out 
 41.1892 -	the flow fragment content into the <span>RFCB</span>. 
 41.1893 -	Then, flow content is removed from the fragment 
 41.1894 -	to accommodate the '::after' content. 
 41.1895 -	Accommodating means that the '::after' content 
 41.1896 +	The '::after' content is laid out
 41.1897 +	in the region after laying out
 41.1898 +	the flow fragment content into the <span>RFCB</span>.
 41.1899 +	Then, flow content is removed from the fragment
 41.1900 +	to accommodate the '::after' content.
 41.1901 +	Accommodating means that the '::after' content
 41.1902  	is laid out without overflowing the region.
 41.1903  
 41.1904 -	If there is not enough room to accommodate 
 41.1905 -	the ::before content, 
 41.1906 -	the '::after' content after removing all flow fragment content, 
 41.1907 -	or a combination of the two, 
 41.1908 +	If there is not enough room to accommodate
 41.1909 +	the ::before content,
 41.1910 +	the '::after' content after removing all flow fragment content,
 41.1911 +	or a combination of the two,
 41.1912  	then the ::before and/or ::after content overflows that region.
 41.1913  
 41.1914  <h3 id="regions-flow-content-box">
 41.1915 @@ -1637,13 +1638,13 @@
 41.1916  
 41.1917  	<ul>
 41.1918  		<li>
 41.1919 -			The boxes generated by its <code>::before</code> and 
 41.1920 +			The boxes generated by its <code>::before</code> and
 41.1921  			<code>::after</code> pseudo-elements, if any.
 41.1922  		</li>
 41.1923  		<li>
 41.1924 -			The anonymous <dfn>region flow content box</dfn> 
 41.1925 -			(called <dfn>RFCB</dfn> in this document) 
 41.1926 -			which contains the fragment of the <a>named flow</a> 
 41.1927 +			The anonymous <dfn>region flow content box</dfn>
 41.1928 +			(called <dfn>RFCB</dfn> in this document)
 41.1929 +			which contains the fragment of the <a>named flow</a>
 41.1930  			that the region receives.
 41.1931  		</li>
 41.1932  	</ul>
 41.1933 @@ -1655,59 +1656,59 @@
 41.1934  		</figcaption>
 41.1935  	</figure>
 41.1936  
 41.1937 -	Laying out a <span>region</span> box follows the same processing rules 
 41.1938 +	Laying out a <span>region</span> box follows the same processing rules
 41.1939  	as for any other <a href="http://www.w3.org/TR/CSS2/visuren.html#block-boxes">block container box</a>.
 41.1940  
 41.1941 -	The <span>RFCB</span> is a 
 41.1942 -	<a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block container box</a> 
 41.1943 +	The <span>RFCB</span> is a
 41.1944 +	<a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block container box</a>
 41.1945  	with a computed 'width' of ''auto'' and whose used 'height' is resolved as detailed below.
 41.1946  
 41.1947 -	Since the <span>RFCB</span> is a <a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block container box</a>, the ::before box and ::after box will also be block containers, though the contents of ::before and ::after may be inline within those boxes. 
 41.1948 +	Since the <span>RFCB</span> is a <a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block container box</a>, the ::before box and ::after box will also be block containers, though the contents of ::before and ::after may be inline within those boxes.
 41.1949  
 41.1950  <h4 id="rfcb-width-resolution">
 41.1951  RFCB 'width' resolution</h4>
 41.1952  
 41.1953 -	At various points in the visual formatting of documents containing regions, 
 41.1954 -	the used 'width' of RFCBs and regions need to be resolved. 
 41.1955 -	In all cases, the resolution is done following the rules for 
 41.1956 -	<a href="http://www.w3.org/TR/CSS2/visudet.html#Computing_widths_and_margins">calculating widths and margins</a> (see [[!CSS21]]). 
 41.1957 -	Sometimes, resolving the used 'width' value requires 
 41.1958 -	measuring the content's <code>min-content</code> 
 41.1959 -	and <code>max-content</code> values 
 41.1960 -	(as <a href="http://www.w3.org/TR/css3-writing-modes/#orthogonal-auto">defined</a> 
 41.1961 -	in the CSS Writing Modes Module [[!CSS3-WRITING-MODES]]). 
 41.1962 -	or an RFCB, <strong>these measures are made 
 41.1963 +	At various points in the visual formatting of documents containing regions,
 41.1964 +	the used 'width' of RFCBs and regions need to be resolved.
 41.1965 +	In all cases, the resolution is done following the rules for
 41.1966 +	<a href="http://www.w3.org/TR/CSS2/visudet.html#Computing_widths_and_margins">calculating widths and margins</a> (see [[!CSS21]]).
 41.1967 +	Sometimes, resolving the used 'width' value requires
 41.1968 +	measuring the content's <code>min-content</code>
 41.1969 +	and <code>max-content</code> values
 41.1970 +	(as <a href="http://www.w3.org/TR/css3-writing-modes/#orthogonal-auto">defined</a>
 41.1971 +	in the CSS Writing Modes Module [[!CSS3-WRITING-MODES]]).
 41.1972 +	or an RFCB, <strong>these measures are made
 41.1973  	on the <em>entire</em> associated <a>named flow</a> content</strong>.
 41.1974  
 41.1975 -	As a consequence, 
 41.1976 -	all <span>RFCBs</span> of <span>regions</span> associated 
 41.1977 -	with a given <a>named flow</a> 
 41.1978 -	share the same <code>min-content</code> 
 41.1979 +	As a consequence,
 41.1980 +	all <span>RFCBs</span> of <span>regions</span> associated
 41.1981 +	with a given <a>named flow</a>
 41.1982 +	share the same <code>min-content</code>
 41.1983  	and <code>max-content</code> measures.
 41.1984  
 41.1985 -	This approach is consistent with the 
 41.1986 +	This approach is consistent with the
 41.1987  	<a href="http://www.w3.org/TR/css3-break/#varying-size-boxes">box model for breaking</a> ([[!CSS3-BREAK]]).
 41.1988  
 41.1989  
 41.1990  <h3 id="regions-visual-formatting-steps">
 41.1991  Regions visual formatting steps</h3>
 41.1992  
 41.1993 -	Formatting documents that contain <a>named flows</a> laid out in regions 
 41.1994 +	Formatting documents that contain <a>named flows</a> laid out in regions
 41.1995  	is a three-step process:
 41.1996  
 41.1997  	<ul>
 41.1998  		<li>
 41.1999 -			<em>Step 1: RFCB <dfn>flow fragment height</dfn> resolution</em>. 
 41.2000 +			<em>Step 1: RFCB <dfn>flow fragment height</dfn> resolution</em>.
 41.2001  			In this step, the heights of fragments fitting in the regions' RFCBs are resolved.
 41.2002  		</li>
 41.2003  		<li>
 41.2004 -			<em>Step 2: document and regions layout</em>. 
 41.2005 -			In this step, the document content and regions are laid out. 
 41.2006 +			<em>Step 2: document and regions layout</em>.
 41.2007 +			In this step, the document content and regions are laid out.
 41.2008  			However, <a>named flow</a> content is not laid out in regions yet.
 41.2009  		</li>
 41.2010  		<li>
 41.2011 -			<em>Step 3: <a>named flow</a> layout</em>. 
 41.2012 -			In this step, the content of <a>named flows</a> 
 41.2013 +			<em>Step 3: <a>named flow</a> layout</em>.
 41.2014 +			In this step, the content of <a>named flows</a>
 41.2015  			is laid out in their respective <a>region chains</a>.
 41.2016  		</li>
 41.2017  	</ul>
 41.2018 @@ -1727,40 +1728,40 @@
 41.2019  <h5 id="rfcb-flow-fragment-height-resolution-phase-1">
 41.2020  RFCB flow fragment height resolution, Phase 1</h5>
 41.2021  
 41.2022 -	The document is laid out with a 
 41.2023 +	The document is laid out with a
 41.2024  	<a href="http://www.w3.org/TR/CSS2/cascade.html#used-value">used</a> height of zero
 41.2025 -	for all <span>RFCB</span>s. In this phase, the content of <a>named flows</a> is not laid out in 
 41.2026 +	for all <span>RFCB</span>s. In this phase, the content of <a>named flows</a> is not laid out in
 41.2027  	<span>regions</span>. This phase yields resolved position and sizes for all regions and
 41.2028  	their RFCBs in the document.
 41.2029  
 41.2030  <h5 id="rfcb-flow-fragment-height-resolution-phase-2">
 41.2031  RFCB flow fragment height resolution, Phase 2</h5>
 41.2032  
 41.2033 -	<a>named flows</a> are laid out in <span>regions</span>. 
 41.2034 -	The user agent resolves 
 41.2035 -	the <em><span>flow fragment height</span></em> 
 41.2036 -	for the <span>RFCB</span>s 
 41.2037 -	using the remainder of the flow 
 41.2038 -	and accounting for <a href="http://www.w3.org/TR/css3-break/">fragmentation rules</a>. 
 41.2039 -	This process accounts for constraints 
 41.2040 -	such as the 'height' or 'max-height' values, 
 41.2041 -	as described in the CSS 2.1 section 
 41.2042 -	on <a href="http://www.w3.org/TR/CSS2/visudet.html#Computing_heights_and_margins">calculating heights and margins</a> 
 41.2043 -	(see the <a href="http://www.w3.org/TR/CSS2/visudet.html#normal-block">Block-level non-replaced elements in normal flow...</a> 
 41.2044 -	section and the <a href="http://www.w3.org/TR/CSS2/visudet.html#block-root-margin">complicated cases</a> section). 
 41.2045 -	During this phase, 
 41.2046 -	generated content is laid out 
 41.2047 -	according to the <a href="#processing-model">rules</a> 
 41.2048 +	<a>named flows</a> are laid out in <span>regions</span>.
 41.2049 +	The user agent resolves
 41.2050 +	the <em><span>flow fragment height</span></em>
 41.2051 +	for the <span>RFCB</span>s
 41.2052 +	using the remainder of the flow
 41.2053 +	and accounting for <a href="http://www.w3.org/TR/css3-break/">fragmentation rules</a>.
 41.2054 +	This process accounts for constraints
 41.2055 +	such as the 'height' or 'max-height' values,
 41.2056 +	as described in the CSS 2.1 section
 41.2057 +	on <a href="http://www.w3.org/TR/CSS2/visudet.html#Computing_heights_and_margins">calculating heights and margins</a>
 41.2058 +	(see the <a href="http://www.w3.org/TR/CSS2/visudet.html#normal-block">Block-level non-replaced elements in normal flow...</a>
 41.2059 +	section and the <a href="http://www.w3.org/TR/CSS2/visudet.html#block-root-margin">complicated cases</a> section).
 41.2060 +	During this phase,
 41.2061 +	generated content is laid out
 41.2062 +	according to the <a href="#processing-model">rules</a>
 41.2063  	described earlier in this document.
 41.2064  
 41.2065 -	In a <a>nested region context</a>, 
 41.2066 -	this phase will trigger 
 41.2067 -	the beginning of Step 1 
 41.2068 -	for any inner <a>named flows</a> 
 41.2069 -	whose regions are contained 
 41.2070 -	in the outer <a>named flow</a>. 
 41.2071 -	All of Step 1 for inner flows 
 41.2072 -	must recursively complete before Step 1 
 41.2073 +	In a <a>nested region context</a>,
 41.2074 +	this phase will trigger
 41.2075 +	the beginning of Step 1
 41.2076 +	for any inner <a>named flows</a>
 41.2077 +	whose regions are contained
 41.2078 +	in the outer <a>named flow</a>.
 41.2079 +	All of Step 1 for inner flows
 41.2080 +	must recursively complete before Step 1
 41.2081  	for an outer flow completes.
 41.2082  
 41.2083  <h4 id="regions-boxes-layout">
 41.2084 @@ -1768,78 +1769,78 @@
 41.2085  
 41.2086  	In this step, the document is laid out according to the normal CSS layout rules.
 41.2087  
 41.2088 -	If a measure of the content is required to resolve the used 'width' of the region box, 
 41.2089 -	the value is resolved as described in the 
 41.2090 +	If a measure of the content is required to resolve the used 'width' of the region box,
 41.2091 +	the value is resolved as described in the
 41.2092  	<a href="#rfcb-width-resolution">RFCB width resolution</a> section.
 41.2093  
 41.2094 -	If a measure of the content is required to resolve the used height of the RFCB 
 41.2095 -	(for example if the region box is absolutely positioned), 
 41.2096 -	the <span>flow fragment height</span> resolved in Step 1 is used 
 41.2097 +	If a measure of the content is required to resolve the used height of the RFCB
 41.2098 +	(for example if the region box is absolutely positioned),
 41.2099 +	the <span>flow fragment height</span> resolved in Step 1 is used
 41.2100  	for the vertical content measure of the RFCB.
 41.2101  
 41.2102 -	At the end of this step, 
 41.2103 -	regions are laid out and ready to receive content 
 41.2104 +	At the end of this step,
 41.2105 +	regions are laid out and ready to receive content
 41.2106  	from their associated <a>named flows</a>.
 41.2107  
 41.2108  <h4 id="named-flows-layout">
 41.2109  Step 3: named flows layout</h4>
 41.2110  
 41.2111 -	In this final step, 
 41.2112 -	the content of <a>named flows</a> 
 41.2113 -	is laid out in the <span>regions</span>' RFCBs 
 41.2114 +	In this final step,
 41.2115 +	the content of <a>named flows</a>
 41.2116 +	is laid out in the <span>regions</span>' RFCBs
 41.2117  	along with the generated content boxes.
 41.2118  
 41.2119 -	The used 'width' for RFCBs is resolved 
 41.2120 +	The used 'width' for RFCBs is resolved
 41.2121  	<a href="#rfcb-width-resolution">as described before</a>.
 41.2122  
 41.2123 -	The used 'height' of RFCBs is resolved 
 41.2124 -	such that none of the boxes 
 41.2125 -	in the region box's normal flow 
 41.2126 -	overflow the region's box. 
 41.2127 -	In other words, 
 41.2128 -	the RFCB boxes are stretched vertically 
 41.2129 -	to accommodate as much 
 41.2130 -	of the flow as possible 
 41.2131 -	without overflowing the region box 
 41.2132 -	and accounting for 
 41.2133 -	<a href="http://www.w3.org/TR/css3-break/">fragmentation rules</a> 
 41.2134 +	The used 'height' of RFCBs is resolved
 41.2135 +	such that none of the boxes
 41.2136 +	in the region box's normal flow
 41.2137 +	overflow the region's box.
 41.2138 +	In other words,
 41.2139 +	the RFCB boxes are stretched vertically
 41.2140 +	to accommodate as much
 41.2141 +	of the flow as possible
 41.2142 +	without overflowing the region box
 41.2143 +	and accounting for
 41.2144 +	<a href="http://www.w3.org/TR/css3-break/">fragmentation rules</a>
 41.2145  	and generated content boxes.
 41.2146  
 41.2147 -	During this phase, 
 41.2148 -	generated content is laid out 
 41.2149 -	according to the <a href="#processing-model">rules</a> 
 41.2150 +	During this phase,
 41.2151 +	generated content is laid out
 41.2152 +	according to the <a href="#processing-model">rules</a>
 41.2153  	described earlier in this document.
 41.2154  
 41.2155 -	In a <a>nested region context</a>, 
 41.2156 +	In a <a>nested region context</a>,
 41.2157  	this step will trigger Step 2
 41.2158 -	for inner <a>named flows</a> 
 41.2159 -	whose regions are contained 
 41.2160 -	in the outer <a>named flow</a>. 
 41.2161 -	Fragmentation of the inner regions 
 41.2162 -	may result as they are laid out 
 41.2163 +	for inner <a>named flows</a>
 41.2164 +	whose regions are contained
 41.2165 +	in the outer <a>named flow</a>.
 41.2166 +	Fragmentation of the inner regions
 41.2167 +	may result as they are laid out
 41.2168  	in the outer <a>region chain</a>.
 41.2169 -	Once Step 3 for an outer named flow is complete, 
 41.2170 +	Once Step 3 for an outer named flow is complete,
 41.2171  	Step 3 for the inner <a>named flows</a> recursively begins.
 41.2172  
 41.2173 -	Once Step 3 for a named flow is complete, 
 41.2174 -	The conditions for the 
 41.2175 -	<a href="#named-flow-events">named flow events</a> are checked, 
 41.2176 -	and if the triggers are met 
 41.2177 +	Once Step 3 for a named flow is complete,
 41.2178 +	The conditions for the
 41.2179 +	<a href="#named-flow-events">named flow events</a> are checked,
 41.2180 +	and if the triggers are met
 41.2181  	the events dispatch at this point.
 41.2182  
 41.2183  	<div class="note"><span class="note-prefix">Note </span>
 41.2184  
 41.2185 -		The model for resolving auto sized regions will cause, 
 41.2186 -		under certain circumstances, 
 41.2187 -		the flow content to be overset or underset. 
 41.2188 -		In other words, 
 41.2189 -		it will not fit tightly. 
 41.2190 -		The model prevents having circular dependencies 
 41.2191 -		in the layout model. 
 41.2192 -		Implementations may decide to apply 
 41.2193 -		further layout steps 
 41.2194 -		to ensure that the whole flow content 
 41.2195 -		is displayed to the user, 
 41.2196 +		The model for resolving auto sized regions will cause,
 41.2197 +		under certain circumstances,
 41.2198 +		the flow content to be overset or underset.
 41.2199 +		In other words,
 41.2200 +		it will not fit tightly.
 41.2201 +		The model prevents having circular dependencies
 41.2202 +		in the layout model.
 41.2203 +		Implementations may decide to apply
 41.2204 +		further layout steps
 41.2205 +		to ensure that the whole flow content
 41.2206 +		is displayed to the user,
 41.2207  		even in edge cases.
 41.2208  	</div>
 41.2209  
 41.2210 @@ -1848,7 +1849,7 @@
 41.2211  
 41.2212  	The process for resolving an RFCB's 'height' and the three-step process used to
 41.2213  	lay out documents containing regions and <a>named flows</a> are
 41.2214 -	<em>conceptual</em> descriptions of what the layout 
 41.2215 +	<em>conceptual</em> descriptions of what the layout
 41.2216  	should yield and implementations should optimize to reduce the number of
 41.2217  	steps and phases necessary wherever possible.
 41.2218  
 41.2219 @@ -1913,31 +1914,31 @@
 41.2220  		</pre>
 41.2221  	</div>
 41.2222  
 41.2223 -	The following sections and figures illustrate the intermediate results 
 41.2224 -	for the visual formatting process. 
 41.2225 -	In the following, we call RFCB-A, RFCB-B and RFCB-C 
 41.2226 +	The following sections and figures illustrate the intermediate results
 41.2227 +	for the visual formatting process.
 41.2228 +	In the following, we call RFCB-A, RFCB-B and RFCB-C
 41.2229  	the <span>RFCBs</span> for regions rA, rB and rC respectively.
 41.2230  
 41.2231  <h4 id="step1-phase1-example">
 41.2232  Step 1 - Phase 1: Laying out RFCBs with used height of zero</h4>
 41.2233  
 41.2234 -	Applying the rules for Step 1, Phase 1, 
 41.2235 -	the computed ''auto'' 'width' values for the RFCBs are resolved 
 41.2236 -	to used values according to the normal 
 41.2237 -	<a href="http://www.w3.org/TR/CSS2/visudet.html#Computing_widths_and_margins">CSS layout rules</a> 
 41.2238 -	meaning they stretch to the width 
 41.2239 +	Applying the rules for Step 1, Phase 1,
 41.2240 +	the computed ''auto'' 'width' values for the RFCBs are resolved
 41.2241 +	to used values according to the normal
 41.2242 +	<a href="http://www.w3.org/TR/CSS2/visudet.html#Computing_widths_and_margins">CSS layout rules</a>
 41.2243 +	meaning they stretch to the width
 41.2244  	of their containing block's content box.
 41.2245  
 41.2246  	<ol>
 41.2247  		<li>RFCB-A: stretches to fit the rA content box.
 41.2248 -			<p>Since rA also has an ''auto'' 'width', its own used 'width' is stretched to fit the 
 41.2249 +			<p>Since rA also has an ''auto'' 'width', its own used 'width' is stretched to fit the
 41.2250  			<code>&lt;body&gt;</code> content box.</p>
 41.2251  		</li>
 41.2252  		<li>RFCB-B: stretches to fit the <code>rB</code> content box.</li>
 41.2253  		<li>RFCB-C: stretches to fit the <code>rC</code> content box.</li>
 41.2254  	</ol>
 41.2255  
 41.2256 -	Also applying the rules for Step 1, Phase 1, 
 41.2257 +	Also applying the rules for Step 1, Phase 1,
 41.2258  	the used values for the RFCBs 'height' properties are all zero.
 41.2259  
 41.2260  	Conceptually, this produces the layout illustrated below.
 41.2261 @@ -1952,31 +1953,31 @@
 41.2262  <h4 id="step1-phase2-example">
 41.2263  Step 1 - Phase 2: Layout flow to compute the RFCBs' flow fragments heights</h4>
 41.2264  
 41.2265 -	In this second phase of Step 1, 
 41.2266 -	the named flow is laid out in <span>regions</span> 
 41.2267 +	In this second phase of Step 1,
 41.2268 +	the named flow is laid out in <span>regions</span>
 41.2269  	and the height of each fragment falling in each RFCB is computed.
 41.2270  
 41.2271 -	The user agent lays out as much 
 41.2272 -	of the flow into an area with RFCB-A's used 'width'. 
 41.2273 -	rA's 'height' computes to ''auto'' 
 41.2274 -	and there is no vertical maximum height for RFCA's 'height'. 
 41.2275 -	However, because there is a break after the first paragraph 
 41.2276 +	The user agent lays out as much
 41.2277 +	of the flow into an area with RFCB-A's used 'width'.
 41.2278 +	rA's 'height' computes to ''auto''
 41.2279 +	and there is no vertical maximum height for RFCA's 'height'.
 41.2280 +	However, because there is a break after the first paragraph
 41.2281  	in the "article" <code>named flow</code>,
 41.2282 -	only this first paragraph is laid out 
 41.2283 -	in RFCB-A and FH-A (the flow fragment height for RFCB-A) 
 41.2284 +	only this first paragraph is laid out
 41.2285 +	in RFCB-A and FH-A (the flow fragment height for RFCB-A)
 41.2286  	is resolved by laying out this first paragraph in the used 'width'.
 41.2287  
 41.2288 -	At this point, the user agent lays out as much 
 41.2289 -	of the remaining flow as possible in RFCB-B. 
 41.2290 -	Because rB's 'max-height' computed value is "150px", 
 41.2291 -	the user agent only lays out the "article" named flow 
 41.2292 -	using RFCB-B's used 'width' until the point where 
 41.2293 -	laying out additional content would cause RFCB-B to overflow rB's box. 
 41.2294 +	At this point, the user agent lays out as much
 41.2295 +	of the remaining flow as possible in RFCB-B.
 41.2296 +	Because rB's 'max-height' computed value is "150px",
 41.2297 +	the user agent only lays out the "article" named flow
 41.2298 +	using RFCB-B's used 'width' until the point where
 41.2299 +	laying out additional content would cause RFCB-B to overflow rB's box.
 41.2300  	The fragment height for RFCB-B is resolved: FH-B (<code>150px</code>).
 41.2301  
 41.2302 -	Finally, the user agent lays out the remainder of the flow in RFCB-C. 
 41.2303 -	Because rC has no other constraints and no region breaks, 
 41.2304 -	the remaining content is laid out in RFCB-C's used 'width'. 
 41.2305 +	Finally, the user agent lays out the remainder of the flow in RFCB-C.
 41.2306 +	Because rC has no other constraints and no region breaks,
 41.2307 +	the remaining content is laid out in RFCB-C's used 'width'.
 41.2308  	This results in a resolved flow fragment height: FH-C.
 41.2309  
 41.2310  	<figure>
 41.2311 @@ -1989,26 +1990,26 @@
 41.2312  <h4 id="step2-example">
 41.2313  Step 2: Layout document and regions without named flows</h4>
 41.2314  
 41.2315 -	The used 'width' of RFCB-A, RFCB-B and RFCB-C 
 41.2316 -	are resolved as in the previous step. 
 41.2317 +	The used 'width' of RFCB-A, RFCB-B and RFCB-C
 41.2318 +	are resolved as in the previous step.
 41.2319  	However, the 'height' is resolved differently.
 41.2320  
 41.2321 -	Resolving the 'height' of rA 
 41.2322 -	<a href="http://www.w3.org/TR/CSS2/visudet.html#normal-block">requires a content measure</a> 
 41.2323 +	Resolving the 'height' of rA
 41.2324 +	<a href="http://www.w3.org/TR/CSS2/visudet.html#normal-block">requires a content measure</a>
 41.2325  	which is FH-A (the flow fragment height for RFCB-A).
 41.2326  
 41.2327 -	The 'height' of rB results from first computing its 
 41.2328 -	<a href="http://www.w3.org/TR/CSS2/visudet.html#block-root-margin">content measure</a> 
 41.2329 -	and then applying the 
 41.2330 -	<a href="http://www.w3.org/TR/CSS2/visudet.html#min-max-heights">rules for max-height</a>. 
 41.2331 -	Here, the vertical content measure evaluates to FH-B. 
 41.2332 -	After applying the rules for 'max-height' 
 41.2333 -	and accounting for margins, padding and borders, 
 41.2334 -	the used 'height' of rB is resolved to LH-B 
 41.2335 +	The 'height' of rB results from first computing its
 41.2336 +	<a href="http://www.w3.org/TR/CSS2/visudet.html#block-root-margin">content measure</a>
 41.2337 +	and then applying the
 41.2338 +	<a href="http://www.w3.org/TR/CSS2/visudet.html#min-max-heights">rules for max-height</a>.
 41.2339 +	Here, the vertical content measure evaluates to FH-B.
 41.2340 +	After applying the rules for 'max-height'
 41.2341 +	and accounting for margins, padding and borders,
 41.2342 +	the used 'height' of rB is resolved to LH-B
 41.2343  	(<code>150px</code>).
 41.2344  
 41.2345 -	The 'height' of rC's box results from 
 41.2346 -	<a href="http://www.w3.org/TR/CSS2/visudet.html#block-root-margin">calculating its content measure</a>: 
 41.2347 +	The 'height' of rC's box results from
 41.2348 +	<a href="http://www.w3.org/TR/CSS2/visudet.html#block-root-margin">calculating its content measure</a>:
 41.2349  	FH-C becomes rC's used 'height'.
 41.2350  
 41.2351  	<figure>
 41.2352 @@ -2021,25 +2022,25 @@
 41.2353  <h4 id="step3-example">
 41.2354  Step 3: named flows layout</h4>
 41.2355  
 41.2356 -	In this final step, 
 41.2357 -	the <code>article</code> <a>named flow</a> 
 41.2358 -	is laid out in its <a>region chain</a>. 
 41.2359 -	The used 'width' for each of the RFCB 
 41.2360 +	In this final step,
 41.2361 +	the <code>article</code> <a>named flow</a>
 41.2362 +	is laid out in its <a>region chain</a>.
 41.2363 +	The used 'width' for each of the RFCB
 41.2364  	is resolved as in step 1 above.
 41.2365  
 41.2366 -	The used 'height' for the RFCB is a result 
 41.2367 -	of laying out the as much of the content 
 41.2368 -	in the <span>region</span> without overflowing its content box 
 41.2369 +	The used 'height' for the RFCB is a result
 41.2370 +	of laying out the as much of the content
 41.2371 +	in the <span>region</span> without overflowing its content box
 41.2372  	and following the <a href="http://www.w3.org/TR/css3-break/">fragmentation rules</a>.
 41.2373  
 41.2374 -	Because the computed 'width' of the RFCB has not changed 
 41.2375 -	and the fragmentation rules applied are the same as in Phase 1, Step 2, 
 41.2376 -	the used 'height' for RFCB-A, RFCB-B and RFCB-C 
 41.2377 +	Because the computed 'width' of the RFCB has not changed
 41.2378 +	and the fragmentation rules applied are the same as in Phase 1, Step 2,
 41.2379 +	the used 'height' for RFCB-A, RFCB-B and RFCB-C
 41.2380  	are LH-A, LH-B and LH-C, respectively.
 41.2381  
 41.2382 -	There may be situations where the used 'height' 
 41.2383 -	of RFCBs resolved in Step 3 are different 
 41.2384 -	from the <span>flow fragment height</span> 
 41.2385 +	There may be situations where the used 'height'
 41.2386 +	of RFCBs resolved in Step 3 are different
 41.2387 +	from the <span>flow fragment height</span>
 41.2388  	computed in Step 1 Phase 2.
 41.2389  
 41.2390  	<figure>
 41.2391 @@ -2052,69 +2053,69 @@
 41.2392  <h2 id="relation-to-document-events">
 41.2393  Relation to document events</h2>
 41.2394  
 41.2395 -	The CSS Regions module does not alter 
 41.2396 -	the normal processing of events 
 41.2397 -	in the document tree. 
 41.2398 -	In particular, 
 41.2399 -	if an event occurs on an element 
 41.2400 -	that is part of a <a>named flow</a>, 
 41.2401 -	the <a href= "http://www.w3.org/TR/dom/#events">event's bubble and capture phases</a> 
 41.2402 +	The CSS Regions module does not alter
 41.2403 +	the normal processing of events
 41.2404 +	in the document tree.
 41.2405 +	In particular,
 41.2406 +	if an event occurs on an element
 41.2407 +	that is part of a <a>named flow</a>,
 41.2408 +	the <a href= "http://www.w3.org/TR/dom/#events">event's bubble and capture phases</a>
 41.2409  	happen following the document tree order.
 41.2410  
 41.2411  	<div class="note"><span class="note-prefix">Note </span>
 41.2412  
 41.2413 -		This means that in most cases 
 41.2414 -		<a>CSS Regions</a> 
 41.2415 +		This means that in most cases
 41.2416 +		<a>CSS Regions</a>
 41.2417  		will not receive user events
 41.2418 -		that trigger on their named flow content. 
 41.2419 -		Event handlers for named flow content can check 
 41.2420 -		<code><a href="http://dev.w3.org/csswg/cssom-view/#extensions-to-the-document-interface">getElementsFromPoint()</a></code> [[CSSOM-VIEW]] 
 41.2421 -		to find the <a>CSS Region</a> 
 41.2422 -		where the user event occurred. 
 41.2423 -		Future versions of CSS-UI may provide 
 41.2424 -		a more general solution for user event bubbling 
 41.2425 -		where the stack of elements 
 41.2426 -		at the event coordinates 
 41.2427 +		that trigger on their named flow content.
 41.2428 +		Event handlers for named flow content can check
 41.2429 +		<code><a href="http://dev.w3.org/csswg/cssom-view/#extensions-to-the-document-interface">getElementsFromPoint()</a></code> [[CSSOM-VIEW]]
 41.2430 +		to find the <a>CSS Region</a>
 41.2431 +		where the user event occurred.
 41.2432 +		Future versions of CSS-UI may provide
 41.2433 +		a more general solution for user event bubbling
 41.2434 +		where the stack of elements
 41.2435 +		at the event coordinates
 41.2436  
 41.2437  	</div>
 41.2438  
 41.2439  <h2 id="relation-to-other-specifications">
 41.2440  Relation to other specifications</h2>
 41.2441  
 41.2442 -	This specification is related to other specifications 
 41.2443 -	as described in the references section. 
 41.2444 +	This specification is related to other specifications
 41.2445 +	as described in the references section.
 41.2446  	In addition, it is related to the following specifications:
 41.2447  
 41.2448  	<ol>
 41.2449  		<li>
 41.2450 -			CSS Fragmentation Module Level 3 [[CSS3-BREAK]]. 
 41.2451 -			This module defines the rules for fragmenting content over multiple containers 
 41.2452 -			and applies to <a>CSS Regions</a> 
 41.2453 +			CSS Fragmentation Module Level 3 [[CSS3-BREAK]].
 41.2454 +			This module defines the rules for fragmenting content over multiple containers
 41.2455 +			and applies to <a>CSS Regions</a>
 41.2456  			in addition to applying to multi-column and paged media.
 41.2457  		</li>
 41.2458  
 41.2459  		<li>
 41.2460 -			CSS Pagination Templates Module Level 3 [[CSS3-PAGE-TEMPLATE]]. 
 41.2461 -			This module defines a syntax to define layout templates 
 41.2462 -			which can be used when paginating content. 
 41.2463 +			CSS Pagination Templates Module Level 3 [[CSS3-PAGE-TEMPLATE]].
 41.2464 +			This module defines a syntax to define layout templates
 41.2465 +			which can be used when paginating content.
 41.2466  			The page templates use regions.
 41.2467  		</li>
 41.2468  
 41.2469  		<li>
 41.2470 -			CSS Exclusions Module [[CSS3-EXCLUSIONS]]. 
 41.2471 -			This module defines a generic way to define exclusions 
 41.2472 -			around which content can flow. 
 41.2473 -			This can be seen as an extension to CSS floats. 
 41.2474 -			In advanced layout designs, 
 41.2475 -			it is expected that the CSS Exclusions module 
 41.2476 +			CSS Exclusions Module [[CSS3-EXCLUSIONS]].
 41.2477 +			This module defines a generic way to define exclusions
 41.2478 +			around which content can flow.
 41.2479 +			This can be seen as an extension to CSS floats.
 41.2480 +			In advanced layout designs,
 41.2481 +			it is expected that the CSS Exclusions module
 41.2482  			will be commonly combined with the CSS Regions module.
 41.2483  		</li>
 41.2484  
 41.2485  		<li>
 41.2486 -			CSS Line Grid Module [[CSS3-LINE-GRID]]. 
 41.2487 -			This module defines a concept of line grid 
 41.2488 -			to align the position of lines in different elements. 
 41.2489 -			The line grid functionality is related and needed 
 41.2490 +			CSS Line Grid Module [[CSS3-LINE-GRID]].
 41.2491 +			This module defines a concept of line grid
 41.2492 +			to align the position of lines in different elements.
 41.2493 +			The line grid functionality is related and needed
 41.2494  			for aligning content flowing in separate regions.
 41.2495  		</li>
 41.2496  	</ol>
 41.2497 @@ -2122,8 +2123,8 @@
 41.2498  <h2 id="usecases">
 41.2499  Use Cases</h2>
 41.2500  
 41.2501 -	Use cases are described on 
 41.2502 -	<a href="http://wiki.csswg.org/spec/css3-regions/regions-use-cases">these</a> 
 41.2503 +	Use cases are described on
 41.2504 +	<a href="http://wiki.csswg.org/spec/css3-regions/regions-use-cases">these</a>
 41.2505  	<a href="http://wiki.csswg.org/spec/css3-regions/regions-print-use-cases">pages</a>.
 41.2506  
 41.2507  <h2 id="changes">
 41.2508 @@ -2144,7 +2145,7 @@
 41.2509  		<li>Removed region styling from this level</li>
 41.2510  		<li>Changed ::region() to ::region</li>
 41.2511  		<li>display:none elements do not become CSS Regions</li>
 41.2512 -		<li>Clarify accessibility interactions with flow-into</li> 
 41.2513 +		<li>Clarify accessibility interactions with flow-into</li>
 41.2514  		<li>Change NamedFlowCollection to NamedFlowMap</li>
 41.2515  		<li>Remove mention of run-in and clarify ::before and ::after block containers</li>
 41.2516  		<li>Removed custom element syntax from examples</li>
 41.2517 @@ -2200,52 +2201,52 @@
 41.2518  <h2 class="no-num" id="acknowledgments">
 41.2519  Acknowledgments</h2>
 41.2520  
 41.2521 -	The editors are grateful to the CSS working group 
 41.2522 +	The editors are grateful to the CSS working group
 41.2523  	for their feedback and help with the genesis of this specification.
 41.2524  
 41.2525 -	In addition, the editors would like to thank 
 41.2526 -	the following individuals for their contributions, 
 41.2527 -	either during the conception of CSS Regions 
 41.2528 +	In addition, the editors would like to thank
 41.2529 +	the following individuals for their contributions,
 41.2530 +	either during the conception of CSS Regions
 41.2531  	or during its development and specification review process:
 41.2532  
 41.2533 -	Erik Arvidsson, 
 41.2534 -	Tab Atkins, 
 41.2535 -	Catalin Badea, 
 41.2536 -	Mihai Balan, 
 41.2537 -	Andrei Bucur, 
 41.2538 -	Razvan Caliman, 
 41.2539 -	Alexandru Chiculita, 
 41.2540 -	Phil Cupp, 
 41.2541 -	Arron Eicholz, 
 41.2542 -	John Jansen, 
 41.2543 -	CJ Gammon, 
 41.2544 -	Dimitri Glazkov, 
 41.2545 -	Daniel Glazman, 
 41.2546 -	Arno Gourdol, 
 41.2547 -	Catalin Grigoroscuta, 
 41.2548 -	David Hyatt, 
 41.2549 -	Brian Heuston, 
 41.2550 -	Ian Hickson, 
 41.2551 -	Jonathan Hoersch, 
 41.2552 -	Michael Jolson, 
 41.2553 -	Brad Kemper, 
 41.2554 -	HÃ¥kon Wium Lie, 
 41.2555 -	Kang-Hao (Kenny) Lu, 
 41.2556 -	Mihai Maerean, 
 41.2557 -	Markus Mielke, 
 41.2558 -	Robert O'Callahan, 
 41.2559 -	Edward O'Connor, 
 41.2560 -	Mihnea Ovidenie, 
 41.2561 -	Virgil Palanciuc, 
 41.2562 -	Olga Popiv, 
 41.2563 -	Christoph Päper, 
 41.2564 -	Anton Prowse, 
 41.2565 -	Florian Rivoal, 
 41.2566 -	Peter Sorotokin, 
 41.2567 -	Elliott Sprehn, 
 41.2568 -	Radu Stavila, 
 41.2569 -	Christian Stockwell, 
 41.2570 -	Eugene Veselov, 
 41.2571 -	Boris Zbarsky,	
 41.2572 -	Stephen Zilles 
 41.2573 -	and the CSS Working Group members.
 41.2574 \ No newline at end of file
 41.2575 +	Erik Arvidsson,
 41.2576 +	Tab Atkins,
 41.2577 +	Catalin Badea,
 41.2578 +	Mihai Balan,
 41.2579 +	Andrei Bucur,
 41.2580 +	Razvan Caliman,
 41.2581 +	Alexandru Chiculita,
 41.2582 +	Phil Cupp,
 41.2583 +	Arron Eicholz,
 41.2584 +	John Jansen,
 41.2585 +	CJ Gammon,
 41.2586 +	Dimitri Glazkov,
 41.2587 +	Daniel Glazman,
 41.2588 +	Arno Gourdol,
 41.2589 +	Catalin Grigoroscuta,
 41.2590 +	David Hyatt,
 41.2591 +	Brian Heuston,
 41.2592 +	Ian Hickson,
 41.2593 +	Jonathan Hoersch,
 41.2594 +	Michael Jolson,
 41.2595 +	Brad Kemper,
 41.2596 +	HÃ¥kon Wium Lie,
 41.2597 +	Kang-Hao (Kenny) Lu,
 41.2598 +	Mihai Maerean,
 41.2599 +	Markus Mielke,
 41.2600 +	Robert O'Callahan,
 41.2601 +	Edward O'Connor,
 41.2602 +	Mihnea Ovidenie,
 41.2603 +	Virgil Palanciuc,
 41.2604 +	Olga Popiv,
 41.2605 +	Christoph Päper,
 41.2606 +	Anton Prowse,
 41.2607 +	Florian Rivoal,
 41.2608 +	Peter Sorotokin,
 41.2609 +	Elliott Sprehn,
 41.2610 +	Radu Stavila,
 41.2611 +	Christian Stockwell,
 41.2612 +	Eugene Veselov,
 41.2613 +	Boris Zbarsky,
 41.2614 +	Stephen Zilles
 41.2615 +	and the CSS Working Group members.