Mercurial > drafts / changeset

     1.1 --- a/css-overflow/Makefile	Tue Jan 27 15:44:28 2015 -0800
     1.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.3 @@ -1,46 +0,0 @@
     1.4 -# Calling the post-processor with file-upload. Assumes the username
     1.5 -# and password are in ~/.curl-w3.org (user = USER:PASS)
     1.6 -#
     1.7 -# To set a date other than today, use: make cdate=YYYYMMDD
     1.8 -#
     1.9 -# To set the status, modify one of the "this version" URLs:
    1.10 -# http://www.w3.org/TR/[YEAR]/CR-[SHORTNAME]-[CDATE]/
    1.11 -# Or set that URL to [VERSION] and call Make as: make status=CR
    1.12 -#
    1.13 -#
    1.14 -# Possible other options to add to the curl command below:
    1.15 -# -F ids=on
    1.16 -
    1.17 -cdate = $(shell date +%Y%m%d)
    1.18 -status = ED
    1.19 -
    1.20 -%.html: %.src.html
    1.21 -	@echo "Calling post-processor to generate $@..."
    1.22 -	@curl -F file=@$< -F group=CSS -F output=html -F method=file -s \
    1.23 -	-F date=$(cdate) -F status=$(status) \
    1.24 -	-K ~/.curl-w3.org https://www.w3.org/Style/Group/process.cgi >$@
    1.25 -%.err: %.src.html
    1.26 -	@echo "Calling post-processor to check $<..."
    1.27 -	@curl -F file=@$< -F group=CSS -F output=err -F method=file -s \
    1.28 -	-F date=$(cdate) -F status=$(status) \
    1.29 -	-K ~/.curl-w3.org https://www.w3.org/Style/Group/process.cgi >$@
    1.30 -
    1.31 -
    1.32 -
    1.33 -all: check Overview.html
    1.34 -	@echo Done.
    1.35 -
    1.36 -check: Overview.err
    1.37 -	@cat $<
    1.38 -	@if egrep -v '^(Warning:|\(Processed in .* seconds\)|No errors)' $<;\
    1.39 -	 then false; else true; fi
    1.40 -
    1.41 -
    1.42 -# A handy shortcut:
    1.43 -
    1.44 -clean:
    1.45 -	rm Overview.html
    1.46 -
    1.47 -
    1.48 -
    1.49 -.PHONY: check clean

     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/css-overflow/Overview.bs	Tue Jan 27 15:56:33 2015 -0800
     2.3 @@ -0,0 +1,1133 @@
     2.4 +<h1>CSS Overflow Module Level 3</h1>
     2.5 +<pre class="metadata">
     2.6 +Status: ED
     2.7 +ED: http://dev.w3.org/csswg/css-overflow/
     2.8 +Shortname: css-overflow
     2.9 +Group: csswg
    2.10 +Level: 1
    2.11 +TR: http://www.w3.org/TR/css-overflow-3/
    2.12 +Previous version: http://www.w3.org/TR/2013/WD-css-overflow-3-20130418/
    2.13 +Editor: L. David Baron, Mozilla, http://dbaron.org/
    2.14 +Abstract: This module contains the features of CSS relating to new mechanisms of overflow handling in visual media (e.g., screen or paper).  In interactive media, it describes features that allow the overflow from a fixed size container to be handled by pagination (displaying one page at a time).  It also describes features, applying to all visual media, that allow the contents of an element to be spread across multiple fragments, allowing the contents to flow across multiple regions or to have different styles for different fragments.
    2.15 +Status Text: The following features are at risk: &hellip;
    2.16 +!Change Log: <a href="https://dvcs.w3.org/hg/csswg/log/tip/css-overflow/Overview.bs">from 27 January 2015 to the present</a>
    2.17 +!Change Log: <a href="https://dvcs.w3.org/hg/csswg/log/tip/css-overflow/Overview.src.html">from 28 March 2013 to 27 January 2015</a>
    2.18 +!Change Log: <a href="https://dvcs.w3.org/hg/csswg/log/tip/css3-overflow/Overview.src.html">from 31 July 2012to 27 March 2013</a>
    2.19 +</pre>
    2.20 +<pre class="link-defaults">
    2.21 +spec:css-transforms-1; type:property; text:transform-style
    2.22 +</pre>
    2.23 +<!-- FIXME: the break-* link doesn't actually work! -->
    2.24 +<pre class="anchors">
    2.25 +url: http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style; type: property; text: overflow-style;
    2.26 +url: http://dev.w3.org/csswg/css-break/#breaking-controls; type: property; text: break-*;
    2.27 +url: http://dev.w3.org/csswg/css-multicol/#overflow-columns; type: dfn; text: overflow columns;
    2.28 +url: http://dev.w3.org/csswg/selectors-3/#subject; type: dfn; text: subject;
    2.29 +</pre>
    2.30 +	<style>
    2.31 +		table.source-demo-pair {
    2.32 +			width: 100%;
    2.33 +		}
    2.34 +
    2.35 +		.in-cards-demo {
    2.36 +			width: 13em;
    2.37 +			height: 8em;
    2.38 +
    2.39 +			padding: 4px;
    2.40 +			border: medium solid blue;
    2.41 +			margin: 6px;
    2.42 +
    2.43 +			font: medium/1.3 Times New Roman, Times, serif;
    2.44 +			white-space: nowrap;
    2.45 +		}
    2.46 +
    2.47 +		.bouncy-columns-demo {
    2.48 +			width: 6em;
    2.49 +			height: 10em;
    2.50 +			float: left;
    2.51 +			margin: 1em;
    2.52 +			font: medium/1.25 Times New Roman, Times, serif;
    2.53 +			white-space: nowrap;
    2.54 +		}
    2.55 +		.bouncy-columns-demo.one {
    2.56 +			background: aqua; color: black;
    2.57 +			transform: rotate(-3deg);
    2.58 +		}
    2.59 +		.bouncy-columns-demo.two {
    2.60 +			background: yellow; color: black;
    2.61 +			transform: rotate(3deg);
    2.62 +		}
    2.63 +
    2.64 +		.article-font-inherit-demo {
    2.65 +			font: 1em/1.25 Times New Roman, Times, serif;
    2.66 +			white-space: nowrap;
    2.67 +		}
    2.68 +		.article-font-inherit-demo.one {
    2.69 +			width: 12em;
    2.70 +			font-size: 1.5em;
    2.71 +			margin-bottom: 1em;
    2.72 +			height: 4em;
    2.73 +		}
    2.74 +		.article-font-inherit-demo.two {
    2.75 +			width: 11em;
    2.76 +			margin-left: 5em;
    2.77 +			margin-right: 2em;
    2.78 +		}
    2.79 +
    2.80 +		.dark-columns-demo {
    2.81 +			width: 6em;
    2.82 +			height: 10em;
    2.83 +			float: left;
    2.84 +			margin-right: 1em;
    2.85 +			font: medium/1.25 Times New Roman, Times, serif;
    2.86 +			white-space: nowrap;
    2.87 +		}
    2.88 +		.dark-columns-demo.one {
    2.89 +			background: aqua; color: black;
    2.90 +		}
    2.91 +		.dark-columns-demo.one :link {
    2.92 +			color: blue;
    2.93 +		}
    2.94 +		.dark-columns-demo.one :visited {
    2.95 +			color: purple;
    2.96 +		}
    2.97 +		.dark-columns-demo.two {
    2.98 +			background: navy; color: white;
    2.99 +		}
   2.100 +		.dark-columns-demo.two :link {
   2.101 +			color: aqua;
   2.102 +		}
   2.103 +		.dark-columns-demo.two :visited {
   2.104 +			color: fuchsia;
   2.105 +		}
   2.106 +
   2.107 +		.article-max-lines-demo {
   2.108 +			font: 1em/1.25 Times New Roman, Times, serif;
   2.109 +			white-space: nowrap;
   2.110 +		}
   2.111 +		.article-max-lines-demo.one::first-letter {
   2.112 +			font-size: 2em;
   2.113 +			line-height: 0.9;
   2.114 +		}
   2.115 +		.article-max-lines-demo.one {
   2.116 +			font-size: 1.5em;
   2.117 +			width: 16em;
   2.118 +		}
   2.119 +		.article-max-lines-demo.two {
   2.120 +			width: 11.5em;
   2.121 +			float: left; margin-right: 1em;
   2.122 +		}
   2.123 +		.article-max-lines-demo.three {
   2.124 +			width: 11.5em;
   2.125 +			float: left;
   2.126 +		}
   2.127 +	</style>
   2.128 +
   2.129 +	<p>
   2.130 +	</p>
   2.131 +
   2.132 +<h2 id="intro">
   2.133 +Introduction</h2>
   2.134 +
   2.135 +	<p>
   2.136 +		In CSS Level 1 [[CSS1]], placing more content than would fit
   2.137 +		inside an element with a specified size
   2.138 +		was generally an authoring error.
   2.139 +		Doing so caused the content to extend
   2.140 +		outside the bounds of the element,
   2.141 +		which would likely cause
   2.142 +		that content to overlap with other elements.
   2.143 +	</p>
   2.144 +
   2.145 +	<p>
   2.146 +		CSS Level 2 [[CSS21]] introduced the 'overflow' property,
   2.147 +		which allows authors to have overflow be handled by scrolling,
   2.148 +		which means it is no longer an authoring error.
   2.149 +		It also allows authors to specify
   2.150 +		that overflow is handled by clipping,
   2.151 +		which makes sense when the author's intent
   2.152 +		is that the content not be shown.
   2.153 +	</p>
   2.154 +
   2.155 +	<p>
   2.156 +		However, scrolling is not the only way
   2.157 +		to present large amounts of content,
   2.158 +		and may even not be the optimal way.
   2.159 +		After all, the codex replaced the scroll
   2.160 +		as the common format for large written works
   2.161 +		because of its advantages.
   2.162 +	</p>
   2.163 +
   2.164 +	<p>
   2.165 +		This specification introduces
   2.166 +		a mechanism for Web pages to specify
   2.167 +		that an element of a page should handle overflow
   2.168 +		through pagination rather than through scrolling.
   2.169 +	</p>
   2.170 +
   2.171 +	<p>
   2.172 +		This specification also extends the concept of overflow
   2.173 +		in another direction.
   2.174 +		Instead of requiring that authors specify a single area
   2.175 +		into which the content of an element must flow,
   2.176 +		this specification allows authors to specify multiple fragments,
   2.177 +		each with their own dimensions and styles,
   2.178 +		so that the content of the element can flow from one to the next,
   2.179 +		using as many as needed to place the content without overflowing.
   2.180 +	</p>
   2.181 +
   2.182 +	<p>
   2.183 +		In both of these cases, implementations must
   2.184 +		break the content in the block-progression dimension.
   2.185 +		Implementations must do this is described
   2.186 +		in the CSS Fragmentation Module [[!CSS3-BREAK]].
   2.187 +	</p>
   2.188 +
   2.189 +<h2 id="overflow-concepts">Types of overflow</h2>
   2.190 +
   2.191 +	<p>
   2.192 +		CSS uses the term <dfn>overflow</dfn> to describe
   2.193 +		the contents of a box
   2.194 +		that extend outside that one of that box's edges
   2.195 +		(i.e., its <i>content edge</i>, <i>padding edge</i>,
   2.196 +		<i>border edge</i>, or <i>margin edge</i>).
   2.197 +		The overflow might be described as the elements or features
   2.198 +		that cause this overflow,
   2.199 +		the non-rectangular region occupied by these features,
   2.200 +		or, more commonly,
   2.201 +		as the minimal rectangle that bounds that region.
   2.202 +		A box's overflow is computed based on the boxes and styles
   2.203 +		of the box and of all its descendants whose containing block chain
   2.204 +		<span class="issue">undefined term?</span>
   2.205 +		includes the box.
   2.206 +	</p>
   2.207 +
   2.208 +	<p>
   2.209 +		In most cases, any of these types of overflow
   2.210 +		can be computed for any box
   2.211 +		from the bounds and properties of that box,
   2.212 +		and from the overflow (of that type)
   2.213 +		of each of its children.
   2.214 +		However, this is not always the case; for example,
   2.215 +		when ''transform-style: preserve-3d'' [[CSS3-TRANSFORMS]] is used on
   2.216 +		some of the children, their descendants with
   2.217 +		''transform-style: preserve-3d'' must also be examined.
   2.218 +	</p>
   2.219 +
   2.220 +<h3 id="ink-overflow">Ink overflow</h3>
   2.221 +
   2.222 +	<p>
   2.223 +		The <dfn id="ink-overflow0">ink overflow</dfn> of a box
   2.224 +		is the part of that box and its contents that
   2.225 +		creates a visual effect outside of
   2.226 +		the box's border box.
   2.227 +	</p>
   2.228 +
   2.229 +	<p>
   2.230 +		Since some effects in CSS (for example, the blurs in
   2.231 +		'text-shadow' [[CSS3TEXT]] and 'box-shadow' [[CSS3BG]])
   2.232 +		do not define what visual extent they cover, the extent
   2.233 +		of the <a>ink overflow</a> is undefined.
   2.234 +	</p>
   2.235 +
   2.236 +	<p class="issue">
   2.237 +		Should we try to define it at all and just leave pieces undefined?
   2.238 +	</p>
   2.239 +
   2.240 +	<p>
   2.241 +		The <dfn>ink overflow region</dfn> is the non-rectangular region
   2.242 +		occupied by the <a>ink overflow</a>, and the
   2.243 +		<dfn>ink overflow rectangle</dfn> is
   2.244 +		the minimal rectangle whose axis is aligned to the box's axes
   2.245 +		and contains the <a>ink overflow region</a>.
   2.246 +		Note that the <a>ink overflow rectangle</a> is a rectangle
   2.247 +		in the box's coordinate system, but might be non-rectangular
   2.248 +		in other coordinate systems due to transforms [[CSS3-TRANSFORMS]].
   2.249 +	</p>
   2.250 +
   2.251 +<h3 id="scrollable-overflow">Scrollable overflow</h3>
   2.252 +
   2.253 +	<p>
   2.254 +		The <dfn id="scrollable-overflow0">scrollable overflow</dfn> of a box is the
   2.255 +		set of things extending outside of that box's padding edge
   2.256 +		for which a scrolling mechanism needs to be provided.
   2.257 +	</p>
   2.258 +
   2.259 +	<p class="issue">
   2.260 +		The following definition should be rewritten to use
   2.261 +		the concept of <a href="http://dev.w3.org/csswg/css-transforms/#3d-rendering-context">3D rendering context</a> [[!CSS3-TRANSFORMS]]
   2.262 +		and related terms,
   2.263 +		particularly once those concepts stabilize following changes
   2.264 +		proposed in the CSS WG meeting on the morning of 2014-01-28.
   2.265 +	</p>
   2.266 +
   2.267 +	<p>
   2.268 +		Given the following definitions
   2.269 +		<span class="issue">which belong in [[CSS3-TRANSFORMS]]</span>:
   2.270 +	</p>
   2.271 +
   2.272 +	<dl>
   2.273 +		<dt><dfn>3d-preserving child</dfn></dt>
   2.274 +		<dd>
   2.275 +			A child box B of a containing block C is a 3d-preserving
   2.276 +			child if it has ''transform-style: preserve-3d''
   2.277 +			and the user-agent is not required to flatten it
   2.278 +			based on the <a href="http://www.w3.org/TR/css3-transforms/#transform-style-property">requirements</a> in [[!CSS3-TRANSFORMS]].
   2.279 +		</dt>
   2.280 +		<dt><dfn>non-3d-preserving child</dfn></dt>
   2.281 +		<dd>
   2.282 +			A child C of a box P is a non-3d-preserving-child if
   2.283 +			it is not a <a>3d-preserving child</a>.
   2.284 +		</dd>
   2.285 +		<dt><dfn>3d-preserving descendant</dfn></dt>
   2.286 +		<dd>
   2.287 +			Box D is a 3d-preserving descendant of box A if A is
   2.288 +			an ancestor of D, and D and all of the boxes (if any)
   2.289 +			in the containing block chain from D to A
   2.290 +			are <a>3d-preserving child</a> boxes.
   2.291 +		</dd>
   2.292 +	</dl>
   2.293 +
   2.294 +	<p>The scrollable overflow of a box is the union of the following things,
   2.295 +	all adjusted for transforms <span class="issue">undefined concept!</span> into the box's coordinate space:</p>
   2.296 +
   2.297 +	<ul>
   2.298 +		<li>
   2.299 +			for the box and all of its <a>3d-preserving descendant</a> boxes:
   2.300 +			<ul>
   2.301 +				<li>the box's own padding edge (for the box itself) or border edge (for <a>3d-preserving descendant</a> boxes)</li>
   2.302 +				<li>the bounds <span class="issue">undefined term!</span> of any text directly in the box</li>
   2.303 +				<li><span class="issue">MORE HERE!</span>
   2.304 +			</ul>
   2.305 +		<li>
   2.306 +			for all the <a>non-3d-preserving child</a> boxes of the
   2.307 +			box and its <a>3d-preserving descendant</a> boxes,
   2.308 +			the scrollable overflow of the box
   2.309 +		</li>
   2.310 +	</ul>
   2.311 +
   2.312 +	<p class="issue">
   2.313 +		I wrote this definition off the top of my head,
   2.314 +		so it can't possibly be right.
   2.315 +		It's missing tons of pieces!
   2.316 +	</p>
   2.317 +
   2.318 +	<p class="issue">
   2.319 +		The handling of preserve-3d subtrees here is probably wrong;
   2.320 +		the elements should probably count
   2.321 +		only towards the overflow of the element that flattens them.
   2.322 +	</p>
   2.323 +
   2.324 +	<p>
   2.325 +		The <dfn>scrollable overflow region</dfn> is the non-rectangular region
   2.326 +		occupied by the <a>scrollable overflow</a>, and the
   2.327 +		<dfn>scrollable overflow rectangle</dfn> is
   2.328 +		the minimal rectangle whose axis is aligned to the box's axes
   2.329 +		and contains the <a>scrollable overflow region</a>.
   2.330 +		Note that the <a>scrollable overflow rectangle</a> is a rectangle
   2.331 +		in the box's coordinate system, but might be non-rectangular
   2.332 +		in other coordinate systems due to transforms [[CSS3-TRANSFORMS]].
   2.333 +	</p>
   2.334 +
   2.335 +<h3 id="border-box-overflow">Border box overflow</h3>
   2.336 +
   2.337 +	<p class="issue">
   2.338 +		This concept has been proposed for some uses, such as for
   2.339 +		determining what the 'outline' property goes around, and
   2.340 +		as the basis of a coordinate system for specifying clips and masks,
   2.341 +		but it's not clear if it's needed.
   2.342 +	</p>
   2.343 +
   2.344 +	<p>
   2.345 +		The <dfn>border-box overflow</dfn> of a box is the
   2.346 +		union of the box's border edge and the border edges of
   2.347 +		the box's descendants.</p>
   2.348 +	</p>
   2.349 +
   2.350 +	<p class="issue">
   2.351 +		If needed, define more formally, as for scrollable overflow above.
   2.352 +		(Maybe even share the definitions in an appropriate way!)
   2.353 +	</p>
   2.354 +
   2.355 +	<p>
   2.356 +		The <dfn>border-box overflow region</dfn> is the non-rectangular region
   2.357 +		occupied by the <a>border-box overflow</a>, and the
   2.358 +		<dfn>border-box overflow rectangle</dfn> is
   2.359 +		the minimal rectangle whose axis is aligned to the box's axes
   2.360 +		and contains the <a>border-box overflow region</a>.
   2.361 +		Note that the <a>border-box overflow rectangle</a> is a rectangle
   2.362 +		in the box's coordinate system, but might be non-rectangular
   2.363 +		in other coordinate systems due to transforms [[CSS3-TRANSFORMS]].
   2.364 +	</p>
   2.365 +
   2.366 +<h2 id="overflow-properties">Overflow properties</h2>
   2.367 +
   2.368 +	<p>
   2.369 +		The 'overflow-x' property specifies
   2.370 +		the handling of overflow in the horizontal direction
   2.371 +		(i.e., overflow from the left and right sides of the box),
   2.372 +		and the 'overflow-y' property specifies the handling
   2.373 +		of overflow in the vertical direction
   2.374 +		(i.e., overflow from the top and bottom sides of the box) 
   2.375 +	</p>
   2.376 +
   2.377 +	<table class=propdef>
   2.378 +		<tr>
   2.379 +			<th>Name:
   2.380 +			<td><dfn>overflow-x</dfn>, <dfn>overflow-y</dfn>
   2.381 +		<tr>
   2.382 +			<th>Value:
   2.383 +			<td>visible | hidden | scroll | auto | paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
   2.384 +		<tr>
   2.385 +			<th>Initial:
   2.386 +			<td>visible
   2.387 +		<tr>
   2.388 +			<th>Applies to:
   2.389 +			<td>block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
   2.390 +		<tr>
   2.391 +			<th>Inherited:
   2.392 +			<td>no
   2.393 +		<tr>
   2.394 +			<th>Percentages:
   2.395 +			<td>N/A
   2.396 +		<tr>
   2.397 +			<th>Media:
   2.398 +			<td>visual
   2.399 +		<tr>
   2.400 +			<th>Computed&nbsp;value:
   2.401 +			<td>see below
   2.402 +		<tr>
   2.403 +			<th>Animatable:
   2.404 +			<td>no
   2.405 +		<tr>
   2.406 +			<th>Canonical order:
   2.407 +			<td><abbr title="follows order of property value definition">per grammar</abbr>
   2.408 +	</table>
   2.409 +
   2.410 +	<p>
   2.411 +		The 'overflow' property is a shorthand property
   2.412 +		that sets the specified values of both 'overflow-x' and 'overflow-y'
   2.413 +		to the value specified for 'overflow'.
   2.414 +	</p>
   2.415 +
   2.416 +	<table class=propdef>
   2.417 +		<tr>
   2.418 +			<th>Name:
   2.419 +			<td><dfn>overflow</dfn>
   2.420 +		<tr>
   2.421 +			<th>Value:
   2.422 +			<td>visible | hidden | scroll | auto | paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
   2.423 +		<tr>
   2.424 +			<th>Initial:
   2.425 +			<td>see individual properties
   2.426 +		<tr>
   2.427 +			<th>Applies to:
   2.428 +			<td>block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
   2.429 +		<tr>
   2.430 +			<th>Inherited:
   2.431 +			<td>no
   2.432 +		<tr>
   2.433 +			<th>Percentages:
   2.434 +			<td>N/A
   2.435 +		<tr>
   2.436 +			<th>Media:
   2.437 +			<td>visual
   2.438 +		<tr>
   2.439 +			<th>Computed&nbsp;value:
   2.440 +			<td>see individual properties
   2.441 +		<tr>
   2.442 +			<th>Animatable:
   2.443 +			<td>no
   2.444 +		<tr>
   2.445 +			<th>Canonical order:
   2.446 +			<td><abbr title="follows order of property value definition">per grammar</abbr>
   2.447 +	</table>
   2.448 +
   2.449 +	<p>The values of these properties are:</p>
   2.450 +
   2.451 +	<dl dfn-for="overflow" dfn-type="value">
   2.452 +		<dt><dfn>visible</dfn>
   2.453 +		<dd>
   2.454 +			There is no special handling of overflow, that is, it
   2.455 +			may be rendered outside the block container.
   2.456 +		</dd>
   2.457 +		<dt><dfn>hidden</dfn>
   2.458 +		<dt><dfn>scroll</dfn>
   2.459 +		<dt><dfn>auto</dfn>
   2.460 +		<dd>
   2.461 +			These values are collectively the <dfn dfn>scrolling values</dfn>;
   2.462 +			they are defined in the section on
   2.463 +			<a href="#scrolling-overflow">scrolling and hidden overflow</a>.
   2.464 +		</dd>
   2.465 +		<dt><dfn>paged-x</dfn>
   2.466 +		<dt><dfn>paged-y</dfn>
   2.467 +		<dt><dfn>paged-x-controls</dfn>
   2.468 +		<dt><dfn>paged-y-controls</dfn>
   2.469 +		<dt><dfn>fragments</dfn>
   2.470 +		<dd>
   2.471 +			These values are collectively the <dfn dfn>fragmenting values</dfn>;
   2.472 +			they are defined in the sections on
   2.473 +			<a href="#paginated-overflow">paginated overflow</a> and
   2.474 +			<a href="#fragment-overflow">fragment overflow</a>.
   2.475 +		</dd>
   2.476 +	</dl>
   2.477 +
   2.478 +	<div id="overflow-computed-values">
   2.479 +		<p>The computed values of 'overflow-x' and 'overflow-y'
   2.480 +		are determined from the cascaded values [[!CSS3CASCADE]]
   2.481 +		based on the following rules:</p>
   2.482 +
   2.483 +		<ol>
   2.484 +			<li>
   2.485 +				If one or both of the cascaded values are
   2.486 +				<a>fragmenting values</a>, then:
   2.487 +				<ol>
   2.488 +					<li>
   2.489 +						If one of the cascaded values is one of the
   2.490 +						<a>fragmenting values</a>
   2.491 +						and the other is not,
   2.492 +						then the computed values are
   2.493 +						the same as the cascaded values.
   2.494 +					</li>
   2.495 +					<li>
   2.496 +						If both of the cascaded values are <a>fragmenting values</a>, then:
   2.497 +						<ol>
   2.498 +							<li>
   2.499 +								for horizontal writing mode [[!CSS3-WRITING-MODES]],
   2.500 +								the computed value for 'overflow-y' is the cascaded value
   2.501 +								and the computed value for 'overflow-x' is ''overflow/hidden'', or
   2.502 +							</li>
   2.503 +							<li>
   2.504 +								for vertical writing mode [[!CSS3-WRITING-MODES]],
   2.505 +								the computed value for 'overflow-x' is the cascaded value
   2.506 +								and the computed value for 'overflow-y' is ''overflow/hidden''.
   2.507 +							</li>
   2.508 +						</ol>
   2.509 +					</li>
   2.510 +				</ol>
   2.511 +			</li>
   2.512 +			<li>
   2.513 +				Otherwise, if one cascaded values is
   2.514 +				one of the <a>scrolling values</a>
   2.515 +				and the other is ''overflow/visible'',
   2.516 +				then computed values are the cascaded values
   2.517 +				with ''overflow/visible'' changed to ''overflow/auto''.
   2.518 +			</li>
   2.519 +			<li>
   2.520 +				Otherwise, the computed values are as specified.
   2.521 +			</li>
   2.522 +		</ol>
   2.523 +	</div>
   2.524 +
   2.525 +	<p class="issue">
   2.526 +		Are all 4 of the ''paged-*'' values really needed?
   2.527 +	</p>
   2.528 +
   2.529 +	<p>
   2.530 +		When the <a>fragmenting values</a> are used,
   2.531 +		the overflow from the fragments themselves
   2.532 +		treats the fragmenting value as ''overflow/hidden''.
   2.533 +		<span class="issue">Is this the right behavior?</span>
   2.534 +		<span class="issue">Give example.</span>
   2.535 +	</p>
   2.536 +
   2.537 +	<p class="issue">
   2.538 +		[[CSS3-MARQUEE]] describes an 'overflow-style' property,
   2.539 +		but it has not picked up implementation experience
   2.540 +		that the working group is aware of.
   2.541 +		Should this document treat 'overflow-style' as a defunct proposal,
   2.542 +		or should this document describe the 'overflow-style' property
   2.543 +		and attempt to revive it,
   2.544 +		despite that implementations have implemented
   2.545 +		'overflow-x' and 'overflow-y' instead?
   2.546 +	</p>
   2.547 +
   2.548 +	<p class="issue">
   2.549 +		There are <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussions</a>
   2.550 +		about how overflow, overflow-style, overflow-x and overflow-y
   2.551 +		should work and interact with each other.
   2.552 +		Until consensus on this topic is reached,
   2.553 +		it is not completely clear which of these
   2.554 +		should be used for
   2.555 +		paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
   2.556 +	</p>
   2.557 +
   2.558 +<h2 id="scrolling-overflow">Scrolling and hidden overflow</h2>
   2.559 +
   2.560 +	<p class="issue">
   2.561 +		Move material from [[CSS21]] and [[CSS3BOX]] here.
   2.562 +	</p>
   2.563 +
   2.564 +	<p class="issue">
   2.565 +		Explain which directions allow scrolling and which don't,
   2.566 +		as a function of 'direction'
   2.567 +		(including propagation of 'direction' to the ICB).
   2.568 +	</p>
   2.569 +
   2.570 +<h2 id="paginated-overflow">Paginated overflow</h2>
   2.571 +
   2.572 +<p class="issue">overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as [[CSS3GCPM]] has?)</p>
   2.573 +
   2.574 +<p class="issue">Ability to display N pages at once
   2.575 +rather than just one page at once?</p>
   2.576 +
   2.577 +	<p class="issue">
   2.578 +		The current implementation of paginated overflow uses
   2.579 +		the 'overflow'/'overflow-x'/'overflow-y' properties
   2.580 +		rather than the 'overflow-style' property as proposed
   2.581 +		in the [[CSS3GCPM]] draft
   2.582 +		(which also matches the [[CSS3-MARQUEE]] proposal).
   2.583 +		We should probably switch away from 'overflow-style',
   2.584 +		but that's not 100% clear.
   2.585 +	</p>
   2.586 +
   2.587 +<h2 id="fragment-overflow">Fragment overflow</h2>
   2.588 +
   2.589 +	<p>
   2.590 +		This section introduces and defines the meaning of
   2.591 +		the new ''fragments'' value of the 'overflow' property.
   2.592 +	</p>
   2.593 +
   2.594 +	<p>
   2.595 +		When the computed value of 'overflow' for an element is ''fragments'',
   2.596 +		and implementations would otherwise have created a box for the element,
   2.597 +		then implementations must create a sequence of <dfn>fragment box</dfn>es
   2.598 +		for that element.
   2.599 +		(It is possible for an element with ''overflow: fragments''
   2.600 +		to generate only one <a>fragment box</a>.
   2.601 +		However, if an element's computed 'overflow' is not ''fragments'',
   2.602 +		then its box is not a <a>fragment box</a>.)
   2.603 +		Every <a>fragment box</a> is a fragmentation container,
   2.604 +		and any overflow
   2.605 +		that would cause that fragmentation container to fragment
   2.606 +		causes another <a>fragment box</a> created as a next sibling
   2.607 +		of the previous one.
   2.608 +		<span class="issue">Or is it as though it's a next sibling of
   2.609 +		the element?  Need to figure out exactly how this interacts with
   2.610 +		other box-level fixup.</span>
   2.611 +		Additionally, if the <a>fragment box</a> is also
   2.612 +		a multi-column box (as defined in [[!CSS3COL]]
   2.613 +		<span class="issue">though it defines <i>multi-column element</i></span>)
   2.614 +		any content that would lead to the creation of <a>overflow columns</a> [[!CSS3COL]]
   2.615 +		instead is flown into an additional fragment box.
   2.616 +		However, fragment boxes may themselves be broken
   2.617 +		(due to fragmentation in a fragmentation context outside of them,
   2.618 +		such as pages, columns, or other fragment boxes);
   2.619 +		such breaking leads to fragments of the same fragment box
   2.620 +		rather than multiple fragment boxes.
   2.621 +		(This matters because fragment boxes may be styled by their index;
   2.622 +		such breaking leads to multiple fragments of a fragment box
   2.623 +		with a single index.
   2.624 +		This design choice is so that
   2.625 +		breaking a fragment box across pages does not break
   2.626 +		the association of indices to particular pieces of content.)
   2.627 +		<span class="issue">Should a forced break that breaks to
   2.628 +		an outer fragmentation context cause a new fragment of a single
   2.629 +		fragment box or a new fragment box?</span>
   2.630 +		<span class="issue">Should we find a term other than
   2.631 +		<a>fragment box</a> here to make this a little less confusing?</span>
   2.632 +	</p>
   2.633 +
   2.634 +	<p class="issue">
   2.635 +		What if we want to be able to style the pieces of an element
   2.636 +		split within another type of fragmentation context?
   2.637 +		These rules prevent ever using ''::nth-fragment()'' for that,
   2.638 +		despite that the name seems the most logical name for such a feature.
   2.639 +	</p>
   2.640 +
   2.641 +	<div class="example">
   2.642 +		<table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
   2.643 +&lt;title&gt;Breaking content into
   2.644 +  equal-sized cards&lt;/title&gt;
   2.645 +&lt;style&gt;
   2.646 +  .in-cards {
   2.647 +    overflow: fragments;
   2.648 +
   2.649 +    width: 13em;
   2.650 +    height: 8em;
   2.651 +
   2.652 +    padding: 4px;
   2.653 +    border: medium solid blue;
   2.654 +    margin: 6px;
   2.655 +
   2.656 +    font: medium/1.3 Times New
   2.657 +      Roman, Times, serif;
   2.658 +  }
   2.659 +&lt;/style&gt;
   2.660 +&lt;div class="in-cards"&gt;
   2.661 +  In this example, the text in the div
   2.662 +  is broken into a series of cards.
   2.663 +  These cards all have the same style.
   2.664 +  The presence of enough content to
   2.665 +  overflow one of the cards causes
   2.666 +  another one to be created.  The second
   2.667 +  card is created just like it's the
   2.668 +  next sibling of the first.
   2.669 +&lt;/div&gt;</pre></td><td>
   2.670 +			<div class="in-cards-demo">In this example, the text in the<br>div is broken into a series of<br>cards.  These cards all have the<br>same style. The presence of<br>enough content to overflow<br>one of the cards causes another</div>
   2.671 +			<div class="in-cards-demo">one to be created.  The second<br>card is created just like it's the<br>next sibling of the first.</div>
   2.672 +		</td></tr></table>
   2.673 +	</div>
   2.674 +
   2.675 +	<p class="issue">
   2.676 +		We should specify that ''overflow: fragments'' does not apply
   2.677 +		to at least some table parts,
   2.678 +		and perhaps other elements as well.
   2.679 +		We need to determine exactly which ones.
   2.680 +	</p>
   2.681 +
   2.682 +	<p class="issue">
   2.683 +		This specification needs to say which type of
   2.684 +		fragmentation context is created
   2.685 +		so that it's clear which values of the 'break-*' properties
   2.686 +		cause breaks within this context.
   2.687 +		We probably want ''break-*: region'' to apply.
   2.688 +	</p>
   2.689 +
   2.690 +	<p class="issue">
   2.691 +		This specification needs a processing model
   2.692 +		that will apply in cases where the layout containing the
   2.693 +		fragments has characteristics that use the intrinsic size of the fragments
   2.694 +		to change the amount of space available for them,
   2.695 +		such as [[CSS3-GRID-LAYOUT]].
   2.696 +		There has already been some work on such a processing model
   2.697 +		in [[CSS3-REGIONS]],
   2.698 +		and the work done on a model there,
   2.699 +		and the editors of that specification,
   2.700 +		should inform what happens in this specification.
   2.701 +	</p>
   2.702 +
   2.703 +<h3 id="fragment-styling">Fragment styling</h3>
   2.704 +
   2.705 +<h4 id="fragment-pseudo-element">The ::nth-fragment() pseudo-element</h4>
   2.706 +
   2.707 +	<p>
   2.708 +		The ::nth-fragment() pseudo-element is a pseudo-element
   2.709 +		that describes some of the <a>fragment box</a>es generated by an element.
   2.710 +		The argument to the pseudo-element takes the same syntax
   2.711 +		as the argument to the :nth-child() pseudo-class
   2.712 +		defined in [[!SELECT]], and has the same meaning
   2.713 +		except that the number is relative to
   2.714 +		<a>fragment box</a>es generated by the element
   2.715 +		instead of siblings of the element.
   2.716 +	</p>
   2.717 +
   2.718 +	<p class="note">
   2.719 +		Selectors that allow addressing fragments
   2.720 +		by counting from the end rather than the start
   2.721 +		are intentionally not provided.
   2.722 +		Such selectors would interfere with determining
   2.723 +		the number of fragments.
   2.724 +	</p>
   2.725 +
   2.726 +	<p class="issue">
   2.727 +		Depending on future discussions,
   2.728 +		this ''::nth-fragment(<var>an+b</var>)'' syntax
   2.729 +		may be replaced with
   2.730 +		the new ''::fragment:nth(<var>an+b</var>)'' syntax.
   2.731 +	</p>
   2.732 +
   2.733 +<h4 id="style-of-fragments">Styling of fragments</h4>
   2.734 +
   2.735 +	<p class="issue">
   2.736 +		Should this apply to fragment overflow only,
   2.737 +		or also to paginated overflow?
   2.738 +		(If it applies,
   2.739 +		then stricter property restrictions would be needed
   2.740 +		for paginated overflow.)
   2.741 +	</p>
   2.742 +
   2.743 +	<p>
   2.744 +		In the absence of rules with ''::nth-fragment()'' pseudo-elements,
   2.745 +		the computed style for each <a>fragment box</a>
   2.746 +		is the computed style for the element
   2.747 +		for which the <a>fragment box</a> was created.
   2.748 +		However, the style for a <a>fragment box</a> is also influenced
   2.749 +		by rules whose selector's <a>subject</a> [[!SELECT]]
   2.750 +		has an ''::nth-fragment()'' pseudo-element,
   2.751 +		if the 1-based number of the <a>fragment box</a> matches
   2.752 +		that ''::nth-fragment()'' pseudo-element
   2.753 +		and the selector (excluding the ''::nth-fragment()'' pseudo-element)
   2.754 +		matches the element generating the fragments.
   2.755 +	</p>
   2.756 +
   2.757 +	<p>
   2.758 +		When determining the style of the <a>fragment box</a>,
   2.759 +		these rules that match the fragment pseudo-element
   2.760 +		cascade together with the rules that match the element,
   2.761 +		with the fragment pseudo-element adding the specificity
   2.762 +		of a pseudo-class to the specificity calculation.
   2.763 +		<span class="issue">Does this need to be specified in
   2.764 +		the cascading module as well?</span>
   2.765 +	</p>
   2.766 +
   2.767 +	<div class="example">
   2.768 +		<table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
   2.769 +&lt;style&gt;
   2.770 +  .bouncy-columns {
   2.771 +    overflow: fragments;
   2.772 +    width: 6em;
   2.773 +    height: 10em;
   2.774 +    float: left;
   2.775 +    margin: 1em;
   2.776 +    font: medium/1.25 Times New
   2.777 +      Roman, Times, serif;
   2.778 +  }
   2.779 +  .bouncy-columns::nth-fragment(1) {
   2.780 +    background: aqua; color: black;
   2.781 +    transform: rotate(-3deg);
   2.782 +  }
   2.783 +  .bouncy-columns::nth-fragment(2) {
   2.784 +    background: yellow; color: black;
   2.785 +    transform: rotate(3deg);
   2.786 +  }
   2.787 +&lt;/style&gt;
   2.788 +&lt;div class="bouncy-columns"&gt;
   2.789 +  <i>...</i>
   2.790 +&lt;/div&gt;</pre></td><td>
   2.791 +			<div class="bouncy-columns-demo one">In this<br>example, the<br>text in the div<br>is broken into<br>a series of<br>columns.  The<br>author<br>probably</div>
   2.792 +			<div class="bouncy-columns-demo two">intended the<br>text to fill two<br>columns.  But<br>if it happens to<br>fill three<br>columns, the<br>third column is<br>still created.  It</div>
   2.793 +			<div class="bouncy-columns-demo">just doesn't<br>have any<br>fragment-specific<br>styling because<br>the author<br>didn't give it<br>any.</div>
   2.794 +		</td></tr></table>
   2.795 +	</div>
   2.796 +
   2.797 +	<p>
   2.798 +		Styling an ''::nth-fragment()'' pseudo-element with the 'overflow'
   2.799 +		property does take effect;
   2.800 +		if a <a>fragment box</a> has a
   2.801 +		computed value of 'overflow' other than ''fragments''
   2.802 +		then that fragment box is the last fragment.
   2.803 +		However, overriding 'overflow' on the first fragment
   2.804 +		does not cause the <a>fragment box</a> not to exist;
   2.805 +		whether there are fragment boxes at all is determined by
   2.806 +		the computed value of overflow for the element.
   2.807 +		<span class="issue">Need to reword this to refer to the
   2.808 +		appropriate choice of 'overflow-x' or 'overflow-y',
   2.809 +		and then point to rule about the handling of the other one
   2.810 +		of 'overflow-x' or 'overflow-y'.</span>
   2.811 +	</p>
   2.812 +
   2.813 +	<p>
   2.814 +		Styling an ''::nth-fragment()'' pseudo-element with the 'content'
   2.815 +		property has no effect;
   2.816 +		the computed value of 'content' for the fragment box
   2.817 +		remains the same as the computed value of content for the element.
   2.818 +	</p>
   2.819 +
   2.820 +	<p>
   2.821 +		Specifying ''display: none'' for a <a>fragment box</a> causes
   2.822 +		the fragment box with that index not to be generated.
   2.823 +		However, in terms of the indices
   2.824 +		used for matching ''::nth-fragment()'' pseudo-elements
   2.825 +		of later fragment boxes,
   2.826 +		it still counts as though it was generated.
   2.827 +		However, since it is not generated, it does not contain any content.
   2.828 +	</p>
   2.829 +
   2.830 +	<p>
   2.831 +		Specifying other values of 'display', 'position',
   2.832 +		or 'float' is permitted, but is not allowed to change
   2.833 +		the computed value of 'display-inside'.
   2.834 +		(Since 'overflow', 'overflow-x', and 'overflow-y' only
   2.835 +		apply to block containers, flex containers, and grid containers
   2.836 +		the computed value of 'display-inside' is always
   2.837 +		''display-inside/block'', ''display-inside/flex'', or
   2.838 +		''display-inside/grid''.
   2.839 +		<span class="issue">Need to specify exactly how this works,
   2.840 +		but it depends on
   2.841 +		having 'display-inside' and 'display-outside' specified.</span>
   2.842 +	</p>
   2.843 +
   2.844 +	<p>
   2.845 +		To match the model for other pseudo-elements
   2.846 +		where the pseudo-elements live inside their corresponding element,
   2.847 +		declarations in ''::nth-fragment()'' pseudo-elements override
   2.848 +		declarations in rules without the pseudo-element.
   2.849 +		The relative priority within such declarations is determined
   2.850 +		by normal cascading order (see [[!CSS21]]).
   2.851 +	</p>
   2.852 +
   2.853 +	<p>
   2.854 +		Styles specified on ''::nth-fragment()'' pseudo-elements
   2.855 +		do affect inheritance to content within the <a>fragment box</a>.
   2.856 +		In other words, the content within the <a>fragment box</a> must
   2.857 +		inherit from the fragment box's style (i.e., the pseudo-element style)
   2.858 +		rather than directly from the element.
   2.859 +		This means that elements split between fragment boxes may
   2.860 +		have different styles for different parts of the element.
   2.861 +	</p>
   2.862 +
   2.863 +	<p class="issue">
   2.864 +		This inheritance rule allows specifying styles indirectly
   2.865 +		(by using explicit ''inherit'' or using default inheritance
   2.866 +		on properties that don't apply to '':first-letter'')
   2.867 +		that can't be specified directly
   2.868 +		(based on the rules in the next section).
   2.869 +		This is a problem.
   2.870 +		The restrictions that apply to styling inside fragments
   2.871 +		should also apply to inheritance from fragments.
   2.872 +	</p>
   2.873 +
   2.874 +	<div class="example">
   2.875 +		<table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
   2.876 +&lt;style&gt;
   2.877 +  .article {
   2.878 +    overflow: fragments;
   2.879 +  }
   2.880 +  .article::nth-fragment(1) {
   2.881 +    font-size: 1.5em;
   2.882 +    margin-bottom: 1em;
   2.883 +    height: 4em;
   2.884 +  }
   2.885 +  .article::nth-fragment(2) {
   2.886 +    margin-left: 5em;
   2.887 +    margin-right: 2em;
   2.888 +  }
   2.889 +&lt;/style&gt;
   2.890 +&lt;div class="article"&gt;
   2.891 +  The &lt;code&gt;font-size&lt;/code&gt; property<i>...</i>
   2.892 +&lt;/div&gt;</pre></td><td>
   2.893 +			<div class="article-font-inherit-demo one">The <code>font-size</code> property<br>specified on the fragment<br>is inherited into the</div>
   2.894 +			<div class="article-font-inherit-demo two">descendants of the fragment.<br>This means that inherited<br>properties can be used<br>reliably on a fragment, as in<br>this example.</div>
   2.895 +		</td></tr></table>
   2.896 +	</div>
   2.897 +
   2.898 +<h4 id="style-in-fragments">Styling inside fragments</h4>
   2.899 +
   2.900 +	<p class="issue">
   2.901 +		Should this apply to fragment overflow only,
   2.902 +		or also to paginated overflow,
   2.903 +		or even to pagination across pages?
   2.904 +	</p>
   2.905 +
   2.906 +	<p>
   2.907 +		The ''::nth-fragment()'' pseudo-element
   2.908 +		can also be used to style
   2.909 +		content inside of a <a>fragment box</a>.
   2.910 +		Unlike the ''::first-line'' and ''::first-letter'' pseudo-elements,
   2.911 +		the ''::nth-fragment()'' pseudo-element can be applied
   2.912 +		to parts of the selector other than the subject:
   2.913 +		in particular, it can match ancestors of the subject.
   2.914 +		However, the only CSS properties applied
   2.915 +		by rules with such selectors
   2.916 +		are those that apply
   2.917 +		to the ''::first-letter'' pseudo-element.
   2.918 +	</p>
   2.919 +
   2.920 +	<p>
   2.921 +		To be more precise,
   2.922 +		when a rule's selector has ''::nth-fragment()'' pseudo-elements
   2.923 +		attached to parts of the selector other than the subject,
   2.924 +		the declarations in that rule apply to
   2.925 +		a fragment (or pseudo-element thereof) when:
   2.926 +	</p>
   2.927 +	<ol>
   2.928 +		<li>
   2.929 +			the declarations are for properties that apply to the
   2.930 +			''::first-letter'' pseudo-element,
   2.931 +		</li>
   2.932 +		<li>
   2.933 +			the declarations would apply to
   2.934 +			that fragment (or pseudo-element thereof)
   2.935 +			had those ''::nth-fragment()'' pseudo-elements been removed,
   2.936 +			with a particular association between
   2.937 +			each sequence of simple selectors and the element it matched,
   2.938 +			and
   2.939 +		</li>
   2.940 +		<li>
   2.941 +			for each removed ''::nth-fragment()'' pseudo-element,
   2.942 +			the fragment lives within a <a>fragment box</a>
   2.943 +			of the element associated in that association
   2.944 +			with the selector that the pseudo-element was attached to,
   2.945 +			and whose index matches the pseudo-element.
   2.946 +		</li>
   2.947 +	</ol>
   2.948 +
   2.949 +	<div class="example">
   2.950 +		<table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
   2.951 +&lt;style&gt;
   2.952 +  .dark-columns {
   2.953 +    overflow: fragments;
   2.954 +    width: 6em;
   2.955 +    height: 10em;
   2.956 +    float: left;
   2.957 +    margin-right: 1em;
   2.958 +    font: medium/1.25 Times New
   2.959 +      Roman, Times, serif;
   2.960 +  }
   2.961 +  .dark-columns::nth-fragment(1) {
   2.962 +    background: aqua; color: black;
   2.963 +  }
   2.964 +  .dark-columns::nth-fragment(1) :link {
   2.965 +    color: blue;
   2.966 +  }
   2.967 +  .dark-columns::nth-fragment(1) :visited {
   2.968 +    color: purple;
   2.969 +  }
   2.970 +  .dark-columns::nth-fragment(2) {
   2.971 +    background: navy; color: white;
   2.972 +  }
   2.973 +  .dark-columns::nth-fragment(2) :link {
   2.974 +    color: aqua;
   2.975 +  }
   2.976 +  .dark-columns::nth-fragment(2) :visited {
   2.977 +    color: fuchsia;
   2.978 +  }
   2.979 +&lt;/style&gt;
   2.980 +&lt;div class="dark-columns"&gt;
   2.981 +  <i>...</i>
   2.982 +&lt;/div&gt;</pre></td><td>
   2.983 +			<div class="dark-columns-demo one">In this<br><a href="http://en.wiktionary.org/wiki/example">example</a>, the<br>text flows<br>from one<br>light-colored<br>fragment into<br>another<br>dark-colored</div>
   2.984 +			<div class="dark-columns-demo two">fragment.  We<br>therefore want<br>different styles<br>for <a href="http://www.w3.org/Provider/Style/IntoContext.html">hyperlinks</a><br>in the different<br>fragments.</div>
   2.985 +		</td></tr></table>
   2.986 +	</div>
   2.987 +
   2.988 +
   2.989 +<h3 id="max-lines">The 'max-lines' property</h3>
   2.990 +
   2.991 +	<p>
   2.992 +		Authors may wish to style the opening lines of an element
   2.993 +		with different styles
   2.994 +		by putting those opening lines in a separate fragment.
   2.995 +		However, since it may be difficult to predict the exact height
   2.996 +		occupied by those lines
   2.997 +		in order to restrict the first fragment to that height,
   2.998 +		this specification introduces a 'max-lines' property
   2.999 +		that forces a fragment to break
  2.1000 +		after a specified number of lines.
  2.1001 +		This forces a break after the given number of lines
  2.1002 +		contained within the element or its descendants,
  2.1003 +		as long as those lines are in the same block formatting context.
  2.1004 +	</p>
  2.1005 +
  2.1006 +	<table class=propdef>
  2.1007 +		<tr>
  2.1008 +			<th>Name:
  2.1009 +			<td><dfn>max-lines</dfn>
  2.1010 +		<tr>
  2.1011 +			<th>Value:
  2.1012 +			<td>none | &lt;integer&gt;
  2.1013 +		<tr>
  2.1014 +			<th>Initial:
  2.1015 +			<td>none
  2.1016 +		<tr>
  2.1017 +			<th>Applies to:
  2.1018 +			<td>fragment boxes
  2.1019 +		<tr>
  2.1020 +			<th>Inherited:
  2.1021 +			<td>no
  2.1022 +		<tr>
  2.1023 +			<th>Animatable:
  2.1024 +			<td>as <a href="http://www.w3.org/TR/css3-transitions/#animatable-types">integer</a>
  2.1025 +		<tr>
  2.1026 +			<th>Percentages:
  2.1027 +			<td>N/A
  2.1028 +		<tr>
  2.1029 +			<th>Media:
  2.1030 +			<td>visual
  2.1031 +		<tr>
  2.1032 +			<th>Computed&nbsp;value:
  2.1033 +			<td>specified value
  2.1034 +		<tr>
  2.1035 +			<th>Canonical order:
  2.1036 +			<td><abbr title="follows order of property value definition">per grammar</abbr>
  2.1037 +	</table>
  2.1038 +
  2.1039 +	<dl dfn-for="max-lines" dfn-type="value">
  2.1040 +		<dt><dfn>none</dfn>
  2.1041 +		<dd>
  2.1042 +			<p>
  2.1043 +				Breaks occur only as specified elsewhere.
  2.1044 +			</p>
  2.1045 +		</dd>
  2.1046 +
  2.1047 +		<dt><dfn>&lt;integer&gt;</dfn>
  2.1048 +		<dd>
  2.1049 +			<p>
  2.1050 +				In addition to any breaks specified elsewhere,
  2.1051 +				a break is forced before any line that would exceed
  2.1052 +				the given number of lines
  2.1053 +				being placed inside the element
  2.1054 +				(excluding lines that are in
  2.1055 +				a different block formatting context from
  2.1056 +				the block formatting context to which
  2.1057 +				an unstyled child of the element would belong).
  2.1058 +			</p>
  2.1059 +
  2.1060 +			<p class="issue">
  2.1061 +				If there are multiple boundaries between this line
  2.1062 +				and the previous, where exactly (in terms of element
  2.1063 +				boundaries) is the break forced?
  2.1064 +			</p>
  2.1065 +
  2.1066 +			<p>
  2.1067 +				Only positive integers are accepted.
  2.1068 +				Zero or negative integers are a parse error.
  2.1069 +			</p>
  2.1070 +		</dd>
  2.1071 +	</dl>
  2.1072 +
  2.1073 +<p class="issue">Should this apply to fragment overflow only, or also
  2.1074 +to pagination?</p>
  2.1075 +
  2.1076 +	<div class="example">
  2.1077 +		<table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
  2.1078 +&lt;style&gt;
  2.1079 +  .article {
  2.1080 +    overflow: fragments;
  2.1081 +  }
  2.1082 +  .article::first-letter {
  2.1083 +    font-size: 2em;
  2.1084 +    line-height: 0.9;
  2.1085 +  }
  2.1086 +  .article::nth-fragment(1) {
  2.1087 +    font-size: 1.5em;
  2.1088 +    max-lines: 3;
  2.1089 +  }
  2.1090 +  .article::nth-fragment(2) {
  2.1091 +    column-count: 2;
  2.1092 +  }
  2.1093 +&lt;/style&gt;
  2.1094 +&lt;div class="article"&gt;
  2.1095 +  <i>...</i>
  2.1096 +&lt;/div&gt;</pre></td><td>
  2.1097 +			<div class="article-max-lines-demo one">The max-lines property allows<br>authors to use a larger font for the first<br>few lines of an article.  Without the</div>
  2.1098 +			<div class="article-max-lines-demo two">max-lines property, authors<br>might have to use the<br>'height' property instead, but<br>that would leave a slight gap<br>if the author miscalculated<br>how much height a given<br>number of lines would<br>occupy (which might be</div>
  2.1099 +			<div class="article-max-lines-demo three">particularly hard if the author<br>didn't know what text would<br>be filling the space, exactly<br>what font would be used, or<br>exactly which platform's font<br>rendering would be used to<br>display the font).</div>
  2.1100 +		</td></tr></table>
  2.1101 +	</div>
  2.1102 +
  2.1103 +<h2 id="static-media">Overflow in static media</h2>
  2.1104 +
  2.1105 +	<p class="issue">
  2.1106 +		This specification should define useful behavior
  2.1107 +		for all values of 'overflow'
  2.1108 +		in static media (such as print).
  2.1109 +		Current implementation behavior is quite poor and
  2.1110 +		produces unexpected results when authors have not considered
  2.1111 +		what will happen when
  2.1112 +		the content they produce for interactive media
  2.1113 +		is printed.
  2.1114 +	</p>
  2.1115 +
  2.1116 +<h2 class=no-num id="acknowledgments">
  2.1117 +Acknowledgments</h2>
  2.1118 +
  2.1119 +	<p>
  2.1120 +		Thanks especially to the feedback from
  2.1121 +		Rossen Atanassov,
  2.1122 +		Bert Bos,
  2.1123 +		Tantek Çelik,
  2.1124 +		John Daggett,
  2.1125 +		fantasai,
  2.1126 +		Daniel Glazman,
  2.1127 +		Vincent Hardy,
  2.1128 +		H&aring;kon Wium Lie,
  2.1129 +		Peter Linss,
  2.1130 +		Robert O'Callahan,
  2.1131 +		Florian Rivoal,
  2.1132 +		Alan Stearns,
  2.1133 +		Steve Zilles,
  2.1134 +		and all the rest of the
  2.1135 +		<a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> community.
  2.1136 +	</p>

     3.1 --- a/css-overflow/Overview.html	Tue Jan 27 15:44:28 2015 -0800
     3.2 +++ b/css-overflow/Overview.html	Tue Jan 27 15:56:33 2015 -0800
     3.3 @@ -1,26 +1,63 @@
     3.4 -<!DOCTYPE html>
     3.5 +<!doctype html>
     3.6 +<html lang="en">
     3.7 + <head>
     3.8 +  
     3.9 +  <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
    3.10 +  
    3.11 +  
    3.12 +  <title>CSS Overflow Module Level 3</title>
    3.13 +  
    3.14 +  
    3.15 +  <link href="../default.css" rel="stylesheet" type="text/css">
    3.16 +  
    3.17 +  
    3.18 +  <link href="../csslogo.ico" rel="shortcut icon" type="image/x-icon">
    3.19 +  
    3.20 +  
    3.21 +  <style>
    3.22 +  body {
    3.23 +    background: url("https://www.w3.org/StyleSheets/TR/logo-ED") top left no-repeat white;
    3.24 +    background-attachment: fixed;
    3.25 +    color: black;
    3.26 +    font-family: sans-serif;
    3.27 +    margin: 0 auto;
    3.28 +    max-width: 50em;
    3.29 +    padding: 2em 1em 2em 70px;
    3.30 +  }
    3.31 +  :link { color: #00C; background: transparent }
    3.32 +  :visited { color: #609; background: transparent }
    3.33 +  a[href]:active { color: #C00; background: transparent }
    3.34 +  a[href]:hover { background: #ffa }
    3.35  
    3.36 -<html lang=en>
    3.37 - <head>
    3.38 -  <meta content="text/html; charset=utf-8" http-equiv=Content-Type>
    3.39 -  <title>CSS Overflow Module Level 3</title>
    3.40 -  <!--
    3.41 -  <link href="http://purl.org/dc/terms/" rel="schema.dcterms">
    3.42 -  <link href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" rel="dcterms.rights">
    3.43 -  -->
    3.44 +  a[href] img { border-style: none }
    3.45  
    3.46 -  <meta content="CSS Overflow Module Level 3" name=dcterms.title>
    3.47 -  <meta content=text name=dcterms.type>
    3.48 -  <meta content=2015-01-27 name=dcterms.date>
    3.49 -  <meta content="L. David Baron" name=dcterms.creator>
    3.50 -  <meta content=W3C name=dcterms.publisher>
    3.51 -  <meta content="http://dev.w3.org/csswg/css-overflow-3/"
    3.52 -   name=dcterms.identifier>
    3.53 -  <link href="#contents" rel=contents>
    3.54 -  <link href="#index" rel=index>
    3.55 -  <link href="../default.css" rel=stylesheet type="text/css">
    3.56 -  <link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel=stylesheet
    3.57 -   type="text/css">
    3.58 +  h1, h2, h3, h4, h5, h6 { text-align: left }
    3.59 +  h1, h2, h3 { color: #005A9C; }
    3.60 +  h1 { font: 170% sans-serif }
    3.61 +  h2 { font: 140% sans-serif }
    3.62 +  h3 { font: 120% sans-serif }
    3.63 +  h4 { font: bold 100% sans-serif }
    3.64 +  h5 { font: italic 100% sans-serif }
    3.65 +  h6 { font: small-caps 100% sans-serif }
    3.66 +
    3.67 +  .hide { display: none }
    3.68 +
    3.69 +  div.head { margin-bottom: 1em }
    3.70 +  div.head h1 { margin-top: 2em; clear: both }
    3.71 +  div.head table { margin-left: 2em; margin-top: 2em }
    3.72 +
    3.73 +  p.copyright { font-size: small }
    3.74 +  p.copyright small { font-size: small }
    3.75 +
    3.76 +  pre { margin-left: 2em }
    3.77 +  dt { font-weight: bold }
    3.78 +
    3.79 +  ul.toc, ol.toc {
    3.80 +    list-style: none;
    3.81 +  }
    3.82 +  </style>
    3.83 +  
    3.84 +
    3.85    <style>
    3.86  		table.source-demo-pair {
    3.87  			width: 100%;
    3.88 @@ -119,763 +156,878 @@
    3.89  			float: left;
    3.90  		}
    3.91  	</style>
    3.92 +  
    3.93  
    3.94 - <body>
    3.95 -  <div class=head> <!--begin-logo-->
    3.96 -   <p><a href="http://www.w3.org/"><img alt=W3C height=48
    3.97 -    src="http://www.w3.org/Icons/w3c_home" width=72></a> <!--end-logo-->
    3.98 +	
    3.99 + </head>
   3.100 + 
   3.101  
   3.102 -   <h1>CSS Overflow Module Level 3</h1>
   3.103 + <body class="h-entry">
   3.104  
   3.105 -   <h2 class="no-num no-toc">Editor's Draft 27 January 2015</h2>
   3.106 +  <div class="head">
   3.107 +  
   3.108 +   <p data-fill-with="logo"><a class="logo" href="http://www.w3.org/">
   3.109 +    <img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72">
   3.110 +</a>
   3.111 +</p>
   3.112 +  
   3.113 +   <h1 class="p-name no-ref" id="title">CSS Overflow Module Level 3</h1>
   3.114 +  
   3.115 +   <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft,
   3.116 +    <time class="dt-updated" datetime="2015-01-27">27 January 2015</time></span></h2>
   3.117 +  
   3.118 +   <div data-fill-with="spec-metadata">
   3.119 +    <dl>
   3.120 +     <dt>This version:
   3.121 +     <dd><a class="u-url" href="http://dev.w3.org/csswg/css-overflow/">http://dev.w3.org/csswg/css-overflow/</a>
   3.122 +     <dt>Latest version:
   3.123 +     <dd><a href="http://www.w3.org/TR/css-overflow-3/">http://www.w3.org/TR/css-overflow-3/</a>
   3.124 +     <dt>Previous Versions:
   3.125 +     <dd><a href="http://www.w3.org/TR/2013/WD-css-overflow-3-20130418/" rel="previous">http://www.w3.org/TR/2013/WD-css-overflow-3-20130418/</a>
   3.126 +     <dt>Feedback:
   3.127 +     <dd><span><a href="mailto:[email protected]?subject=%5Bcss-overflow%5D%20feedback">[email protected]</a> with subject line “<kbd>[css-overflow] <var>… message topic …</var></kbd>” (<a href="http://lists.w3.org/Archives/Public/www-style/" rel="discussion">archives</a>)</span>
   3.128 +     <dt>Issue Tracking:
   3.129 +     <dd><a href="#issues-index">Inline In Spec</a>
   3.130 +     <dt class="editor">Editor:
   3.131 +     <dd class="editor">
   3.132 +      <div class="p-author h-card vcard"><a class="p-name fn u-url url" href="http://dbaron.org/">L. David Baron</a> (<span class="p-org org">Mozilla</span>)</div>
   3.133 +     <dt>Change Log:
   3.134 +     <dd><span><a href="https://dvcs.w3.org/hg/csswg/log/tip/css-overflow/Overview.bs">from 27 January 2015 to the present</a></span>
   3.135 +     <dd><span><a href="https://dvcs.w3.org/hg/csswg/log/tip/css-overflow/Overview.src.html">from 28 March 2013 to 27 January 2015</a></span>
   3.136 +     <dd><span><a href="https://dvcs.w3.org/hg/csswg/log/tip/css3-overflow/Overview.src.html">from 31 July 2012to 27 March 2013</a></span>
   3.137 +    </dl>
   3.138 +   </div>
   3.139 +  
   3.140 +   <div data-fill-with="warning"></div>
   3.141 +  
   3.142 +   <p class="copyright" data-fill-with="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2015 <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
   3.143 +</p>
   3.144 +  
   3.145 +   <hr title="Separator for header">
   3.146 +</div>
   3.147  
   3.148 +
   3.149 +  <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="content">Abstract</span></h2>
   3.150 +
   3.151 +  <div class="p-summary" data-fill-with="abstract">
   3.152 +   <p>This module contains the features of CSS relating to new mechanisms of overflow handling in visual media (e.g., screen or paper).  In interactive media, it describes features that allow the overflow from a fixed size container to be handled by pagination (displaying one page at a time).  It also describes features, applying to all visual media, that allow the contents of an element to be spread across multiple fragments, allowing the contents to flow across multiple regions or to have different styles for different fragments.</p>
   3.153 +
   3.154 +<a href="http://www.w3.org/TR/CSS/">CSS</a> is a language for describing the rendering of structured documents 
   3.155 +(such as HTML and XML) 
   3.156 +on screen, on paper, in speech, etc.</div>
   3.157 +
   3.158 +
   3.159 +  <h2 class="no-num no-toc no-ref heading settled" id="status"><span class="content">Status of this document</span></h2>
   3.160 +
   3.161 +  <div data-fill-with="status">
   3.162 +   <p>
   3.163 +	This is a public copy of the editors’ draft.
   3.164 +	It is provided for discussion only and may change at any moment.
   3.165 +	Its publication here does not imply endorsement of its contents by W3C.
   3.166 +	Don’t cite this document other than as work in progress.
   3.167 +
   3.168 +</p>
   3.169 +   <p>
   3.170 +	The (<a href="http://lists.w3.org/Archives/Public/www-style/">archived</a>) public mailing list
   3.171 +	<a href="mailto:[email protected]?Subject=%5Bcss-overflow%5D%20PUT%20SUBJECT%20HERE">[email protected]</a>
   3.172 +	(see <a href="http://www.w3.org/Mail/Request">instructions</a>)
   3.173 +	is preferred for discussion of this specification.
   3.174 +	When sending e-mail,
   3.175 +	please put the text “css-overflow” in the subject,
   3.176 +	preferably like this:
   3.177 +	“[css-overflow] <em>…summary of comment…</em>”
   3.178 +
   3.179 +</p>
   3.180 +   <p>
   3.181 +	This document was produced by the <a href="http://www.w3.org/Style/CSS/members">CSS Working Group</a>
   3.182 +	(part of the <a href="http://www.w3.org/Style/">Style Activity</a>).
   3.183 +
   3.184 +</p>
   3.185 +   <p>
   3.186 +	This document was produced by a group operating under
   3.187 +	the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>.
   3.188 +	W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/32061/status" rel="disclosure">public list of any patent disclosures</a>
   3.189 +	made in connection with the deliverables of the group;
   3.190 +	that page also includes instructions for disclosing a patent.
   3.191 +	An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a>
   3.192 +	must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.
   3.193 +
   3.194 +</p>
   3.195 +   <p>
   3.196 +	This document is governed by the <a href="http://www.w3.org/2014/Process-20140801/">1 August 2014 W3C Process Document</a>.
   3.197 +
   3.198 +</p>
   3.199 +   <p>
   3.200 +	The following features are at risk: …
   3.201 +</p></div>
   3.202 +
   3.203 +  <div data-fill-with="at-risk"></div>
   3.204 +
   3.205 +
   3.206 +  <h2 class="no-num no-toc no-ref heading settled" id="contents"><span class="content">Table of Contents</span></h2>
   3.207 +
   3.208 +  <div data-fill-with="table-of-contents" role="navigation">
   3.209 +   <ul class="toc" role="directory">
   3.210 +    <li><a href="#intro"><span class="secno">1</span> <span class="content">
   3.211 +Introduction</span></a>
   3.212 +    <li><a href="#overflow-concepts"><span class="secno">2</span> <span class="content">Types of overflow</span></a>
   3.213 +     <ul class="toc">
   3.214 +      <li><a href="#ink-overflow"><span class="secno">2.1</span> <span class="content">Ink overflow</span></a>
   3.215 +      <li><a href="#scrollable-overflow"><span class="secno">2.2</span> <span class="content">Scrollable overflow</span></a>
   3.216 +      <li><a href="#border-box-overflow"><span class="secno">2.3</span> <span class="content">Border box overflow</span></a>
   3.217 +     </ul>
   3.218 +    <li><a href="#overflow-properties"><span class="secno">3</span> <span class="content">Overflow properties</span></a>
   3.219 +    <li><a href="#scrolling-overflow"><span class="secno">4</span> <span class="content">Scrolling and hidden overflow</span></a>
   3.220 +    <li><a href="#paginated-overflow"><span class="secno">5</span> <span class="content">Paginated overflow</span></a>
   3.221 +    <li><a href="#fragment-overflow"><span class="secno">6</span> <span class="content">Fragment overflow</span></a>
   3.222 +     <ul class="toc">
   3.223 +      <li><a href="#fragment-styling"><span class="secno">6.1</span> <span class="content">Fragment styling</span></a>
   3.224 +       <ul class="toc">
   3.225 +        <li><a href="#fragment-pseudo-element"><span class="secno">6.1.1</span> <span class="content">The ::nth-fragment() pseudo-element</span></a>
   3.226 +        <li><a href="#style-of-fragments"><span class="secno">6.1.2</span> <span class="content">Styling of fragments</span></a>
   3.227 +        <li><a href="#style-in-fragments"><span class="secno">6.1.3</span> <span class="content">Styling inside fragments</span></a>
   3.228 +       </ul>
   3.229 +      <li><a href="#max-lines"><span class="secno">6.2</span> <span class="content">The <span class="property" title="max-lines">max-lines</span> property</span></a>
   3.230 +     </ul>
   3.231 +    <li><a href="#static-media"><span class="secno">7</span> <span class="content">Overflow in static media</span></a>
   3.232 +    <li><a href="#acknowledgments"><span class="secno"></span> <span class="content">
   3.233 +Acknowledgments</span></a>
   3.234 +    <li><a href="#conformance"><span class="secno"></span> <span class="content">
   3.235 +Conformance</span></a>
   3.236 +     <ul class="toc">
   3.237 +      <li><a href="#conventions"><span class="secno"></span> <span class="content">
   3.238 +Document conventions</span></a>
   3.239 +      <li><a href="#conformance-classes"><span class="secno"></span> <span class="content">
   3.240 +Conformance classes</span></a>
   3.241 +      <li><a href="#partial"><span class="secno"></span> <span class="content">
   3.242 +Partial implementations</span></a>
   3.243 +      <li><a href="#experimental"><span class="secno"></span> <span class="content">
   3.244 +Experimental implementations</span></a>
   3.245 +      <li><a href="#testing"><span class="secno"></span> <span class="content">
   3.246 +Non-experimental implementations</span></a>
   3.247 +     </ul>
   3.248 +    <li><a href="#references"><span class="secno"></span> <span class="content">References</span></a>
   3.249 +     <ul class="toc">
   3.250 +      <li><a href="#normative"><span class="secno"></span> <span class="content">Normative References</span></a>
   3.251 +      <li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
   3.252 +     </ul>
   3.253 +    <li><a href="#index"><span class="secno"></span> <span class="content">Index</span></a>
   3.254 +    <li><a href="#property-index"><span class="secno"></span> <span class="content">Property Index</span></a>
   3.255 +    <li><a href="#issues-index"><span class="secno"></span> <span class="content">Issues Index</span></a>
   3.256 +   </ul></div>
   3.257 +
   3.258 +  <main>
   3.259 +
   3.260 +
   3.261 +
   3.262 +
   3.263 +
   3.264 +	
   3.265 +   <p>
   3.266 +	</p>
   3.267 +
   3.268 +
   3.269 +   <h2 class="heading settled" data-level="1" id="intro"><span class="secno">1. </span><span class="content">
   3.270 +Introduction</span><a class="self-link" href="#intro"></a></h2>
   3.271 +
   3.272 +	
   3.273 +   <p>
   3.274 +		In CSS Level 1 <a data-link-type="biblio" href="#biblio-css1">[CSS1]</a>, placing more content than would fit
   3.275 +		inside an element with a specified size
   3.276 +		was generally an authoring error.
   3.277 +		Doing so caused the content to extend
   3.278 +		outside the bounds of the element,
   3.279 +		which would likely cause
   3.280 +		that content to overlap with other elements.
   3.281 +	</p>
   3.282 +
   3.283 +	
   3.284 +   <p>
   3.285 +		CSS Level 2 <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a> introduced the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> property,
   3.286 +		which allows authors to have overflow be handled by scrolling,
   3.287 +		which means it is no longer an authoring error.
   3.288 +		It also allows authors to specify
   3.289 +		that overflow is handled by clipping,
   3.290 +		which makes sense when the author’s intent
   3.291 +		is that the content not be shown.
   3.292 +	</p>
   3.293 +
   3.294 +	
   3.295 +   <p>
   3.296 +		However, scrolling is not the only way
   3.297 +		to present large amounts of content,
   3.298 +		and may even not be the optimal way.
   3.299 +		After all, the codex replaced the scroll
   3.300 +		as the common format for large written works
   3.301 +		because of its advantages.
   3.302 +	</p>
   3.303 +
   3.304 +	
   3.305 +   <p>
   3.306 +		This specification introduces
   3.307 +		a mechanism for Web pages to specify
   3.308 +		that an element of a page should handle overflow
   3.309 +		through pagination rather than through scrolling.
   3.310 +	</p>
   3.311 +
   3.312 +	
   3.313 +   <p>
   3.314 +		This specification also extends the concept of overflow
   3.315 +		in another direction.
   3.316 +		Instead of requiring that authors specify a single area
   3.317 +		into which the content of an element must flow,
   3.318 +		this specification allows authors to specify multiple fragments,
   3.319 +		each with their own dimensions and styles,
   3.320 +		so that the content of the element can flow from one to the next,
   3.321 +		using as many as needed to place the content without overflowing.
   3.322 +	</p>
   3.323 +
   3.324 +	
   3.325 +   <p>
   3.326 +		In both of these cases, implementations must
   3.327 +		break the content in the block-progression dimension.
   3.328 +		Implementations must do this is described
   3.329 +		in the CSS Fragmentation Module <a data-link-type="biblio" href="#biblio-css3-break">[CSS3-BREAK]</a>.
   3.330 +	</p>
   3.331 +
   3.332 +
   3.333 +   <h2 class="heading settled" data-level="2" id="overflow-concepts"><span class="secno">2. </span><span class="content">Types of overflow</span><a class="self-link" href="#overflow-concepts"></a></h2>
   3.334 +
   3.335 +	
   3.336 +   <p>
   3.337 +		CSS uses the term <dfn data-dfn-type="dfn" data-noexport="" id="overflow">overflow<a class="self-link" href="#overflow"></a></dfn> to describe
   3.338 +		the contents of a box
   3.339 +		that extend outside that one of that box’s edges
   3.340 +		(i.e., its <i>content edge</i>, <i>padding edge</i>,
   3.341 +		<i>border edge</i>, or <i>margin edge</i>).
   3.342 +		The overflow might be described as the elements or features
   3.343 +		that cause this overflow,
   3.344 +		the non-rectangular region occupied by these features,
   3.345 +		or, more commonly,
   3.346 +		as the minimal rectangle that bounds that region.
   3.347 +		A box’s overflow is computed based on the boxes and styles
   3.348 +		of the box and of all its descendants whose containing block chain
   3.349 +		<span class="issue" id="issue-18c1c008"><a class="self-link" href="#issue-18c1c008"></a>undefined term?</span>
   3.350 +		includes the box.
   3.351 +	</p>
   3.352 +
   3.353 +	
   3.354 +   <p>
   3.355 +		In most cases, any of these types of overflow
   3.356 +		can be computed for any box
   3.357 +		from the bounds and properties of that box,
   3.358 +		and from the overflow (of that type)
   3.359 +		of each of its children.
   3.360 +		However, this is not always the case; for example,
   3.361 +		when <a class="css" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-transforms-1/#propdef-transform-style">transform-style: preserve-3d</a> <a data-link-type="biblio" href="#biblio-css3-transforms">[CSS3-TRANSFORMS]</a> is used on
   3.362 +		some of the children, their descendants with
   3.363 +		<a class="css" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-transforms-1/#propdef-transform-style">transform-style: preserve-3d</a> must also be examined.
   3.364 +	</p>
   3.365 +
   3.366 +
   3.367 +   <h3 class="heading settled" data-level="2.1" id="ink-overflow"><span class="secno">2.1. </span><span class="content">Ink overflow</span><a class="self-link" href="#ink-overflow"></a></h3>
   3.368 +
   3.369 +	
   3.370 +   <p>
   3.371 +		The <dfn data-dfn-type="dfn" data-noexport="" id="ink-overflow0">ink overflow<a class="self-link" href="#ink-overflow0"></a></dfn> of a box
   3.372 +		is the part of that box and its contents that
   3.373 +		creates a visual effect outside of
   3.374 +		the box’s border box.
   3.375 +	</p>
   3.376 +
   3.377 +	
   3.378 +   <p>
   3.379 +		Since some effects in CSS (for example, the blurs in
   3.380 +		<a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-text-decor-3/#propdef-text-shadow">text-shadow</a> <a data-link-type="biblio" href="#biblio-css3text">[CSS3TEXT]</a> and <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-backgrounds-3/#box-shadow">box-shadow</a> <a data-link-type="biblio" href="#biblio-css3bg">[CSS3BG]</a>)
   3.381 +		do not define what visual extent they cover, the extent
   3.382 +		of the <a data-link-type="dfn" href="#ink-overflow0">ink overflow</a> is undefined.
   3.383 +	</p>
   3.384 +
   3.385 +	
   3.386 +   <p class="issue" id="issue-1baddb1e"><a class="self-link" href="#issue-1baddb1e"></a>
   3.387 +		Should we try to define it at all and just leave pieces undefined?
   3.388 +	</p>
   3.389 +
   3.390 +	
   3.391 +   <p>
   3.392 +		The <dfn data-dfn-type="dfn" data-noexport="" id="ink-overflow-region">ink overflow region<a class="self-link" href="#ink-overflow-region"></a></dfn> is the non-rectangular region
   3.393 +		occupied by the <a data-link-type="dfn" href="#ink-overflow0">ink overflow</a>, and the
   3.394 +		<dfn data-dfn-type="dfn" data-noexport="" id="ink-overflow-rectangle">ink overflow rectangle<a class="self-link" href="#ink-overflow-rectangle"></a></dfn> is
   3.395 +		the minimal rectangle whose axis is aligned to the box’s axes
   3.396 +		and contains the <a data-link-type="dfn" href="#ink-overflow-region">ink overflow region</a>.
   3.397 +		Note that the <a data-link-type="dfn" href="#ink-overflow-rectangle">ink overflow rectangle</a> is a rectangle
   3.398 +		in the box’s coordinate system, but might be non-rectangular
   3.399 +		in other coordinate systems due to transforms <a data-link-type="biblio" href="#biblio-css3-transforms">[CSS3-TRANSFORMS]</a>.
   3.400 +	</p>
   3.401 +
   3.402 +
   3.403 +   <h3 class="heading settled" data-level="2.2" id="scrollable-overflow"><span class="secno">2.2. </span><span class="content">Scrollable overflow</span><a class="self-link" href="#scrollable-overflow"></a></h3>
   3.404 +
   3.405 +	
   3.406 +   <p>
   3.407 +		The <dfn data-dfn-type="dfn" data-noexport="" id="scrollable-overflow0">scrollable overflow<a class="self-link" href="#scrollable-overflow0"></a></dfn> of a box is the
   3.408 +		set of things extending outside of that box’s padding edge
   3.409 +		for which a scrolling mechanism needs to be provided.
   3.410 +	</p>
   3.411 +
   3.412 +	
   3.413 +   <p class="issue" id="issue-36f1a23e"><a class="self-link" href="#issue-36f1a23e"></a>
   3.414 +		The following definition should be rewritten to use
   3.415 +		the concept of <a href="http://dev.w3.org/csswg/css-transforms/#3d-rendering-context">3D rendering context</a> <a data-link-type="biblio" href="#biblio-css3-transforms">[CSS3-TRANSFORMS]</a>
   3.416 +		and related terms,
   3.417 +		particularly once those concepts stabilize following changes
   3.418 +		proposed in the CSS WG meeting on the morning of 2014-01-28.
   3.419 +	</p>
   3.420 +
   3.421 +	
   3.422 +   <p>
   3.423 +		Given the following definitions
   3.424 +		<span class="issue" id="issue-172bf444"><a class="self-link" href="#issue-172bf444"></a>which belong in <a data-link-type="biblio" href="#biblio-css3-transforms">[CSS3-TRANSFORMS]</a></span>:
   3.425 +	</p>
   3.426 +
   3.427 +	
   3.428     <dl>
   3.429 -    <dt>This version:
   3.430 +		
   3.431 +    <dt><dfn data-dfn-type="dfn" data-noexport="" id="3d_preserving-child">3d-preserving child<a class="self-link" href="#3d_preserving-child"></a></dfn>
   3.432 +    
   3.433 +		
   3.434 +    <dd>
   3.435 +			A child box B of a containing block C is a 3d-preserving
   3.436 +			child if it has <a class="css" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-transforms-1/#propdef-transform-style">transform-style: preserve-3d</a>
   3.437 +			and the user-agent is not required to flatten it
   3.438 +			based on the <a href="http://www.w3.org/TR/css3-transforms/#transform-style-property">requirements</a> in <a data-link-type="biblio" href="#biblio-css3-transforms">[CSS3-TRANSFORMS]</a>.
   3.439 +		
   3.440 +		
   3.441 +    <dt><dfn data-dfn-type="dfn" data-noexport="" id="non_3d_preserving-child">non-3d-preserving child<a class="self-link" href="#non_3d_preserving-child"></a></dfn>
   3.442 +    
   3.443 +		
   3.444 +    <dd>
   3.445 +			A child C of a box P is a non-3d-preserving-child if
   3.446 +			it is not a <a data-link-type="dfn" href="#3d_preserving-child">3d-preserving child</a>.
   3.447 +		
   3.448 +    
   3.449 +		
   3.450 +    <dt><dfn data-dfn-type="dfn" data-noexport="" id="3d_preserving-descendant">3d-preserving descendant<a class="self-link" href="#3d_preserving-descendant"></a></dfn>
   3.451 +    
   3.452 +		
   3.453 +    <dd>
   3.454 +			Box D is a 3d-preserving descendant of box A if A is
   3.455 +			an ancestor of D, and D and all of the boxes (if any)
   3.456 +			in the containing block chain from D to A
   3.457 +			are <a data-link-type="dfn" href="#3d_preserving-child">3d-preserving child</a> boxes.
   3.458 +		
   3.459 +    
   3.460 +	
   3.461 +   </dl>
   3.462  
   3.463 -    <dd><a
   3.464 -     href="http://dev.w3.org/csswg/css-overflow-3/">http://dev.w3.org/csswg/css-overflow-3/</a>
   3.465 +	
   3.466 +   <p>The scrollable overflow of a box is the union of the following things,
   3.467 +	all adjusted for transforms <span class="issue" id="issue-1b139c15"><a class="self-link" href="#issue-1b139c15"></a>undefined concept!</span> into the box’s coordinate space:</p>
   3.468  
   3.469 -    <dt>Latest version:
   3.470 +	
   3.471 +   <ul>
   3.472 +		
   3.473 +    <li>
   3.474 +			for the box and all of its <a data-link-type="dfn" href="#3d_preserving-descendant">3d-preserving descendant</a> boxes:
   3.475 +			
   3.476 +     <ul>
   3.477 +				
   3.478 +      <li>the box’s own padding edge (for the box itself) or border edge (for <a data-link-type="dfn" href="#3d_preserving-descendant">3d-preserving descendant</a> boxes)
   3.479 +      
   3.480 +				
   3.481 +      <li>the bounds <span class="issue" id="issue-2d1dc4f9"><a class="self-link" href="#issue-2d1dc4f9"></a>undefined term!</span> of any text directly in the box
   3.482 +      
   3.483 +				
   3.484 +      <li><span class="issue" id="issue-75780f3f"><a class="self-link" href="#issue-75780f3f"></a>MORE HERE!</span>
   3.485 +			
   3.486 +     </ul>
   3.487 +     
   3.488 +		
   3.489 +    <li>
   3.490 +			for all the <a data-link-type="dfn" href="#non_3d_preserving-child">non-3d-preserving child</a> boxes of the
   3.491 +			box and its <a data-link-type="dfn" href="#3d_preserving-descendant">3d-preserving descendant</a> boxes,
   3.492 +			the scrollable overflow of the box
   3.493 +		
   3.494 +    
   3.495 +	
   3.496 +   </ul>
   3.497  
   3.498 -    <dd><a
   3.499 -     href="http://www.w3.org/TR/css-overflow-3/">http://www.w3.org/TR/css-overflow-3/</a>
   3.500 +	
   3.501 +   <p class="issue" id="issue-e889eac0"><a class="self-link" href="#issue-e889eac0"></a>
   3.502 +		I wrote this definition off the top of my head,
   3.503 +		so it can’t possibly be right.
   3.504 +		It’s missing tons of pieces!
   3.505 +	</p>
   3.506  
   3.507 -    <dt>Editor's draft:
   3.508 +	
   3.509 +   <p class="issue" id="issue-521d48c7"><a class="self-link" href="#issue-521d48c7"></a>
   3.510 +		The handling of preserve-3d subtrees here is probably wrong;
   3.511 +		the elements should probably count
   3.512 +		only towards the overflow of the element that flattens them.
   3.513 +	</p>
   3.514  
   3.515 -    <dd><a
   3.516 -     href="http://dev.w3.org/csswg/css-overflow-3/">http://dev.w3.org/csswg/css-overflow-3/</a>
   3.517 -     (<a
   3.518 -     href="https://dvcs.w3.org/hg/csswg/log/tip/css-overflow/Overview.src.html">change
   3.519 -     log</a>, <a
   3.520 -     href="https://dvcs.w3.org/hg/csswg/log/tip/css3-overflow/Overview.src.html">older
   3.521 -     change log</a>)
   3.522 +	
   3.523 +   <p>
   3.524 +		The <dfn data-dfn-type="dfn" data-noexport="" id="scrollable-overflow-region">scrollable overflow region<a class="self-link" href="#scrollable-overflow-region"></a></dfn> is the non-rectangular region
   3.525 +		occupied by the <a data-link-type="dfn" href="#scrollable-overflow0">scrollable overflow</a>, and the
   3.526 +		<dfn data-dfn-type="dfn" data-noexport="" id="scrollable-overflow-rectangle">scrollable overflow rectangle<a class="self-link" href="#scrollable-overflow-rectangle"></a></dfn> is
   3.527 +		the minimal rectangle whose axis is aligned to the box’s axes
   3.528 +		and contains the <a data-link-type="dfn" href="#scrollable-overflow-region">scrollable overflow region</a>.
   3.529 +		Note that the <a data-link-type="dfn" href="#scrollable-overflow-rectangle">scrollable overflow rectangle</a> is a rectangle
   3.530 +		in the box’s coordinate system, but might be non-rectangular
   3.531 +		in other coordinate systems due to transforms <a data-link-type="biblio" href="#biblio-css3-transforms">[CSS3-TRANSFORMS]</a>.
   3.532 +	</p>
   3.533  
   3.534 -    <dt>Previous version:
   3.535  
   3.536 -    <dd><a
   3.537 -     href="http://www.w3.org/TR/2013/WD-css-overflow-3-20130418/">http://www.w3.org/TR/2013/WD-css-overflow-3-20130418/</a>
   3.538 +   <h3 class="heading settled" data-level="2.3" id="border-box-overflow"><span class="secno">2.3. </span><span class="content">Border box overflow</span><a class="self-link" href="#border-box-overflow"></a></h3>
   3.539  
   3.540 -    <dt>Editors:
   3.541 +	
   3.542 +   <p class="issue" id="issue-3930f393"><a class="self-link" href="#issue-3930f393"></a>
   3.543 +		This concept has been proposed for some uses, such as for
   3.544 +		determining what the <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-ui-3/#propdef-outline">outline</a> property goes around, and
   3.545 +		as the basis of a coordinate system for specifying clips and masks,
   3.546 +		but it’s not clear if it’s needed.
   3.547 +	</p>
   3.548  
   3.549 -    <dd class="h-card vcard"> <a class="p-name fn u-url url"
   3.550 -     href="http://dbaron.org/" rel=author>L. David Baron</a>, <a
   3.551 -     class="p-org org" href="http://www.mozilla.org/">Mozilla</a>
   3.552 +	
   3.553 +   <p>
   3.554 +		The <dfn data-dfn-type="dfn" data-noexport="" id="border_box-overflow">border-box overflow<a class="self-link" href="#border_box-overflow"></a></dfn> of a box is the
   3.555 +		union of the box’s border edge and the border edges of
   3.556 +		the box’s descendants.</p>
   3.557 +	
   3.558 +   <p></p>
   3.559  
   3.560 -    <dt>Issue Tracking:
   3.561 +	
   3.562 +   <p class="issue" id="issue-42ea3c29"><a class="self-link" href="#issue-42ea3c29"></a>
   3.563 +		If needed, define more formally, as for scrollable overflow above.
   3.564 +		(Maybe even share the definitions in an appropriate way!)
   3.565 +	</p>
   3.566  
   3.567 -    <dd>Maintained in document (only editor's draft is current)
   3.568 +	
   3.569 +   <p>
   3.570 +		The <dfn data-dfn-type="dfn" data-noexport="" id="border_box-overflow-region">border-box overflow region<a class="self-link" href="#border_box-overflow-region"></a></dfn> is the non-rectangular region
   3.571 +		occupied by the <a data-link-type="dfn" href="#border_box-overflow">border-box overflow</a>, and the
   3.572 +		<dfn data-dfn-type="dfn" data-noexport="" id="border_box-overflow-rectangle">border-box overflow rectangle<a class="self-link" href="#border_box-overflow-rectangle"></a></dfn> is
   3.573 +		the minimal rectangle whose axis is aligned to the box’s axes
   3.574 +		and contains the <a data-link-type="dfn" href="#border_box-overflow-region">border-box overflow region</a>.
   3.575 +		Note that the <a data-link-type="dfn" href="#border_box-overflow-rectangle">border-box overflow rectangle</a> is a rectangle
   3.576 +		in the box’s coordinate system, but might be non-rectangular
   3.577 +		in other coordinate systems due to transforms <a data-link-type="biblio" href="#biblio-css3-transforms">[CSS3-TRANSFORMS]</a>.
   3.578 +	</p>
   3.579  
   3.580 -    <dt>Feedback:
   3.581  
   3.582 -    <dd><a
   3.583 -     href="mailto:[email protected]?subject=%5Bcss-overflow%5D%20feedback">[email protected]</a>
   3.584 -     with subject line “<kbd>[css-overflow] <var>… message topic
   3.585 -     …</var></kbd>” (<a
   3.586 -     href="http://lists.w3.org/Archives/Public/www-style/"
   3.587 -     rel=discussion>archives</a>)
   3.588 +   <h2 class="heading settled" data-level="3" id="overflow-properties"><span class="secno">3. </span><span class="content">Overflow properties</span><a class="self-link" href="#overflow-properties"></a></h2>
   3.589  
   3.590 -    <dt>Test suite:
   3.591 +	
   3.592 +   <p>
   3.593 +		The <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> property specifies
   3.594 +		the handling of overflow in the horizontal direction
   3.595 +		(i.e., overflow from the left and right sides of the box),
   3.596 +		and the <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> property specifies the handling
   3.597 +		of overflow in the vertical direction
   3.598 +		(i.e., overflow from the top and bottom sides of the box) 
   3.599 +	</p>
   3.600  
   3.601 -    <dd>none yet
   3.602 -   </dl>
   3.603 -   <!--begin-copyright-->
   3.604 -   <p class=copyright><a
   3.605 -    href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
   3.606 -    rel=license>Copyright</a> © 2015 <a href="http://www.w3.org/"><abbr
   3.607 -    title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a
   3.608 -    href="http://www.csail.mit.edu/"><abbr
   3.609 -    title="Massachusetts Institute of Technology">MIT</abbr></a>, <a
   3.610 -    href="http://www.ercim.eu/"><abbr
   3.611 -    title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
   3.612 -    <a href="http://www.keio.ac.jp/">Keio</a>, <a
   3.613 -    href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a
   3.614 -    href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
   3.615 -    <a
   3.616 -    href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
   3.617 -    and <a
   3.618 -    href="http://www.w3.org/Consortium/Legal/copyright-documents">document
   3.619 -    use</a> rules apply.</p>
   3.620 -   <!--end-copyright-->
   3.621 -   <hr title="Separator for header">
   3.622 -  </div>
   3.623 -
   3.624 -  <h2 class="no-num no-toc" id=abstract>Abstract</h2>
   3.625 -
   3.626 -  <p> <a href="http://www.w3.org/TR/CSS/">CSS</a> is a language for
   3.627 -   describing the rendering of structured documents (such as HTML and XML) on
   3.628 -   screen, on paper, in speech, etc. This module contains the features of CSS
   3.629 -   relating to new mechanisms of overflow handling in visual media (e.g.,
   3.630 -   screen or paper). In interactive media, it describes features that allow
   3.631 -   the overflow from a fixed size container to be handled by pagination
   3.632 -   (displaying one page at a time). It also describes features, applying to
   3.633 -   all visual media, that allow the contents of an element to be spread
   3.634 -   across multiple fragments, allowing the contents to flow across multiple
   3.635 -   regions or to have different styles for different fragments.
   3.636 -
   3.637 -  <h2 class="no-num no-toc" id=status>Status of this document</h2>
   3.638 -  <!--begin-status-->
   3.639 -
   3.640 -  <p>This is a public copy of the editors' draft. It is provided for
   3.641 -   discussion only and may change at any moment. Its publication here does
   3.642 -   not imply endorsement of its contents by W3C. Don't cite this document
   3.643 -   other than as work in progress.
   3.644 -
   3.645 -  <p>The (<a
   3.646 -   href="http://lists.w3.org/Archives/Public/www-style/">archived</a>) public
   3.647 -   mailing list <a
   3.648 -   href="mailto:[email protected]?Subject=%5Bcss-overflow-3%5D%20PUT%20SUBJECT%20HERE">
   3.649 -   [email protected]</a> (see <a
   3.650 -   href="http://www.w3.org/Mail/Request">instructions</a>) is preferred for
   3.651 -   discussion of this specification. When sending e-mail, please put the text
   3.652 -   “css-overflow-3” in the subject, preferably like this:
   3.653 -   “[<!---->css-overflow-3<!---->] <em>…summary of comment…</em>”
   3.654 -
   3.655 -  <p>This document was produced by the <a
   3.656 -   href="http://www.w3.org/Style/CSS/members">CSS Working Group</a> (part of
   3.657 -   the <a href="http://www.w3.org/Style/">Style Activity</a>).
   3.658 -
   3.659 -  <p>This document was produced by a group operating under the <a
   3.660 -   href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
   3.661 -   2004 W3C Patent Policy</a>. W3C maintains a <a
   3.662 -   href="http://www.w3.org/2004/01/pp-impl/32061/status"
   3.663 -   rel=disclosure>public list of any patent disclosures</a> made in
   3.664 -   connection with the deliverables of the group; that page also includes
   3.665 -   instructions for disclosing a patent. An individual who has actual
   3.666 -   knowledge of a patent which the individual believes contains <a
   3.667 -   href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
   3.668 -   Claim(s)</a> must disclose the information in accordance with <a
   3.669 -   href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
   3.670 -   6 of the W3C Patent Policy</a>.</p>
   3.671 -  <!--end-status-->
   3.672 -
   3.673 -  <p>The following features are at risk: …
   3.674 -
   3.675 -  <h2 class="no-num no-toc" id=contents> Table of contents</h2>
   3.676 -  <!--begin-toc-->
   3.677 -
   3.678 -  <ul class=toc>
   3.679 -   <li><a href="#intro"><span class=secno>1. </span> Introduction</a>
   3.680 -
   3.681 -   <li><a href="#overflow-concepts"><span class=secno>2. </span>Types of
   3.682 -    overflow</a>
   3.683 -    <ul class=toc>
   3.684 -     <li><a href="#ink-overflow"><span class=secno>2.1. </span>Ink
   3.685 -      overflow</a>
   3.686 -
   3.687 -     <li><a href="#scrollable-overflow"><span class=secno>2.2.
   3.688 -      </span>Scrollable overflow</a>
   3.689 -
   3.690 -     <li><a href="#border-box-overflow"><span class=secno>2.3. </span>Border
   3.691 -      box overflow</a>
   3.692 -    </ul>
   3.693 -
   3.694 -   <li><a href="#overflow-properties"><span class=secno>3. </span>Overflow
   3.695 -    properties</a>
   3.696 -
   3.697 -   <li><a href="#scrolling-overflow"><span class=secno>4. </span>Scrolling
   3.698 -    and hidden overflow</a>
   3.699 -
   3.700 -   <li><a href="#paginated-overflow"><span class=secno>5. </span>Paginated
   3.701 -    overflow</a>
   3.702 -
   3.703 -   <li><a href="#fragment-overflow"><span class=secno>6. </span>Fragment
   3.704 -    overflow</a>
   3.705 -    <ul class=toc>
   3.706 -     <li><a href="#fragment-styling"><span class=secno>6.1. </span>Fragment
   3.707 -      styling</a>
   3.708 -      <ul class=toc>
   3.709 -       <li><a href="#fragment-pseudo-element"><span class=secno>6.1.1.
   3.710 -        </span>The ::nth-fragment() pseudo-element</a>
   3.711 -
   3.712 -       <li><a href="#style-of-fragments"><span class=secno>6.1.2.
   3.713 -        </span>Styling of fragments</a>
   3.714 -
   3.715 -       <li><a href="#style-in-fragments"><span class=secno>6.1.3.
   3.716 -        </span>Styling inside fragments</a>
   3.717 -      </ul>
   3.718 -
   3.719 -     <li><a href="#max-lines"><span class=secno>6.2. </span>The ‘<code
   3.720 -      class=property>max-lines</code>’ property</a>
   3.721 -    </ul>
   3.722 -
   3.723 -   <li><a href="#static-media"><span class=secno>7. </span>Overflow in static
   3.724 -    media</a>
   3.725 -
   3.726 -   <li><a href="#conformance"><span class=secno>8. </span> Conformance</a>
   3.727 -    <ul class=toc>
   3.728 -     <li><a href="#placement"><span class=secno>8.1. </span> Module
   3.729 -      interactions</a>
   3.730 -
   3.731 -     <li><a href="#values"><span class=secno>8.2. </span> Values</a>
   3.732 -
   3.733 -     <li><a href="#conventions"><span class=secno>8.3. </span> Document
   3.734 -      conventions</a>
   3.735 -
   3.736 -     <li><a href="#conformance-classes"><span class=secno>8.4. </span>
   3.737 -      Conformance classes</a>
   3.738 -
   3.739 -     <li><a href="#partial"><span class=secno>8.5. </span> Partial
   3.740 -      implementations</a>
   3.741 -
   3.742 -     <li><a href="#experimental"><span class=secno>8.6. </span> Experimental
   3.743 -      implementations</a>
   3.744 -
   3.745 -     <li><a href="#testing"><span class=secno>8.7. </span> Non-experimental
   3.746 -      implementations</a>
   3.747 -
   3.748 -     <li><a href="#cr-exit-criteria"><span class=secno>8.8. </span> CR exit
   3.749 -      criteria</a>
   3.750 -    </ul>
   3.751 -
   3.752 -   <li class=no-num><a href="#acknowledgments"> Acknowledgments</a>
   3.753 -
   3.754 -   <li class=no-num><a href="#references"> References</a>
   3.755 -    <ul class=toc>
   3.756 -     <li class=no-num><a href="#normative-references"> Normative
   3.757 -      references</a>
   3.758 -
   3.759 -     <li class=no-num><a href="#other-references"> Other references</a>
   3.760 -    </ul>
   3.761 -
   3.762 -   <li class=no-num><a href="#index"> Index</a>
   3.763 -
   3.764 -   <li class=no-num><a href="#property-index"> Property index</a>
   3.765 -  </ul>
   3.766 -  <!--end-toc-->
   3.767 -
   3.768 -  <h2 id=intro><span class=secno>1. </span> Introduction</h2>
   3.769 -
   3.770 -  <p> In CSS Level 1 <a href="#ref-CSS1">[CSS1]<!--{{CSS1}}--></a>, placing
   3.771 -   more content than would fit inside an element with a specified size was
   3.772 -   generally an authoring error. Doing so caused the content to extend
   3.773 -   outside the bounds of the element, which would likely cause that content
   3.774 -   to overlap with other elements.
   3.775 -
   3.776 -  <p> CSS Level 2 <a href="#ref-CSS21">[CSS21]<!--{{CSS21}}--></a> introduced
   3.777 -   the ‘<a href="#overflow0"><code class=property>overflow</code></a>’
   3.778 -   property, which allows authors to have overflow be handled by scrolling,
   3.779 -   which means it is no longer an authoring error. It also allows authors to
   3.780 -   specify that overflow is handled by clipping, which makes sense when the
   3.781 -   author's intent is that the content not be shown.
   3.782 -
   3.783 -  <p> However, scrolling is not the only way to present large amounts of
   3.784 -   content, and may even not be the optimal way. After all, the codex
   3.785 -   replaced the scroll as the common format for large written works because
   3.786 -   of its advantages.
   3.787 -
   3.788 -  <p> This specification introduces a mechanism for Web pages to specify that
   3.789 -   an element of a page should handle overflow through pagination rather than
   3.790 -   through scrolling.
   3.791 -
   3.792 -  <p> This specification also extends the concept of overflow in another
   3.793 -   direction. Instead of requiring that authors specify a single area into
   3.794 -   which the content of an element must flow, this specification allows
   3.795 -   authors to specify multiple fragments, each with their own dimensions and
   3.796 -   styles, so that the content of the element can flow from one to the next,
   3.797 -   using as many as needed to place the content without overflowing.
   3.798 -
   3.799 -  <p> In both of these cases, implementations must break the content in the
   3.800 -   block-progression dimension. Implementations must do this is described in
   3.801 -   the CSS Fragmentation Module <a
   3.802 -   href="#ref-CSS3-BREAK">[CSS3-BREAK]<!--{{!CSS3-BREAK}}--></a>.
   3.803 -
   3.804 -  <h2 id=overflow-concepts><span class=secno>2. </span>Types of overflow</h2>
   3.805 -
   3.806 -  <p> CSS uses the term <dfn id=overflow>overflow</dfn> to describe the
   3.807 -   contents of a box that extend outside that one of that box's edges (i.e.,
   3.808 -   its <i>content edge</i>, <i>padding edge</i>, <i>border edge</i>, or
   3.809 -   <i>margin edge</i>). The overflow might be described as the elements or
   3.810 -   features that cause this overflow, the non-rectangular region occupied by
   3.811 -   these features, or, more commonly, as the minimal rectangle that bounds
   3.812 -   that region. A box's overflow is computed based on the boxes and styles of
   3.813 -   the box and of all its descendants whose containing block chain <span
   3.814 -   class=issue>undefined term?</span> includes the box.
   3.815 -
   3.816 -  <p> In most cases, any of these types of overflow can be computed for any
   3.817 -   box from the bounds and properties of that box, and from the overflow (of
   3.818 -   that type) of each of its children. However, this is not always the case;
   3.819 -   for example, when ‘<code class=css>transform-style:
   3.820 -   preserve-3d</code>’ <a
   3.821 -   href="#ref-CSS3-TRANSFORMS">[CSS3-TRANSFORMS]<!--{{CSS3-TRANSFORMS}}--></a>
   3.822 -   is used on some of the children, their descendants with ‘<code
   3.823 -   class=css>transform-style: preserve-3d</code>’ must also be examined.
   3.824 -
   3.825 -  <h3 id=ink-overflow><span class=secno>2.1. </span>Ink overflow</h3>
   3.826 -
   3.827 -  <p> The <dfn id=ink-overflow0>ink overflow</dfn> of a box is the part of
   3.828 -   that box and its contents that creates a visual effect outside of the
   3.829 -   box's border box.
   3.830 -
   3.831 -  <p> Since some effects in CSS (for example, the blurs in ‘<code
   3.832 -   class=property>text-shadow</code>’ <a
   3.833 -   href="#ref-CSS-TEXT-3">[CSS-TEXT-3]<!--{{CSS-TEXT-3}}--></a> and ‘<code
   3.834 -   class=property>box-shadow</code>’ <a
   3.835 -   href="#ref-CSS3BG">[CSS3BG]<!--{{CSS3BG}}--></a>) do not define what
   3.836 -   visual extent they cover, the extent of the <a
   3.837 -   href="#ink-overflow0"><i>ink overflow</i></a> is undefined.
   3.838 -
   3.839 -  <p class=issue> Should we try to define it at all and just leave pieces
   3.840 -   undefined?
   3.841 -
   3.842 -  <p> The <dfn id=ink-overflow-region>ink overflow region</dfn> is the
   3.843 -   non-rectangular region occupied by the <a href="#ink-overflow0"><i>ink
   3.844 -   overflow</i></a>, and the <dfn id=ink-overflow-rectangle>ink overflow
   3.845 -   rectangle</dfn> is the minimal rectangle whose axis is aligned to the
   3.846 -   box's axes and contains the <a href="#ink-overflow-region"><i>ink overflow
   3.847 -   region</i></a>. Note that the <a href="#ink-overflow-rectangle"><i>ink
   3.848 -   overflow rectangle</i></a> is a rectangle in the box's coordinate system,
   3.849 -   but might be non-rectangular in other coordinate systems due to transforms
   3.850 -   <a
   3.851 -   href="#ref-CSS3-TRANSFORMS">[CSS3-TRANSFORMS]<!--{{CSS3-TRANSFORMS}}--></a>.
   3.852 -
   3.853 -  <h3 id=scrollable-overflow><span class=secno>2.2. </span>Scrollable
   3.854 -   overflow</h3>
   3.855 -
   3.856 -  <p> The <dfn id=scrollable-overflow0>scrollable overflow</dfn> of a box is
   3.857 -   the set of things extending outside of that box's padding edge for which a
   3.858 -   scrolling mechanism needs to be provided.
   3.859 -
   3.860 -  <p class=issue> The following definition should be rewritten to use the
   3.861 -   concept of <a
   3.862 -   href="http://dev.w3.org/csswg/css-transforms/#3d-rendering-context">3D
   3.863 -   rendering context</a> <a
   3.864 -   href="#ref-CSS3-TRANSFORMS">[CSS3-TRANSFORMS]<!--{{!CSS3-TRANSFORMS}}--></a>
   3.865 -   and related terms, particularly once those concepts stabilize following
   3.866 -   changes proposed in the CSS WG meeting on the morning of 2014-01-28.
   3.867 -
   3.868 -  <p> Given the following definitions <span class=issue>which belong in <a
   3.869 -   href="#ref-CSS3-TRANSFORMS">[CSS3-TRANSFORMS]<!--{{CSS3-TRANSFORMS}}--></a></span>:
   3.870 -
   3.871 -  <dl>
   3.872 -   <dt><dfn id=d-preserving-child>3d-preserving child</dfn>
   3.873 -
   3.874 -   <dd> A child box B of a containing block C is a 3d-preserving child if it
   3.875 -    has ‘<code class=css>transform-style: preserve-3d</code>’ and the
   3.876 -    user-agent is not required to flatten it based on the <a
   3.877 -    href="http://www.w3.org/TR/css3-transforms/#transform-style-property">requirements</a>
   3.878 -    in <a
   3.879 -    href="#ref-CSS3-TRANSFORMS">[CSS3-TRANSFORMS]<!--{{!CSS3-TRANSFORMS}}--></a>.
   3.880 -
   3.881 -   <dt><dfn id=non-3d-preserving-child>non-3d-preserving child</dfn>
   3.882 -
   3.883 -   <dd> A child C of a box P is a non-3d-preserving-child if it is not a <a
   3.884 -    href="#d-preserving-child"><i>3d-preserving child</i></a>.
   3.885 -
   3.886 -   <dt><dfn id=d-preserving-descendant>3d-preserving descendant</dfn>
   3.887 -
   3.888 -   <dd> Box D is a 3d-preserving descendant of box A if A is an ancestor of
   3.889 -    D, and D and all of the boxes (if any) in the containing block chain from
   3.890 -    D to A are <a href="#d-preserving-child"><i>3d-preserving child</i></a>
   3.891 -    boxes.
   3.892 -  </dl>
   3.893 -
   3.894 -  <p>The scrollable overflow of a box is the union of the following things,
   3.895 -   all adjusted for transforms <span class=issue>undefined concept!</span>
   3.896 -   into the box's coordinate space:
   3.897 -
   3.898 -  <ul>
   3.899 -   <li> for the box and all of its <a
   3.900 -    href="#d-preserving-descendant"><i>3d-preserving descendant</i></a>
   3.901 -    boxes:
   3.902 -    <ul>
   3.903 -     <li>the box's own padding edge (for the box itself) or border edge (for
   3.904 -      <a href="#d-preserving-descendant"><i>3d-preserving descendant</i></a>
   3.905 -      boxes)
   3.906 -
   3.907 -     <li>the bounds <span class=issue>undefined term!</span> of any text
   3.908 -      directly in the box
   3.909 -
   3.910 -     <li><span class=issue>MORE HERE!</span>
   3.911 -    </ul>
   3.912 -
   3.913 -   <li> for all the <a href="#non-3d-preserving-child"><i>non-3d-preserving
   3.914 -    child</i></a> boxes of the box and its <a
   3.915 -    href="#d-preserving-descendant"><i>3d-preserving descendant</i></a>
   3.916 -    boxes, the scrollable overflow of the box
   3.917 -  </ul>
   3.918 -
   3.919 -  <p class=issue> I wrote this definition off the top of my head, so it can't
   3.920 -   possibly be right. It's missing tons of pieces!
   3.921 -
   3.922 -  <p class=issue> The handling of preserve-3d subtrees here is probably
   3.923 -   wrong; the elements should probably count only towards the overflow of the
   3.924 -   element that flattens them.
   3.925 -
   3.926 -  <p> The <dfn id=scrollable-overflow-region>scrollable overflow region</dfn>
   3.927 -   is the non-rectangular region occupied by the <a
   3.928 -   href="#scrollable-overflow0"><i>scrollable overflow</i></a>, and the <dfn
   3.929 -   id=scrollable-overflow-rectangle>scrollable overflow rectangle</dfn> is
   3.930 -   the minimal rectangle whose axis is aligned to the box's axes and contains
   3.931 -   the <a href="#scrollable-overflow-region"><i>scrollable overflow
   3.932 -   region</i></a>. Note that the <a
   3.933 -   href="#scrollable-overflow-rectangle"><i>scrollable overflow
   3.934 -   rectangle</i></a> is a rectangle in the box's coordinate system, but might
   3.935 -   be non-rectangular in other coordinate systems due to transforms <a
   3.936 -   href="#ref-CSS3-TRANSFORMS">[CSS3-TRANSFORMS]<!--{{CSS3-TRANSFORMS}}--></a>.
   3.937 -
   3.938 -  <h3 id=border-box-overflow><span class=secno>2.3. </span>Border box
   3.939 -   overflow</h3>
   3.940 -
   3.941 -  <p class=issue> This concept has been proposed for some uses, such as for
   3.942 -   determining what the ‘<code class=property>outline</code>’ property
   3.943 -   goes around, and as the basis of a coordinate system for specifying clips
   3.944 -   and masks, but it's not clear if it's needed.
   3.945 -
   3.946 -  <p> The <dfn id=border-box-overflow0>border-box overflow</dfn> of a box is
   3.947 -   the union of the box's border edge and the border edges of the box's
   3.948 -   descendants.
   3.949 -
   3.950 -  <p class=issue> If needed, define more formally, as for scrollable overflow
   3.951 -   above. (Maybe even share the definitions in an appropriate way!)
   3.952 -
   3.953 -  <p> The <dfn id=border-box-overflow-region>border-box overflow region</dfn>
   3.954 -   is the non-rectangular region occupied by the <a
   3.955 -   href="#border-box-overflow0"><i>border-box overflow</i></a>, and the <dfn
   3.956 -   id=border-box-overflow-rectangle>border-box overflow rectangle</dfn> is
   3.957 -   the minimal rectangle whose axis is aligned to the box's axes and contains
   3.958 -   the <a href="#border-box-overflow-region"><i>border-box overflow
   3.959 -   region</i></a>. Note that the <a
   3.960 -   href="#border-box-overflow-rectangle"><i>border-box overflow
   3.961 -   rectangle</i></a> is a rectangle in the box's coordinate system, but might
   3.962 -   be non-rectangular in other coordinate systems due to transforms <a
   3.963 -   href="#ref-CSS3-TRANSFORMS">[CSS3-TRANSFORMS]<!--{{CSS3-TRANSFORMS}}--></a>.
   3.964 -
   3.965 -  <h2 id=overflow-properties><span class=secno>3. </span>Overflow properties</h2>
   3.966 -
   3.967 -  <p> The ‘<a href="#overflow-x"><code
   3.968 -   class=property>overflow-x</code></a>’ property specifies the handling of
   3.969 -   overflow in the horizontal direction (i.e., overflow from the left and
   3.970 -   right sides of the box), and the ‘<a href="#overflow-y"><code
   3.971 -   class=property>overflow-y</code></a>’ property specifies the handling of
   3.972 -   overflow in the vertical direction (i.e., overflow from the top and bottom
   3.973 -   sides of the box)
   3.974 -
   3.975 -  <table class=propdef>
   3.976 -   <tbody>
   3.977 -    <tr>
   3.978 -     <th>Name:
   3.979 -
   3.980 -     <td><dfn id=overflow-x>overflow-x</dfn>, <dfn
   3.981 -      id=overflow-y>overflow-y</dfn>
   3.982 -
   3.983 -    <tr>
   3.984 -     <th><a href="#values">Value</a>:
   3.985 -
   3.986 -     <td>visible | hidden | scroll | auto | paged-x | paged-y |
   3.987 -      paged-x-controls | paged-y-controls | fragments
   3.988 -
   3.989 -    <tr>
   3.990 -     <th>Initial:
   3.991 -
   3.992 -     <td>visible
   3.993 -
   3.994 -    <tr>
   3.995 -     <th>Applies to:
   3.996 -
   3.997 -     <td>block containers <a href="#ref-CSS21">[CSS21]<!--{{!CSS21}}--></a>,
   3.998 -      flex containers <a
   3.999 -      href="#ref-CSS3-FLEXBOX">[CSS3-FLEXBOX]<!--{{!CSS3-FLEXBOX}}--></a>,
  3.1000 -      and grid containers <a
  3.1001 -      href="#ref-CSS-GRID-1">[CSS-GRID-1]<!--{{!CSS-GRID-1}}--></a>
  3.1002 -
  3.1003 -    <tr>
  3.1004 -     <th>Inherited:
  3.1005 -
  3.1006 -     <td>no
  3.1007 -
  3.1008 -    <tr>
  3.1009 -     <th>Percentages:
  3.1010 -
  3.1011 -     <td>N/A
  3.1012 -
  3.1013 -    <tr>
  3.1014 -     <th>Media:
  3.1015 -
  3.1016 -     <td>visual
  3.1017 -
  3.1018 -    <tr>
  3.1019 -     <th>Computed value:
  3.1020 -
  3.1021 -     <td>see below
  3.1022 -
  3.1023 -    <tr>
  3.1024 -     <th>Animatable:
  3.1025 -
  3.1026 -     <td>no
  3.1027 -
  3.1028 -    <tr>
  3.1029 -     <th>Canonical order:
  3.1030 -
  3.1031 -     <td><abbr title="follows order of property value definition">per
  3.1032 -      grammar</abbr>
  3.1033 -  </table>
  3.1034 -
  3.1035 -  <p> The ‘<a href="#overflow0"><code class=property>overflow</code></a>’
  3.1036 -   property is a shorthand property that sets the specified values of both
  3.1037 -   ‘<a href="#overflow-x"><code class=property>overflow-x</code></a>’ and
  3.1038 -   ‘<a href="#overflow-y"><code class=property>overflow-y</code></a>’ to
  3.1039 -   the value specified for ‘<a href="#overflow0"><code
  3.1040 -   class=property>overflow</code></a>’.
  3.1041 -
  3.1042 -  <table class=propdef>
  3.1043 -   <tbody>
  3.1044 -    <tr>
  3.1045 -     <th>Name:
  3.1046 -
  3.1047 -     <td><dfn id=overflow0>overflow</dfn>
  3.1048 -
  3.1049 -    <tr>
  3.1050 -     <th><a href="#values">Value</a>:
  3.1051 -
  3.1052 -     <td>visible | hidden | scroll | auto | paged-x | paged-y |
  3.1053 -      paged-x-controls | paged-y-controls | fragments
  3.1054 -
  3.1055 -    <tr>
  3.1056 -     <th>Initial:
  3.1057 -
  3.1058 -     <td>see individual properties
  3.1059 -
  3.1060 -    <tr>
  3.1061 -     <th>Applies to:
  3.1062 -
  3.1063 -     <td>block containers <a href="#ref-CSS21">[CSS21]<!--{{!CSS21}}--></a>,
  3.1064 -      flex containers <a
  3.1065 -      href="#ref-CSS3-FLEXBOX">[CSS3-FLEXBOX]<!--{{!CSS3-FLEXBOX}}--></a>,
  3.1066 -      and grid containers <a
  3.1067 -      href="#ref-CSS-GRID-1">[CSS-GRID-1]<!--{{!CSS-GRID-1}}--></a>
  3.1068 -
  3.1069 -    <tr>
  3.1070 -     <th>Inherited:
  3.1071 -
  3.1072 -     <td>no
  3.1073 -
  3.1074 -    <tr>
  3.1075 -     <th>Percentages:
  3.1076 -
  3.1077 -     <td>N/A
  3.1078 -
  3.1079 -    <tr>
  3.1080 -     <th>Media:
  3.1081 -
  3.1082 -     <td>visual
  3.1083 -
  3.1084 -    <tr>
  3.1085 -     <th>Computed value:
  3.1086 -
  3.1087 -     <td>see individual properties
  3.1088 -
  3.1089 -    <tr>
  3.1090 -     <th>Animatable:
  3.1091 -
  3.1092 -     <td>no
  3.1093 -
  3.1094 -    <tr>
  3.1095 -     <th>Canonical order:
  3.1096 -
  3.1097 -     <td><abbr title="follows order of property value definition">per
  3.1098 -      grammar</abbr>
  3.1099 -  </table>
  3.1100 -
  3.1101 -  <p>The values of these properties are:
  3.1102 -
  3.1103 -  <dl>
  3.1104 -   <dt><dfn id=visible>visible</dfn>
  3.1105 -
  3.1106 -   <dd> There is no special handling of overflow, that is, it may be rendered
  3.1107 -    outside the block container.
  3.1108 -
  3.1109 -   <dt><dfn id=hidden>hidden</dfn>
  3.1110 -
  3.1111 -   <dt><dfn id=scroll>scroll</dfn>
  3.1112 -
  3.1113 -   <dt><dfn id=auto>auto</dfn>
  3.1114 -
  3.1115 -   <dd> These values are collectively the <dfn id=scrolling-values>scrolling
  3.1116 -    values</dfn>; they are defined in the section on <a
  3.1117 -    href="#scrolling-overflow">scrolling and hidden overflow</a>.
  3.1118 -
  3.1119 -   <dt><dfn id=paged-x>paged-x</dfn>
  3.1120 -
  3.1121 -   <dt><dfn id=paged-y>paged-y</dfn>
  3.1122 -
  3.1123 -   <dt><dfn id=paged-x-controls>paged-x-controls</dfn>
  3.1124 -
  3.1125 -   <dt><dfn id=paged-y-controls>paged-y-controls</dfn>
  3.1126 -
  3.1127 -   <dt><dfn id=fragments>fragments</dfn>
  3.1128 -
  3.1129 -   <dd> These values are collectively the <dfn
  3.1130 -    id=fragmenting-values>fragmenting values</dfn>; they are defined in the
  3.1131 -    sections on <a href="#paginated-overflow">paginated overflow</a> and <a
  3.1132 -    href="#fragment-overflow">fragment overflow</a>.
  3.1133 -  </dl>
  3.1134 -
  3.1135 -  <div id=overflow-computed-values>
  3.1136 -   <p>The computed values of ‘<a href="#overflow-x"><code
  3.1137 -    class=property>overflow-x</code></a>’ and ‘<a
  3.1138 -    href="#overflow-y"><code class=property>overflow-y</code></a>’ are
  3.1139 -    determined from the cascaded values <a
  3.1140 -    href="#ref-CSS3CASCADE">[CSS3CASCADE]<!--{{!CSS3CASCADE}}--></a> based on
  3.1141 -    the following rules:
  3.1142 -
  3.1143 -   <ol>
  3.1144 -    <li> If one or both of the cascaded values are <a
  3.1145 -     href="#fragmenting-values"><i>fragmenting values</i></a>, then:
  3.1146 -     <ol>
  3.1147 -      <li> If one of the cascaded values is one of the <a
  3.1148 -       href="#fragmenting-values"><i>fragmenting values</i></a> and the other
  3.1149 -       is not, then the computed values are the same as the cascaded values.
  3.1150 -
  3.1151 -      <li> If both of the cascaded values are <a
  3.1152 -       href="#fragmenting-values"><i>fragmenting values</i></a>, then:
  3.1153 -       <ol>
  3.1154 -        <li> for horizontal writing mode <a
  3.1155 -         href="#ref-CSS-WRITING-MODES-3">[CSS-WRITING-MODES-3]<!--{{!CSS-WRITING-MODES-3}}--></a>,
  3.1156 -         the computed value for ‘<a href="#overflow-y"><code
  3.1157 -         class=property>overflow-y</code></a>’ is the cascaded value and
  3.1158 -         the computed value for ‘<a href="#overflow-x"><code
  3.1159 -         class=property>overflow-x</code></a>’ is ‘<a
  3.1160 -         href="#hidden"><code class=css>hidden</code></a>’, or
  3.1161 -
  3.1162 -        <li> for vertical writing mode <a
  3.1163 -         href="#ref-CSS-WRITING-MODES-3">[CSS-WRITING-MODES-3]<!--{{!CSS-WRITING-MODES-3}}--></a>,
  3.1164 -         the computed value for ‘<a href="#overflow-x"><code
  3.1165 -         class=property>overflow-x</code></a>’ is the cascaded value and
  3.1166 -         the computed value for ‘<a href="#overflow-y"><code
  3.1167 -         class=property>overflow-y</code></a>’ is ‘<a
  3.1168 -         href="#hidden"><code class=css>hidden</code></a>’.
  3.1169 -       </ol>
  3.1170 -     </ol>
  3.1171 -
  3.1172 -    <li> Otherwise, if one cascaded values is one of the <a
  3.1173 -     href="#scrolling-values"><i>scrolling values</i></a> and the other is
  3.1174 -     ‘<a href="#visible"><code class=css>visible</code></a>’, then
  3.1175 -     computed values are the cascaded values with ‘<a href="#visible"><code
  3.1176 -     class=css>visible</code></a>’ changed to ‘<a href="#auto"><code
  3.1177 -     class=css>auto</code></a>’.
  3.1178 -
  3.1179 -    <li> Otherwise, the computed values are as specified.
  3.1180 -   </ol>
  3.1181 -  </div>
  3.1182 -
  3.1183 -  <p class=issue> Are all 4 of the ‘<code class=css>paged-*</code>’
  3.1184 -   values really needed?
  3.1185 -
  3.1186 -  <p> When the <a href="#fragmenting-values"><i>fragmenting values</i></a>
  3.1187 -   are used, the overflow from the fragments themselves treats the
  3.1188 -   fragmenting value as ‘<a href="#hidden"><code
  3.1189 -   class=css>hidden</code></a>’. <span class=issue>Is this the right
  3.1190 -   behavior?</span> <span class=issue>Give example.</span>
  3.1191 -
  3.1192 -  <p class=issue> <a
  3.1193 -   href="#ref-CSS3-MARQUEE">[CSS3-MARQUEE]<!--{{CSS3-MARQUEE}}--></a>
  3.1194 -   describes an ‘<code class=property>overflow-style</code>’ property,
  3.1195 -   but it has not picked up implementation experience that the working group
  3.1196 -   is aware of. Should this document treat ‘<code
  3.1197 -   class=property>overflow-style</code>’ as a defunct proposal, or should
  3.1198 -   this document describe the ‘<code
  3.1199 -   class=property>overflow-style</code>’ property and attempt to revive it,
  3.1200 -   despite that implementations have implemented ‘<a
  3.1201 -   href="#overflow-x"><code class=property>overflow-x</code></a>’ and ‘<a
  3.1202 -   href="#overflow-y"><code class=property>overflow-y</code></a>’ instead?
  3.1203 -
  3.1204 -  <p class=issue> There are <a
  3.1205 -   href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussions</a>
  3.1206 -   about how overflow, overflow-style, overflow-x and overflow-y should work
  3.1207 -   and interact with each other. Until consensus on this topic is reached, it
  3.1208 -   is not completely clear which of these should be used for paged-x |
  3.1209 -   paged-y | paged-x-controls | paged-y-controls | fragments
  3.1210 -
  3.1211 -  <h2 id=scrolling-overflow><span class=secno>4. </span>Scrolling and hidden
  3.1212 -   overflow</h2>
  3.1213 -
  3.1214 -  <p class=issue> Move material from <a
  3.1215 -   href="#ref-CSS21">[CSS21]<!--{{CSS21}}--></a> and <a
  3.1216 -   href="#ref-CSS3BOX">[CSS3BOX]<!--{{CSS3BOX}}--></a> here.
  3.1217 -
  3.1218 -  <p class=issue> Explain which directions allow scrolling and which don't,
  3.1219 -   as a function of ‘<code class=property>direction</code>’ (including
  3.1220 -   propagation of ‘<code class=property>direction</code>’ to the ICB).
  3.1221 -
  3.1222 -  <h2 id=paginated-overflow><span class=secno>5. </span>Paginated overflow</h2>
  3.1223 -
  3.1224 -  <p class=issue>overflow:paginate or overflow:pages (or paged-x, paged-y,
  3.1225 -   paged-x-controls, paged-y-controls as <a
  3.1226 -   href="#ref-CSS3GCPM">[CSS3GCPM]<!--{{CSS3GCPM}}--></a> has?)
  3.1227 -
  3.1228 -  <p class=issue>Ability to display N pages at once rather than just one page
  3.1229 -   at once?
  3.1230 -
  3.1231 -  <p class=issue> The current implementation of paginated overflow uses the
  3.1232 -   ‘<a href="#overflow0"><code class=property>overflow</code></a>’/‘<a
  3.1233 -   href="#overflow-x"><code class=property>overflow-x</code></a>’/‘<a
  3.1234 -   href="#overflow-y"><code class=property>overflow-y</code></a>’
  3.1235 -   properties rather than the ‘<code
  3.1236 -   class=property>overflow-style</code>’ property as proposed in the <a
  3.1237 -   href="#ref-CSS3GCPM">[CSS3GCPM]<!--{{CSS3GCPM}}--></a> draft (which also
  3.1238 -   matches the <a
  3.1239 -   href="#ref-CSS3-MARQUEE">[CSS3-MARQUEE]<!--{{CSS3-MARQUEE}}--></a>
  3.1240 -   proposal). We should probably switch away from ‘<code
  3.1241 -   class=property>overflow-style</code>’, but that's not 100% clear.
  3.1242 -
  3.1243 -  <h2 id=fragment-overflow><span class=secno>6. </span>Fragment overflow</h2>
  3.1244 -
  3.1245 -  <p> This section introduces and defines the meaning of the new ‘<a
  3.1246 -   href="#fragments"><code class=css>fragments</code></a>’ value of the
  3.1247 -   ‘<a href="#overflow0"><code class=property>overflow</code></a>’
  3.1248 -   property.
  3.1249 -
  3.1250 -  <p> When the computed value of ‘<a href="#overflow0"><code
  3.1251 -   class=property>overflow</code></a>’ for an element is ‘<a
  3.1252 -   href="#fragments"><code class=css>fragments</code></a>’, and
  3.1253 -   implementations would otherwise have created a box for the element, then
  3.1254 -   implementations must create a sequence of <dfn id=fragment-box>fragment
  3.1255 -   box</dfn>es for that element. (It is possible for an element with ‘<code
  3.1256 -   class=css>overflow: fragments</code>’ to generate only one <a
  3.1257 -   href="#fragment-box"><i>fragment box</i></a>. However, if an element's
  3.1258 -   computed ‘<a href="#overflow0"><code
  3.1259 -   class=property>overflow</code></a>’ is not ‘<a href="#fragments"><code
  3.1260 -   class=css>fragments</code></a>’, then its box is not a <a
  3.1261 -   href="#fragment-box"><i>fragment box</i></a>.) Every <a
  3.1262 -   href="#fragment-box"><i>fragment box</i></a> is a fragmentation container,
  3.1263 -   and any overflow that would cause that fragmentation container to fragment
  3.1264 -   causes another <a href="#fragment-box"><i>fragment box</i></a> created as
  3.1265 -   a next sibling of the previous one. <span class=issue>Or is it as though
  3.1266 -   it's a next sibling of the element? Need to figure out exactly how this
  3.1267 -   interacts with other box-level fixup.</span> Additionally, if the <a
  3.1268 -   href="#fragment-box"><i>fragment box</i></a> is also a multi-column box
  3.1269 -   (as defined in <a href="#ref-CSS3COL">[CSS3COL]<!--{{!CSS3COL}}--></a>
  3.1270 -   <span class=issue>though it defines <i>multi-column element</i></span>)
  3.1271 -   any content that would lead to the creation of <i>overflow columns</i> <a
  3.1272 -   href="#ref-CSS3COL">[CSS3COL]<!--{{!CSS3COL}}--></a> instead is flown into
  3.1273 -   an additional fragment box. However, fragment boxes may themselves be
  3.1274 -   broken (due to fragmentation in a fragmentation context outside of them,
  3.1275 -   such as pages, columns, or other fragment boxes); such breaking leads to
  3.1276 -   fragments of the same fragment box rather than multiple fragment boxes.
  3.1277 -   (This matters because fragment boxes may be styled by their index; such
  3.1278 -   breaking leads to multiple fragments of a fragment box with a single
  3.1279 -   index. This design choice is so that breaking a fragment box across pages
  3.1280 -   does not break the association of indices to particular pieces of
  3.1281 -   content.) <span class=issue>Should a forced break that breaks to an outer
  3.1282 -   fragmentation context cause a new fragment of a single fragment box or a
  3.1283 -   new fragment box?</span> <span class=issue>Should we find a term other
  3.1284 -   than <a href="#fragment-box"><i>fragment box</i></a> here to make this a
  3.1285 -   little less confusing?</span>
  3.1286 -
  3.1287 -  <p class=issue> What if we want to be able to style the pieces of an
  3.1288 -   element split within another type of fragmentation context? These rules
  3.1289 -   prevent ever using ‘<code class=css>::nth-fragment()</code>’ for that,
  3.1290 -   despite that the name seems the most logical name for such a feature.
  3.1291 -
  3.1292 -  <div class=example>
  3.1293 -   <table class=source-demo-pair>
  3.1294 +	
  3.1295 +   <table class="propdef">
  3.1296 +		
  3.1297      <tbody>
  3.1298       <tr>
  3.1299 -      <td>
  3.1300 -       <pre>&lt;!DOCTYPE HTML&gt;
  3.1301 -&lt;title&gt;Breaking content into
  3.1302 -  equal-sized cards&lt;/title&gt;
  3.1303 -&lt;style&gt;
  3.1304 +			
  3.1305 +      <th>Name:
  3.1306 +			
  3.1307 +      <td><dfn class="css" data-dfn-type="property" data-export="" id="propdef-overflow-x">overflow-x<a class="self-link" href="#propdef-overflow-x"></a></dfn>, <dfn class="css" data-dfn-type="property" data-export="" id="propdef-overflow-y">overflow-y<a class="self-link" href="#propdef-overflow-y"></a></dfn>
  3.1308 +     <tr>
  3.1309 +			
  3.1310 +      <th>Value:
  3.1311 +			
  3.1312 +      <td>visible | hidden | scroll | auto | paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
  3.1313 +		
  3.1314 +     <tr>
  3.1315 +			
  3.1316 +      <th>Initial:
  3.1317 +			
  3.1318 +      <td>visible
  3.1319 +		
  3.1320 +     <tr>
  3.1321 +			
  3.1322 +      <th>Applies to:
  3.1323 +			
  3.1324 +      <td>block containers <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a>, flex containers <a data-link-type="biblio" href="#biblio-css3-flexbox">[CSS3-FLEXBOX]</a>, and grid containers <a data-link-type="biblio" href="#biblio-css3-grid-layout">[CSS3-GRID-LAYOUT]</a>
  3.1325 +		
  3.1326 +     <tr>
  3.1327 +			
  3.1328 +      <th>Inherited:
  3.1329 +			
  3.1330 +      <td>no
  3.1331 +		
  3.1332 +     <tr>
  3.1333 +			
  3.1334 +      <th>Percentages:
  3.1335 +			
  3.1336 +      <td>N/A
  3.1337 +		
  3.1338 +     <tr>
  3.1339 +			
  3.1340 +      <th>Media:
  3.1341 +			
  3.1342 +      <td>visual
  3.1343 +		
  3.1344 +     <tr>
  3.1345 +			
  3.1346 +      <th>Computed value:
  3.1347 +			
  3.1348 +      <td>see below
  3.1349 +		
  3.1350 +     <tr>
  3.1351 +			
  3.1352 +      <th>Animatable:
  3.1353 +			
  3.1354 +      <td>no
  3.1355 +		
  3.1356 +     <tr>
  3.1357 +			
  3.1358 +      <th>Canonical order:
  3.1359 +			
  3.1360 +      <td><abbr title="follows order of property value definition">per grammar</abbr>
  3.1361 +	
  3.1362 +   </table>
  3.1363 +
  3.1364 +	
  3.1365 +   <p>
  3.1366 +		The <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> property is a shorthand property
  3.1367 +		that sets the specified values of both <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> and <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>
  3.1368 +		to the value specified for <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>.
  3.1369 +	</p>
  3.1370 +
  3.1371 +	
  3.1372 +   <table class="propdef">
  3.1373 +		
  3.1374 +    <tbody>
  3.1375 +     <tr>
  3.1376 +			
  3.1377 +      <th>Name:
  3.1378 +			
  3.1379 +      <td><dfn class="css" data-dfn-type="property" data-export="" id="propdef-overflow">overflow<a class="self-link" href="#propdef-overflow"></a></dfn>
  3.1380 +     <tr>
  3.1381 +			
  3.1382 +      <th>Value:
  3.1383 +			
  3.1384 +      <td>visible | hidden | scroll | auto | paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
  3.1385 +		
  3.1386 +     <tr>
  3.1387 +			
  3.1388 +      <th>Initial:
  3.1389 +			
  3.1390 +      <td>see individual properties
  3.1391 +		
  3.1392 +     <tr>
  3.1393 +			
  3.1394 +      <th>Applies to:
  3.1395 +			
  3.1396 +      <td>block containers <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a>, flex containers <a data-link-type="biblio" href="#biblio-css3-flexbox">[CSS3-FLEXBOX]</a>, and grid containers <a data-link-type="biblio" href="#biblio-css3-grid-layout">[CSS3-GRID-LAYOUT]</a>
  3.1397 +		
  3.1398 +     <tr>
  3.1399 +			
  3.1400 +      <th>Inherited:
  3.1401 +			
  3.1402 +      <td>no
  3.1403 +		
  3.1404 +     <tr>
  3.1405 +			
  3.1406 +      <th>Percentages:
  3.1407 +			
  3.1408 +      <td>N/A
  3.1409 +		
  3.1410 +     <tr>
  3.1411 +			
  3.1412 +      <th>Media:
  3.1413 +			
  3.1414 +      <td>visual
  3.1415 +		
  3.1416 +     <tr>
  3.1417 +			
  3.1418 +      <th>Computed value:
  3.1419 +			
  3.1420 +      <td>see individual properties
  3.1421 +		
  3.1422 +     <tr>
  3.1423 +			
  3.1424 +      <th>Animatable:
  3.1425 +			
  3.1426 +      <td>no
  3.1427 +		
  3.1428 +     <tr>
  3.1429 +			
  3.1430 +      <th>Canonical order:
  3.1431 +			
  3.1432 +      <td><abbr title="follows order of property value definition">per grammar</abbr>
  3.1433 +	
  3.1434 +   </table>
  3.1435 +
  3.1436 +	
  3.1437 +   <p>The values of these properties are:</p>
  3.1438 +
  3.1439 +	
  3.1440 +   <dl>
  3.1441 +		
  3.1442 +    <dt><dfn class="css" data-dfn-for="overflow" data-dfn-type="value" data-export="" id="valdef-overflow-visible">visible<a class="self-link" href="#valdef-overflow-visible"></a></dfn>
  3.1443 +		
  3.1444 +    <dd>
  3.1445 +			There is no special handling of overflow, that is, it
  3.1446 +			may be rendered outside the block container.
  3.1447 +		
  3.1448 +    
  3.1449 +		
  3.1450 +    <dt><dfn class="css" data-dfn-for="overflow" data-dfn-type="value" data-export="" id="valdef-overflow-hidden">hidden<a class="self-link" href="#valdef-overflow-hidden"></a></dfn>
  3.1451 +		
  3.1452 +    <dt><dfn class="css" data-dfn-for="overflow" data-dfn-type="value" data-export="" id="valdef-overflow-scroll">scroll<a class="self-link" href="#valdef-overflow-scroll"></a></dfn>
  3.1453 +		
  3.1454 +    <dt><dfn class="css" data-dfn-for="overflow" data-dfn-type="value" data-export="" id="valdef-overflow-auto">auto<a class="self-link" href="#valdef-overflow-auto"></a></dfn>
  3.1455 +		
  3.1456 +    <dd>
  3.1457 +			These values are collectively the <dfn data-dfn-for="overflow" data-dfn-type="dfn" data-noexport="" id="scrolling-values">scrolling values<a class="self-link" href="#scrolling-values"></a></dfn>;
  3.1458 +			they are defined in the section on
  3.1459 +			<a href="#scrolling-overflow">scrolling and hidden overflow</a>.
  3.1460 +		
  3.1461 +    
  3.1462 +		
  3.1463 +    <dt><dfn class="css" data-dfn-for="overflow" data-dfn-type="value" data-export="" id="valdef-overflow-paged-x">paged-x<a class="self-link" href="#valdef-overflow-paged-x"></a></dfn>
  3.1464 +		
  3.1465 +    <dt><dfn class="css" data-dfn-for="overflow" data-dfn-type="value" data-export="" id="valdef-overflow-paged-y">paged-y<a class="self-link" href="#valdef-overflow-paged-y"></a></dfn>
  3.1466 +		
  3.1467 +    <dt><dfn class="css" data-dfn-for="overflow" data-dfn-type="value" data-export="" id="valdef-overflow-paged-x-controls">paged-x-controls<a class="self-link" href="#valdef-overflow-paged-x-controls"></a></dfn>
  3.1468 +		
  3.1469 +    <dt><dfn class="css" data-dfn-for="overflow" data-dfn-type="value" data-export="" id="valdef-overflow-paged-y-controls">paged-y-controls<a class="self-link" href="#valdef-overflow-paged-y-controls"></a></dfn>
  3.1470 +		
  3.1471 +    <dt><dfn class="css" data-dfn-for="overflow" data-dfn-type="value" data-export="" id="valdef-overflow-fragments">fragments<a class="self-link" href="#valdef-overflow-fragments"></a></dfn>
  3.1472 +		
  3.1473 +    <dd>
  3.1474 +			These values are collectively the <dfn data-dfn-for="overflow" data-dfn-type="dfn" data-noexport="" id="fragmenting-values">fragmenting values<a class="self-link" href="#fragmenting-values"></a></dfn>;
  3.1475 +			they are defined in the sections on
  3.1476 +			<a href="#paginated-overflow">paginated overflow</a> and
  3.1477 +			<a href="#fragment-overflow">fragment overflow</a>.
  3.1478 +		
  3.1479 +    
  3.1480 +	
  3.1481 +   </dl>
  3.1482 +
  3.1483 +	
  3.1484 +   <div id="overflow-computed-values">
  3.1485 +		
  3.1486 +    <p>The computed values of <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> and <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>
  3.1487 +		are determined from the cascaded values <a data-link-type="biblio" href="#biblio-css3cascade">[CSS3CASCADE]</a>
  3.1488 +		based on the following rules:</p>
  3.1489 +    
  3.1490 +
  3.1491 +		
  3.1492 +    <ol>
  3.1493 +			
  3.1494 +     <li>
  3.1495 +				If one or both of the cascaded values are
  3.1496 +				<a data-link-type="dfn" href="#fragmenting-values">fragmenting values</a>, then:
  3.1497 +				
  3.1498 +      <ol>
  3.1499 +					
  3.1500 +       <li>
  3.1501 +						If one of the cascaded values is one of the
  3.1502 +						<a data-link-type="dfn" href="#fragmenting-values">fragmenting values</a>
  3.1503 +						and the other is not,
  3.1504 +						then the computed values are
  3.1505 +						the same as the cascaded values.
  3.1506 +					
  3.1507 +       
  3.1508 +					
  3.1509 +       <li>
  3.1510 +						If both of the cascaded values are <a data-link-type="dfn" href="#fragmenting-values">fragmenting values</a>, then:
  3.1511 +						
  3.1512 +        <ol>
  3.1513 +							
  3.1514 +         <li>
  3.1515 +								for horizontal writing mode <a data-link-type="biblio" href="#biblio-css3-writing-modes">[CSS3-WRITING-MODES]</a>,
  3.1516 +								the computed value for <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> is the cascaded value
  3.1517 +								and the computed value for <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> is <a class="css" data-link-type="maybe" href="#valdef-overflow-hidden">hidden</a>, or
  3.1518 +							
  3.1519 +         
  3.1520 +							
  3.1521 +         <li>
  3.1522 +								for vertical writing mode <a data-link-type="biblio" href="#biblio-css3-writing-modes">[CSS3-WRITING-MODES]</a>,
  3.1523 +								the computed value for <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> is the cascaded value
  3.1524 +								and the computed value for <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> is <a class="css" data-link-type="maybe" href="#valdef-overflow-hidden">hidden</a>.
  3.1525 +							
  3.1526 +         
  3.1527 +						
  3.1528 +        </ol>
  3.1529 +        
  3.1530 +					
  3.1531 +       
  3.1532 +				
  3.1533 +      </ol>
  3.1534 +      
  3.1535 +			
  3.1536 +     
  3.1537 +			
  3.1538 +     <li>
  3.1539 +				Otherwise, if one cascaded values is
  3.1540 +				one of the <a data-link-type="dfn" href="#scrolling-values">scrolling values</a>
  3.1541 +				and the other is <a class="css" data-link-type="maybe" href="#valdef-overflow-visible">visible</a>,
  3.1542 +				then computed values are the cascaded values
  3.1543 +				with <a class="css" data-link-type="maybe" href="#valdef-overflow-visible">visible</a> changed to <a class="css" data-link-type="maybe" href="#valdef-overflow-auto">auto</a>.
  3.1544 +			
  3.1545 +     
  3.1546 +			
  3.1547 +     <li>
  3.1548 +				Otherwise, the computed values are as specified.
  3.1549 +			
  3.1550 +     
  3.1551 +		
  3.1552 +    </ol>
  3.1553 +    
  3.1554 +	
  3.1555 +   </div>
  3.1556 +
  3.1557 +	
  3.1558 +   <p class="issue" id="issue-45d3d9aa"><a class="self-link" href="#issue-45d3d9aa"></a>
  3.1559 +		Are all 4 of the <span class="css">paged-*</span> values really needed?
  3.1560 +	</p>
  3.1561 +
  3.1562 +	
  3.1563 +   <p>
  3.1564 +		When the <a data-link-type="dfn" href="#fragmenting-values">fragmenting values</a> are used,
  3.1565 +		the overflow from the fragments themselves
  3.1566 +		treats the fragmenting value as <a class="css" data-link-type="maybe" href="#valdef-overflow-hidden">hidden</a>.
  3.1567 +		<span class="issue" id="issue-ef127061"><a class="self-link" href="#issue-ef127061"></a>Is this the right behavior?</span>
  3.1568 +		<span class="issue" id="issue-78cdbe9b"><a class="self-link" href="#issue-78cdbe9b"></a>Give example.</span>
  3.1569 +	</p>
  3.1570 +
  3.1571 +	
  3.1572 +   <p class="issue" id="issue-2c53acbd"><a class="self-link" href="#issue-2c53acbd"></a>
  3.1573 +		<a data-link-type="biblio" href="#biblio-css3-marquee">[CSS3-MARQUEE]</a> describes an <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> property,
  3.1574 +		but it has not picked up implementation experience
  3.1575 +		that the working group is aware of.
  3.1576 +		Should this document treat <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> as a defunct proposal,
  3.1577 +		or should this document describe the <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> property
  3.1578 +		and attempt to revive it,
  3.1579 +		despite that implementations have implemented
  3.1580 +		<a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> and <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> instead?
  3.1581 +	</p>
  3.1582 +
  3.1583 +	
  3.1584 +   <p class="issue" id="issue-a8b88d7e"><a class="self-link" href="#issue-a8b88d7e"></a>
  3.1585 +		There are <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussions</a>
  3.1586 +		about how overflow, overflow-style, overflow-x and overflow-y
  3.1587 +		should work and interact with each other.
  3.1588 +		Until consensus on this topic is reached,
  3.1589 +		it is not completely clear which of these
  3.1590 +		should be used for
  3.1591 +		paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
  3.1592 +	</p>
  3.1593 +
  3.1594 +
  3.1595 +   <h2 class="heading settled" data-level="4" id="scrolling-overflow"><span class="secno">4. </span><span class="content">Scrolling and hidden overflow</span><a class="self-link" href="#scrolling-overflow"></a></h2>
  3.1596 +
  3.1597 +	
  3.1598 +   <p class="issue" id="issue-726ed205"><a class="self-link" href="#issue-726ed205"></a>
  3.1599 +		Move material from <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a> and <a data-link-type="biblio" href="#biblio-css3box">[CSS3BOX]</a> here.
  3.1600 +	</p>
  3.1601 +
  3.1602 +	
  3.1603 +   <p class="issue" id="issue-c318b1c1"><a class="self-link" href="#issue-c318b1c1"></a>
  3.1604 +		Explain which directions allow scrolling and which don’t,
  3.1605 +		as a function of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-writing-modes-3/#propdef-direction">direction</a>
  3.1606 +		(including propagation of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-writing-modes-3/#propdef-direction">direction</a> to the ICB).
  3.1607 +	</p>
  3.1608 +
  3.1609 +
  3.1610 +   <h2 class="heading settled" data-level="5" id="paginated-overflow"><span class="secno">5. </span><span class="content">Paginated overflow</span><a class="self-link" href="#paginated-overflow"></a></h2>
  3.1611 +
  3.1612 +
  3.1613 +   <p class="issue" id="issue-03349ce5"><a class="self-link" href="#issue-03349ce5"></a>overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> has?)</p>
  3.1614 +
  3.1615 +
  3.1616 +   <p class="issue" id="issue-22961e25"><a class="self-link" href="#issue-22961e25"></a>Ability to display N pages at once
  3.1617 +rather than just one page at once?</p>
  3.1618 +
  3.1619 +	
  3.1620 +   <p class="issue" id="issue-7328bc11"><a class="self-link" href="#issue-7328bc11"></a>
  3.1621 +		The current implementation of paginated overflow uses
  3.1622 +		the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>/<a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a>/<a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> properties
  3.1623 +		rather than the <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> property as proposed
  3.1624 +		in the <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> draft
  3.1625 +		(which also matches the <a data-link-type="biblio" href="#biblio-css3-marquee">[CSS3-MARQUEE]</a> proposal).
  3.1626 +		We should probably switch away from <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a>,
  3.1627 +		but that’s not 100% clear.
  3.1628 +	</p>
  3.1629 +
  3.1630 +
  3.1631 +   <h2 class="heading settled" data-level="6" id="fragment-overflow"><span class="secno">6. </span><span class="content">Fragment overflow</span><a class="self-link" href="#fragment-overflow"></a></h2>
  3.1632 +
  3.1633 +	
  3.1634 +   <p>
  3.1635 +		This section introduces and defines the meaning of
  3.1636 +		the new <a class="css" data-link-type="maybe" href="#valdef-overflow-fragments">fragments</a> value of the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> property.
  3.1637 +	</p>
  3.1638 +
  3.1639 +	
  3.1640 +   <p>
  3.1641 +		When the computed value of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> for an element is <a class="css" data-link-type="maybe" href="#valdef-overflow-fragments">fragments</a>,
  3.1642 +		and implementations would otherwise have created a box for the element,
  3.1643 +		then implementations must create a sequence of <dfn data-dfn-type="dfn" data-noexport="" id="fragment-box">fragment box<a class="self-link" href="#fragment-box"></a></dfn>es
  3.1644 +		for that element.
  3.1645 +		(It is possible for an element with <a class="css" data-link-type="propdesc" href="#propdef-overflow">overflow: fragments</a>
  3.1646 +		to generate only one <a data-link-type="dfn" href="#fragment-box">fragment box</a>.
  3.1647 +		However, if an element’s computed <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> is not <a class="css" data-link-type="maybe" href="#valdef-overflow-fragments">fragments</a>,
  3.1648 +		then its box is not a <a data-link-type="dfn" href="#fragment-box">fragment box</a>.)
  3.1649 +		Every <a data-link-type="dfn" href="#fragment-box">fragment box</a> is a fragmentation container,
  3.1650 +		and any overflow
  3.1651 +		that would cause that fragmentation container to fragment
  3.1652 +		causes another <a data-link-type="dfn" href="#fragment-box">fragment box</a> created as a next sibling
  3.1653 +		of the previous one.
  3.1654 +		<span class="issue" id="issue-74f423ed"><a class="self-link" href="#issue-74f423ed"></a>Or is it as though it’s a next sibling of
  3.1655 +		the element?  Need to figure out exactly how this interacts with
  3.1656 +		other box-level fixup.</span>
  3.1657 +		Additionally, if the <a data-link-type="dfn" href="#fragment-box">fragment box</a> is also
  3.1658 +		a multi-column box (as defined in <a data-link-type="biblio" href="#biblio-css3col">[CSS3COL]</a>
  3.1659 +		<span class="issue" id="issue-928903ce"><a class="self-link" href="#issue-928903ce"></a>though it defines <i>multi-column element</i></span>)
  3.1660 +		any content that would lead to the creation of <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-multicol/#overflow-columns">overflow columns</a> <a data-link-type="biblio" href="#biblio-css3col">[CSS3COL]</a>
  3.1661 +		instead is flown into an additional fragment box.
  3.1662 +		However, fragment boxes may themselves be broken
  3.1663 +		(due to fragmentation in a fragmentation context outside of them,
  3.1664 +		such as pages, columns, or other fragment boxes);
  3.1665 +		such breaking leads to fragments of the same fragment box
  3.1666 +		rather than multiple fragment boxes.
  3.1667 +		(This matters because fragment boxes may be styled by their index;
  3.1668 +		such breaking leads to multiple fragments of a fragment box
  3.1669 +		with a single index.
  3.1670 +		This design choice is so that
  3.1671 +		breaking a fragment box across pages does not break
  3.1672 +		the association of indices to particular pieces of content.)
  3.1673 +		<span class="issue" id="issue-060b1de8"><a class="self-link" href="#issue-060b1de8"></a>Should a forced break that breaks to
  3.1674 +		an outer fragmentation context cause a new fragment of a single
  3.1675 +		fragment box or a new fragment box?</span>
  3.1676 +		<span class="issue" id="issue-5b4b087c"><a class="self-link" href="#issue-5b4b087c"></a>Should we find a term other than
  3.1677 +		<a data-link-type="dfn" href="#fragment-box">fragment box</a> here to make this a little less confusing?</span>
  3.1678 +	</p>
  3.1679 +
  3.1680 +	
  3.1681 +   <p class="issue" id="issue-89a60b9c"><a class="self-link" href="#issue-89a60b9c"></a>
  3.1682 +		What if we want to be able to style the pieces of an element
  3.1683 +		split within another type of fragmentation context?
  3.1684 +		These rules prevent ever using <span class="css">::nth-fragment()</span> for that,
  3.1685 +		despite that the name seems the most logical name for such a feature.
  3.1686 +	</p>
  3.1687 +
  3.1688 +	
  3.1689 +   <div class="example">
  3.1690 +		
  3.1691 +    <table class="source-demo-pair">
  3.1692 +     <tbody>
  3.1693 +      <tr>
  3.1694 +       <td>
  3.1695 +        <pre>&lt;!DOCTYPE HTML>
  3.1696 +&lt;title>Breaking content into
  3.1697 +  equal-sized cards&lt;/title>
  3.1698 +&lt;style>
  3.1699    .in-cards {
  3.1700      overflow: fragments;
  3.1701  
  3.1702 @@ -889,109 +1041,143 @@
  3.1703      font: medium/1.3 Times New
  3.1704        Roman, Times, serif;
  3.1705    }
  3.1706 -&lt;/style&gt;
  3.1707 -&lt;div class="in-cards"&gt;
  3.1708 +&lt;/style>
  3.1709 +&lt;div class="in-cards">
  3.1710    In this example, the text in the div
  3.1711    is broken into a series of cards.
  3.1712    These cards all have the same style.
  3.1713    The presence of enough content to
  3.1714    overflow one of the cards causes
  3.1715    another one to be created.  The second
  3.1716 -  card is created just like it's the
  3.1717 +  card is created just like it’s the
  3.1718    next sibling of the first.
  3.1719 -&lt;/div&gt;</pre>
  3.1720 +&lt;/div></pre>
  3.1721 +       <td>
  3.1722 +			
  3.1723 +        <div class="in-cards-demo">In this example, the text in the<br>div is broken into a series of<br>cards.  These cards all have the<br>same style. The presence of<br>enough content to overflow<br>one of the cards causes another</div>
  3.1724 +        
  3.1725 +			
  3.1726 +        <div class="in-cards-demo">one to be created.  The second<br>card is created just like it’s the<br>next sibling of the first.</div>
  3.1727 +        
  3.1728 +		
  3.1729 +    </table>
  3.1730 +    
  3.1731 +	
  3.1732 +   </div>
  3.1733  
  3.1734 -      <td>
  3.1735 -       <div class=in-cards-demo>In this example, the text in the<br>
  3.1736 -        div is broken into a series of<br>
  3.1737 -        cards. These cards all have the<br>
  3.1738 -        same style. The presence of<br>
  3.1739 -        enough content to overflow<br>
  3.1740 -        one of the cards causes another</div>
  3.1741 +	
  3.1742 +   <p class="issue" id="issue-f590932f"><a class="self-link" href="#issue-f590932f"></a>
  3.1743 +		We should specify that <a class="css" data-link-type="propdesc" href="#propdef-overflow">overflow: fragments</a> does not apply
  3.1744 +		to at least some table parts,
  3.1745 +		and perhaps other elements as well.
  3.1746 +		We need to determine exactly which ones.
  3.1747 +	</p>
  3.1748  
  3.1749 -       <div class=in-cards-demo>one to be created. The second<br>
  3.1750 -        card is created just like it's the<br>
  3.1751 -        next sibling of the first.</div>
  3.1752 -   </table>
  3.1753 -  </div>
  3.1754 +	
  3.1755 +   <p class="issue" id="issue-54f95309"><a class="self-link" href="#issue-54f95309"></a>
  3.1756 +		This specification needs to say which type of
  3.1757 +		fragmentation context is created
  3.1758 +		so that it’s clear which values of the <a class="property" data-link-type="propdesc">break-*</a> properties
  3.1759 +		cause breaks within this context.
  3.1760 +		We probably want <span class="css">break-*: region</span> to apply.
  3.1761 +	</p>
  3.1762  
  3.1763 -  <p class=issue> We should specify that ‘<code class=css>overflow:
  3.1764 -   fragments</code>’ does not apply to at least some table parts, and
  3.1765 -   perhaps other elements as well. We need to determine exactly which ones.
  3.1766 +	
  3.1767 +   <p class="issue" id="issue-e784096c"><a class="self-link" href="#issue-e784096c"></a>
  3.1768 +		This specification needs a processing model
  3.1769 +		that will apply in cases where the layout containing the
  3.1770 +		fragments has characteristics that use the intrinsic size of the fragments
  3.1771 +		to change the amount of space available for them,
  3.1772 +		such as <a data-link-type="biblio" href="#biblio-css3-grid-layout">[CSS3-GRID-LAYOUT]</a>.
  3.1773 +		There has already been some work on such a processing model
  3.1774 +		in <a data-link-type="biblio" href="#biblio-css3-regions">[CSS3-REGIONS]</a>,
  3.1775 +		and the work done on a model there,
  3.1776 +		and the editors of that specification,
  3.1777 +		should inform what happens in this specification.
  3.1778 +	</p>
  3.1779  
  3.1780 -  <p class=issue> This specification needs to say which type of fragmentation
  3.1781 -   context is created so that it's clear which values of the ‘<code
  3.1782 -   class=css>break-*</code>’ properties cause breaks within this context.
  3.1783 -   We probably want ‘<code class=css>break-*: region</code>’ to apply.
  3.1784  
  3.1785 -  <p class=issue> This specification needs a processing model that will apply
  3.1786 -   in cases where the layout containing the fragments has characteristics
  3.1787 -   that use the intrinsic size of the fragments to change the amount of space
  3.1788 -   available for them, such as <a
  3.1789 -   href="#ref-CSS-GRID-1">[CSS-GRID-1]<!--{{CSS-GRID-1}}--></a>. There has
  3.1790 -   already been some work on such a processing model in <a
  3.1791 -   href="#ref-CSS-REGIONS-1">[CSS-REGIONS-1]<!--{{CSS-REGIONS-1}}--></a>, and
  3.1792 -   the work done on a model there, and the editors of that specification,
  3.1793 -   should inform what happens in this specification.
  3.1794 +   <h3 class="heading settled" data-level="6.1" id="fragment-styling"><span class="secno">6.1. </span><span class="content">Fragment styling</span><a class="self-link" href="#fragment-styling"></a></h3>
  3.1795  
  3.1796 -  <h3 id=fragment-styling><span class=secno>6.1. </span>Fragment styling</h3>
  3.1797  
  3.1798 -  <h4 id=fragment-pseudo-element><span class=secno>6.1.1. </span>The
  3.1799 -   ::nth-fragment() pseudo-element</h4>
  3.1800 +   <h4 class="heading settled" data-level="6.1.1" id="fragment-pseudo-element"><span class="secno">6.1.1. </span><span class="content">The ::nth-fragment() pseudo-element</span><a class="self-link" href="#fragment-pseudo-element"></a></h4>
  3.1801  
  3.1802 -  <p> The ::nth-fragment() pseudo-element is a pseudo-element that describes
  3.1803 -   some of the <a href="#fragment-box"><i>fragment box</i></a>es generated by
  3.1804 -   an element. The argument to the pseudo-element takes the same syntax as
  3.1805 -   the argument to the :nth-child() pseudo-class defined in <a
  3.1806 -   href="#ref-SELECT">[SELECT]<!--{{!SELECT}}--></a>, and has the same
  3.1807 -   meaning except that the number is relative to <a
  3.1808 -   href="#fragment-box"><i>fragment box</i></a>es generated by the element
  3.1809 -   instead of siblings of the element.
  3.1810 +	
  3.1811 +   <p>
  3.1812 +		The ::nth-fragment() pseudo-element is a pseudo-element
  3.1813 +		that describes some of the <a data-link-type="dfn" href="#fragment-box">fragment box</a>es generated by an element.
  3.1814 +		The argument to the pseudo-element takes the same syntax
  3.1815 +		as the argument to the :nth-child() pseudo-class
  3.1816 +		defined in <a data-link-type="biblio" href="#biblio-select">[SELECT]</a>, and has the same meaning
  3.1817 +		except that the number is relative to
  3.1818 +		<a data-link-type="dfn" href="#fragment-box">fragment box</a>es generated by the element
  3.1819 +		instead of siblings of the element.
  3.1820 +	</p>
  3.1821  
  3.1822 -  <p class=note> Selectors that allow addressing fragments by counting from
  3.1823 -   the end rather than the start are intentionally not provided. Such
  3.1824 -   selectors would interfere with determining the number of fragments.
  3.1825 +	
  3.1826 +   <p class="note" role="note">
  3.1827 +		Selectors that allow addressing fragments
  3.1828 +		by counting from the end rather than the start
  3.1829 +		are intentionally not provided.
  3.1830 +		Such selectors would interfere with determining
  3.1831 +		the number of fragments.
  3.1832 +	</p>
  3.1833  
  3.1834 -  <p class=issue> Depending on future discussions, this ‘<code
  3.1835 -   class=css>::nth-fragment(<var>an+b</var>)</code>’ syntax may be replaced
  3.1836 -   with the new ‘<code class=css>::fragment:nth(<var>an+b</var>)</code>’
  3.1837 -   syntax.
  3.1838 +	
  3.1839 +   <p class="issue" id="issue-4cfde272"><a class="self-link" href="#issue-4cfde272"></a>
  3.1840 +		Depending on future discussions,
  3.1841 +		this <span class="css">::nth-fragment(an+b)</span> syntax
  3.1842 +		may be replaced with
  3.1843 +		the new <span class="css">::fragment:nth(an+b)</span> syntax.
  3.1844 +	</p>
  3.1845  
  3.1846 -  <h4 id=style-of-fragments><span class=secno>6.1.2. </span>Styling of
  3.1847 -   fragments</h4>
  3.1848  
  3.1849 -  <p class=issue> Should this apply to fragment overflow only, or also to
  3.1850 -   paginated overflow? (If it applies, then stricter property restrictions
  3.1851 -   would be needed for paginated overflow.)
  3.1852 +   <h4 class="heading settled" data-level="6.1.2" id="style-of-fragments"><span class="secno">6.1.2. </span><span class="content">Styling of fragments</span><a class="self-link" href="#style-of-fragments"></a></h4>
  3.1853  
  3.1854 -  <p> In the absence of rules with ‘<code
  3.1855 -   class=css>::nth-fragment()</code>’ pseudo-elements, the computed style
  3.1856 -   for each <a href="#fragment-box"><i>fragment box</i></a> is the computed
  3.1857 -   style for the element for which the <a href="#fragment-box"><i>fragment
  3.1858 -   box</i></a> was created. However, the style for a <a
  3.1859 -   href="#fragment-box"><i>fragment box</i></a> is also influenced by rules
  3.1860 -   whose selector's <i>subject</i> <a
  3.1861 -   href="#ref-SELECT">[SELECT]<!--{{!SELECT}}--></a> has an ‘<code
  3.1862 -   class=css>::nth-fragment()</code>’ pseudo-element, if the 1-based number
  3.1863 -   of the <a href="#fragment-box"><i>fragment box</i></a> matches that
  3.1864 -   ‘<code class=css>::nth-fragment()</code>’ pseudo-element and the
  3.1865 -   selector (excluding the ‘<code class=css>::nth-fragment()</code>’
  3.1866 -   pseudo-element) matches the element generating the fragments.
  3.1867 +	
  3.1868 +   <p class="issue" id="issue-27c56696"><a class="self-link" href="#issue-27c56696"></a>
  3.1869 +		Should this apply to fragment overflow only,
  3.1870 +		or also to paginated overflow?
  3.1871 +		(If it applies,
  3.1872 +		then stricter property restrictions would be needed
  3.1873 +		for paginated overflow.)
  3.1874 +	</p>
  3.1875  
  3.1876 -  <p> When determining the style of the <a href="#fragment-box"><i>fragment
  3.1877 -   box</i></a>, these rules that match the fragment pseudo-element cascade
  3.1878 -   together with the rules that match the element, with the fragment
  3.1879 -   pseudo-element adding the specificity of a pseudo-class to the specificity
  3.1880 -   calculation. <span class=issue>Does this need to be specified in the
  3.1881 -   cascading module as well?</span>
  3.1882 +	
  3.1883 +   <p>
  3.1884 +		In the absence of rules with <span class="css">::nth-fragment()</span> pseudo-elements,
  3.1885 +		the computed style for each <a data-link-type="dfn" href="#fragment-box">fragment box</a>
  3.1886 +		is the computed style for the element
  3.1887 +		for which the <a data-link-type="dfn" href="#fragment-box">fragment box</a> was created.
  3.1888 +		However, the style for a <a data-link-type="dfn" href="#fragment-box">fragment box</a> is also influenced
  3.1889 +		by rules whose selector’s <a data-link-type="dfn" href="http://dev.w3.org/csswg/selectors-3/#subject">subject</a> <a data-link-type="biblio" href="#biblio-select">[SELECT]</a>
  3.1890 +		has an <span class="css">::nth-fragment()</span> pseudo-element,
  3.1891 +		if the 1-based number of the <a data-link-type="dfn" href="#fragment-box">fragment box</a> matches
  3.1892 +		that <span class="css">::nth-fragment()</span> pseudo-element
  3.1893 +		and the selector (excluding the <span class="css">::nth-fragment()</span> pseudo-element)
  3.1894 +		matches the element generating the fragments.
  3.1895 +	</p>
  3.1896  
  3.1897 -  <div class=example>
  3.1898 -   <table class=source-demo-pair>
  3.1899 -    <tbody>
  3.1900 -     <tr>
  3.1901 -      <td>
  3.1902 -       <pre>&lt;!DOCTYPE HTML&gt;
  3.1903 -&lt;style&gt;
  3.1904 +	
  3.1905 +   <p>
  3.1906 +		When determining the style of the <a data-link-type="dfn" href="#fragment-box">fragment box</a>,
  3.1907 +		these rules that match the fragment pseudo-element
  3.1908 +		cascade together with the rules that match the element,
  3.1909 +		with the fragment pseudo-element adding the specificity
  3.1910 +		of a pseudo-class to the specificity calculation.
  3.1911 +		<span class="issue" id="issue-8f881f96"><a class="self-link" href="#issue-8f881f96"></a>Does this need to be specified in
  3.1912 +		the cascading module as well?</span>
  3.1913 +	</p>
  3.1914 +
  3.1915 +	
  3.1916 +   <div class="example">
  3.1917 +		
  3.1918 +    <table class="source-demo-pair">
  3.1919 +     <tbody>
  3.1920 +      <tr>
  3.1921 +       <td>
  3.1922 +        <pre>&lt;!DOCTYPE HTML>
  3.1923 +&lt;style>
  3.1924    .bouncy-columns {
  3.1925      overflow: fragments;
  3.1926      width: 6em;
  3.1927 @@ -1009,117 +1195,119 @@
  3.1928      background: yellow; color: black;
  3.1929      transform: rotate(3deg);
  3.1930    }
  3.1931 -&lt;/style&gt;
  3.1932 -&lt;div class="bouncy-columns"&gt;
  3.1933 +&lt;/style>
  3.1934 +&lt;div class="bouncy-columns">
  3.1935    <i>...</i>
  3.1936 -&lt;/div&gt;</pre>
  3.1937 +&lt;/div></pre>
  3.1938 +       <td>
  3.1939 +			
  3.1940 +        <div class="bouncy-columns-demo one">In this<br>example, the<br>text in the div<br>is broken into<br>a series of<br>columns.  The<br>author<br>probably</div>
  3.1941 +        
  3.1942 +			
  3.1943 +        <div class="bouncy-columns-demo two">intended the<br>text to fill two<br>columns.  But<br>if it happens to<br>fill three<br>columns, the<br>third column is<br>still created.  It</div>
  3.1944 +        
  3.1945 +			
  3.1946 +        <div class="bouncy-columns-demo">just doesn’t<br>have any<br>fragment-specific<br>styling because<br>the author<br>didn’t give it<br>any.</div>
  3.1947 +        
  3.1948 +		
  3.1949 +    </table>
  3.1950 +    
  3.1951 +	
  3.1952 +   </div>
  3.1953  
  3.1954 -      <td>
  3.1955 -       <div class="bouncy-columns-demo one">In this<br>
  3.1956 -        example, the<br>
  3.1957 -        text in the div<br>
  3.1958 -        is broken into<br>
  3.1959 -        a series of<br>
  3.1960 -        columns. The<br>
  3.1961 -        author<br>
  3.1962 -        probably</div>
  3.1963 +	
  3.1964 +   <p>
  3.1965 +		Styling an <span class="css">::nth-fragment()</span> pseudo-element with the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>
  3.1966 +		property does take effect;
  3.1967 +		if a <a data-link-type="dfn" href="#fragment-box">fragment box</a> has a
  3.1968 +		computed value of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> other than <a class="css" data-link-type="maybe" href="#valdef-overflow-fragments">fragments</a>
  3.1969 +		then that fragment box is the last fragment.
  3.1970 +		However, overriding <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> on the first fragment
  3.1971 +		does not cause the <a data-link-type="dfn" href="#fragment-box">fragment box</a> not to exist;
  3.1972 +		whether there are fragment boxes at all is determined by
  3.1973 +		the computed value of overflow for the element.
  3.1974 +		<span class="issue" id="issue-1c902202"><a class="self-link" href="#issue-1c902202"></a>Need to reword this to refer to the
  3.1975 +		appropriate choice of <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> or <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>,
  3.1976 +		and then point to rule about the handling of the other one
  3.1977 +		of <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> or <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>.</span>
  3.1978 +	</p>
  3.1979  
  3.1980 -       <div class="bouncy-columns-demo two">intended the<br>
  3.1981 -        text to fill two<br>
  3.1982 -        columns. But<br>
  3.1983 -        if it happens to<br>
  3.1984 -        fill three<br>
  3.1985 -        columns, the<br>
  3.1986 -        third column is<br>
  3.1987 -        still created. It</div>
  3.1988 +	
  3.1989 +   <p>
  3.1990 +		Styling an <span class="css">::nth-fragment()</span> pseudo-element with the <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-content-3/#propdef-content">content</a>
  3.1991 +		property has no effect;
  3.1992 +		the computed value of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-content-3/#propdef-content">content</a> for the fragment box
  3.1993 +		remains the same as the computed value of content for the element.
  3.1994 +	</p>
  3.1995  
  3.1996 -       <div class=bouncy-columns-demo>just doesn't<br>
  3.1997 -        have any<br>
  3.1998 -        fragment-specific<br>
  3.1999 -        styling because<br>
  3.2000 -        the author<br>
  3.2001 -        didn't give it<br>
  3.2002 -        any.</div>
  3.2003 -   </table>
  3.2004 -  </div>
  3.2005 +	
  3.2006 +   <p>
  3.2007 +		Specifying <a class="css" data-link-type="propdesc" href="http://dev.w3.org/csswg/css2/visuren.html#propdef-display">display: none</a> for a <a data-link-type="dfn" href="#fragment-box">fragment box</a> causes
  3.2008 +		the fragment box with that index not to be generated.
  3.2009 +		However, in terms of the indices
  3.2010 +		used for matching <span class="css">::nth-fragment()</span> pseudo-elements
  3.2011 +		of later fragment boxes,
  3.2012 +		it still counts as though it was generated.
  3.2013 +		However, since it is not generated, it does not contain any content.
  3.2014 +	</p>
  3.2015  
  3.2016 -  <p> Styling an ‘<code class=css>::nth-fragment()</code>’ pseudo-element
  3.2017 -   with the ‘<a href="#overflow0"><code
  3.2018 -   class=property>overflow</code></a>’ property does take effect; if a <a
  3.2019 -   href="#fragment-box"><i>fragment box</i></a> has a computed value of ‘<a
  3.2020 -   href="#overflow0"><code class=property>overflow</code></a>’ other than
  3.2021 -   ‘<a href="#fragments"><code class=css>fragments</code></a>’ then that
  3.2022 -   fragment box is the last fragment. However, overriding ‘<a
  3.2023 -   href="#overflow0"><code class=property>overflow</code></a>’ on the first
  3.2024 -   fragment does not cause the <a href="#fragment-box"><i>fragment
  3.2025 -   box</i></a> not to exist; whether there are fragment boxes at all is
  3.2026 -   determined by the computed value of overflow for the element. <span
  3.2027 -   class=issue>Need to reword this to refer to the appropriate choice of
  3.2028 -   ‘<a href="#overflow-x"><code class=property>overflow-x</code></a>’ or
  3.2029 -   ‘<a href="#overflow-y"><code class=property>overflow-y</code></a>’,
  3.2030 -   and then point to rule about the handling of the other one of ‘<a
  3.2031 -   href="#overflow-x"><code class=property>overflow-x</code></a>’ or ‘<a
  3.2032 -   href="#overflow-y"><code class=property>overflow-y</code></a>’.</span>
  3.2033 +	
  3.2034 +   <p>
  3.2035 +		Specifying other values of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css2/visuren.html#propdef-display">display</a>, <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-position-3/#propdef-position">position</a>,
  3.2036 +		or <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css2/visuren.html#propdef-float">float</a> is permitted, but is not allowed to change
  3.2037 +		the computed value of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-inside">display-inside</a>.
  3.2038 +		(Since <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>, <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a>, and <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> only
  3.2039 +		apply to block containers, flex containers, and grid containers
  3.2040 +		the computed value of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-inside">display-inside</a> is always
  3.2041 +		<a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-display-3/#valdef-display-inside-block">block</a>, <a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-display-3/#valdef-display-inside-flex">flex</a>, or
  3.2042 +		<a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-display-3/#valdef-display-inside-grid">grid</a>.
  3.2043 +		<span class="issue" id="issue-d98e732d"><a class="self-link" href="#issue-d98e732d"></a>Need to specify exactly how this works,
  3.2044 +		but it depends on
  3.2045 +		having <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-inside">display-inside</a> and <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-outside">display-outside</a> specified.</span>
  3.2046 +	</p>
  3.2047  
  3.2048 -  <p> Styling an ‘<code class=css>::nth-fragment()</code>’ pseudo-element
  3.2049 -   with the ‘<code class=property>content</code>’ property has no effect;
  3.2050 -   the computed value of ‘<code class=property>content</code>’ for the
  3.2051 -   fragment box remains the same as the computed value of content for the
  3.2052 -   element.
  3.2053 +	
  3.2054 +   <p>
  3.2055 +		To match the model for other pseudo-elements
  3.2056 +		where the pseudo-elements live inside their corresponding element,
  3.2057 +		declarations in <span class="css">::nth-fragment()</span> pseudo-elements override
  3.2058 +		declarations in rules without the pseudo-element.
  3.2059 +		The relative priority within such declarations is determined
  3.2060 +		by normal cascading order (see <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a>).
  3.2061 +	</p>
  3.2062  
  3.2063 -  <p> Specifying ‘<code class=css>display: none</code>’ for a <a
  3.2064 -   href="#fragment-box"><i>fragment box</i></a> causes the fragment box with
  3.2065 -   that index not to be generated. However, in terms of the indices used for
  3.2066 -   matching ‘<code class=css>::nth-fragment()</code>’ pseudo-elements of
  3.2067 -   later fragment boxes, it still counts as though it was generated. However,
  3.2068 -   since it is not generated, it does not contain any content.
  3.2069 +	
  3.2070 +   <p>
  3.2071 +		Styles specified on <span class="css">::nth-fragment()</span> pseudo-elements
  3.2072 +		do affect inheritance to content within the <a data-link-type="dfn" href="#fragment-box">fragment box</a>.
  3.2073 +		In other words, the content within the <a data-link-type="dfn" href="#fragment-box">fragment box</a> must
  3.2074 +		inherit from the fragment box’s style (i.e., the pseudo-element style)
  3.2075 +		rather than directly from the element.
  3.2076 +		This means that elements split between fragment boxes may
  3.2077 +		have different styles for different parts of the element.
  3.2078 +	</p>
  3.2079  
  3.2080 -  <p> Specifying other values of ‘<code class=property>display</code>’,
  3.2081 -   ‘<code class=property>position</code>’, or ‘<code
  3.2082 -   class=property>float</code>’ is permitted, but is not allowed to change
  3.2083 -   the computed value of ‘<code class=property>display-inside</code>’.
  3.2084 -   (Since ‘<a href="#overflow0"><code
  3.2085 -   class=property>overflow</code></a>’, ‘<a href="#overflow-x"><code
  3.2086 -   class=property>overflow-x</code></a>’, and ‘<a
  3.2087 -   href="#overflow-y"><code class=property>overflow-y</code></a>’ only
  3.2088 -   apply to block containers, flex containers, and grid containers the
  3.2089 -   computed value of ‘<code class=property>display-inside</code>’ is
  3.2090 -   always ‘<code class=css>block</code>’, ‘<code
  3.2091 -   class=css>flex</code>’ or ‘<code class=css>grid</code>’. <span
  3.2092 -   class=issue>Need to specify exactly how this works, but it depends on
  3.2093 -   having ‘<code class=property>display-inside</code>’ and ‘<code
  3.2094 -   class=property>display-outside</code>’ specified.</span>
  3.2095 +	
  3.2096 +   <p class="issue" id="issue-5862943f"><a class="self-link" href="#issue-5862943f"></a>
  3.2097 +		This inheritance rule allows specifying styles indirectly
  3.2098 +		(by using explicit <a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-cascade-3/#valuedef-inherit">inherit</a> or using default inheritance
  3.2099 +		on properties that don’t apply to <span class="css">:first-letter</span>)
  3.2100 +		that can’t be specified directly
  3.2101 +		(based on the rules in the next section).
  3.2102 +		This is a problem.
  3.2103 +		The restrictions that apply to styling inside fragments
  3.2104 +		should also apply to inheritance from fragments.
  3.2105 +	</p>
  3.2106  
  3.2107 -  <p> To match the model for other pseudo-elements where the pseudo-elements
  3.2108 -   live inside their corresponding element, declarations in ‘<code
  3.2109 -   class=css>::nth-fragment()</code>’ pseudo-elements override declarations
  3.2110 -   in rules without the pseudo-element. The relative priority within such
  3.2111 -   declarations is determined by normal cascading order (see <a
  3.2112 -   href="#ref-CSS21">[CSS21]<!--{{!CSS21}}--></a>).
  3.2113 -
  3.2114 -  <p> Styles specified on ‘<code class=css>::nth-fragment()</code>’
  3.2115 -   pseudo-elements do affect inheritance to content within the <a
  3.2116 -   href="#fragment-box"><i>fragment box</i></a>. In other words, the content
  3.2117 -   within the <a href="#fragment-box"><i>fragment box</i></a> must inherit
  3.2118 -   from the fragment box's style (i.e., the pseudo-element style) rather than
  3.2119 -   directly from the element. This means that elements split between fragment
  3.2120 -   boxes may have different styles for different parts of the element.
  3.2121 -
  3.2122 -  <p class=issue> This inheritance rule allows specifying styles indirectly
  3.2123 -   (by using explicit ‘<code class=css>inherit</code>’ or using default
  3.2124 -   inheritance on properties that don't apply to ‘<code
  3.2125 -   class=css>:first-letter</code>’) that can't be specified directly (based
  3.2126 -   on the rules in the next section). This is a problem. The restrictions
  3.2127 -   that apply to styling inside fragments should also apply to inheritance
  3.2128 -   from fragments.
  3.2129 -
  3.2130 -  <div class=example>
  3.2131 -   <table class=source-demo-pair>
  3.2132 -    <tbody>
  3.2133 -     <tr>
  3.2134 -      <td>
  3.2135 -       <pre>&lt;!DOCTYPE HTML&gt;
  3.2136 -&lt;style&gt;
  3.2137 +	
  3.2138 +   <div class="example">
  3.2139 +		
  3.2140 +    <table class="source-demo-pair">
  3.2141 +     <tbody>
  3.2142 +      <tr>
  3.2143 +       <td>
  3.2144 +        <pre>&lt;!DOCTYPE HTML>
  3.2145 +&lt;style>
  3.2146    .article {
  3.2147      overflow: fragments;
  3.2148    }
  3.2149 @@ -1132,71 +1320,95 @@
  3.2150      margin-left: 5em;
  3.2151      margin-right: 2em;
  3.2152    }
  3.2153 -&lt;/style&gt;
  3.2154 -&lt;div class="article"&gt;
  3.2155 -  The &lt;code&gt;font-size&lt;/code&gt; property<i>...</i>
  3.2156 -&lt;/div&gt;</pre>
  3.2157 +&lt;/style>
  3.2158 +&lt;div class="article">
  3.2159 +  The &lt;code>font-size&lt;/code> property<i>...</i>
  3.2160 +&lt;/div></pre>
  3.2161 +       <td>
  3.2162 +			
  3.2163 +        <div class="article-font-inherit-demo one">The <code>font-size</code> property<br>specified on the fragment<br>is inherited into the</div>
  3.2164 +        
  3.2165 +			
  3.2166 +        <div class="article-font-inherit-demo two">descendants of the fragment.<br>This means that inherited<br>properties can be used<br>reliably on a fragment, as in<br>this example.</div>
  3.2167 +        
  3.2168 +		
  3.2169 +    </table>
  3.2170 +    
  3.2171 +	
  3.2172 +   </div>
  3.2173  
  3.2174 -      <td>
  3.2175 -       <div class="article-font-inherit-demo one">The <code>font-size</code>
  3.2176 -        property<br>
  3.2177 -        specified on the fragment<br>
  3.2178 -        is inherited into the</div>
  3.2179  
  3.2180 -       <div class="article-font-inherit-demo two">descendants of the
  3.2181 -        fragment.<br>
  3.2182 -        This means that inherited<br>
  3.2183 -        properties can be used<br>
  3.2184 -        reliably on a fragment, as in<br>
  3.2185 -        this example.</div>
  3.2186 -   </table>
  3.2187 -  </div>
  3.2188 +   <h4 class="heading settled" data-level="6.1.3" id="style-in-fragments"><span class="secno">6.1.3. </span><span class="content">Styling inside fragments</span><a class="self-link" href="#style-in-fragments"></a></h4>
  3.2189  
  3.2190 -  <h4 id=style-in-fragments><span class=secno>6.1.3. </span>Styling inside
  3.2191 -   fragments</h4>
  3.2192 +	
  3.2193 +   <p class="issue" id="issue-b1e468e3"><a class="self-link" href="#issue-b1e468e3"></a>
  3.2194 +		Should this apply to fragment overflow only,
  3.2195 +		or also to paginated overflow,
  3.2196 +		or even to pagination across pages?
  3.2197 +	</p>
  3.2198  
  3.2199 -  <p class=issue> Should this apply to fragment overflow only, or also to
  3.2200 -   paginated overflow, or even to pagination across pages?
  3.2201 +	
  3.2202 +   <p>
  3.2203 +		The <span class="css">::nth-fragment()</span> pseudo-element
  3.2204 +		can also be used to style
  3.2205 +		content inside of a <a data-link-type="dfn" href="#fragment-box">fragment box</a>.
  3.2206 +		Unlike the <a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-pseudo-4/#selectordef-first-line">::first-line</a> and <span class="css">::first-letter</span> pseudo-elements,
  3.2207 +		the <span class="css">::nth-fragment()</span> pseudo-element can be applied
  3.2208 +		to parts of the selector other than the subject:
  3.2209 +		in particular, it can match ancestors of the subject.
  3.2210 +		However, the only CSS properties applied
  3.2211 +		by rules with such selectors
  3.2212 +		are those that apply
  3.2213 +		to the <span class="css">::first-letter</span> pseudo-element.
  3.2214 +	</p>
  3.2215  
  3.2216 -  <p> The ‘<code class=css>::nth-fragment()</code>’ pseudo-element can
  3.2217 -   also be used to style content inside of a <a
  3.2218 -   href="#fragment-box"><i>fragment box</i></a>. Unlike the ‘<code
  3.2219 -   class=css>::first-line</code>’ and ‘<code
  3.2220 -   class=css>::first-letter</code>’ pseudo-elements, the ‘<code
  3.2221 -   class=css>::nth-fragment()</code>’ pseudo-element can be applied to
  3.2222 -   parts of the selector other than the subject: in particular, it can match
  3.2223 -   ancestors of the subject. However, the only CSS properties applied by
  3.2224 -   rules with such selectors are those that apply to the ‘<code
  3.2225 -   class=css>::first-letter</code>’ pseudo-element.
  3.2226 +	
  3.2227 +   <p>
  3.2228 +		To be more precise,
  3.2229 +		when a rule’s selector has <span class="css">::nth-fragment()</span> pseudo-elements
  3.2230 +		attached to parts of the selector other than the subject,
  3.2231 +		the declarations in that rule apply to
  3.2232 +		a fragment (or pseudo-element thereof) when:
  3.2233 +	</p>
  3.2234 +	
  3.2235 +   <ol>
  3.2236 +		
  3.2237 +    <li>
  3.2238 +			the declarations are for properties that apply to the
  3.2239 +			<span class="css">::first-letter</span> pseudo-element,
  3.2240 +		
  3.2241 +    
  3.2242 +		
  3.2243 +    <li>
  3.2244 +			the declarations would apply to
  3.2245 +			that fragment (or pseudo-element thereof)
  3.2246 +			had those <span class="css">::nth-fragment()</span> pseudo-elements been removed,
  3.2247 +			with a particular association between
  3.2248 +			each sequence of simple selectors and the element it matched,
  3.2249 +			and
  3.2250 +		
  3.2251 +    
  3.2252 +		
  3.2253 +    <li>
  3.2254 +			for each removed <span class="css">::nth-fragment()</span> pseudo-element,
  3.2255 +			the fragment lives within a <a data-link-type="dfn" href="#fragment-box">fragment box</a>
  3.2256 +			of the element associated in that association
  3.2257 +			with the selector that the pseudo-element was attached to,
  3.2258 +			and whose index matches the pseudo-element.
  3.2259 +		
  3.2260 +    
  3.2261 +	
  3.2262 +   </ol>
  3.2263  
  3.2264 -  <p> To be more precise, when a rule's selector has ‘<code
  3.2265 -   class=css>::nth-fragment()</code>’ pseudo-elements attached to parts of
  3.2266 -   the selector other than the subject, the declarations in that rule apply
  3.2267 -   to a fragment (or pseudo-element thereof) when:
  3.2268 -
  3.2269 -  <ol>
  3.2270 -   <li> the declarations are for properties that apply to the ‘<code
  3.2271 -    class=css>::first-letter</code>’ pseudo-element,
  3.2272 -
  3.2273 -   <li> the declarations would apply to that fragment (or pseudo-element
  3.2274 -    thereof) had those ‘<code class=css>::nth-fragment()</code>’
  3.2275 -    pseudo-elements been removed, with a particular association between each
  3.2276 -    sequence of simple selectors and the element it matched, and
  3.2277 -
  3.2278 -   <li> for each removed ‘<code class=css>::nth-fragment()</code>’
  3.2279 -    pseudo-element, the fragment lives within a <a
  3.2280 -    href="#fragment-box"><i>fragment box</i></a> of the element associated in
  3.2281 -    that association with the selector that the pseudo-element was attached
  3.2282 -    to, and whose index matches the pseudo-element.
  3.2283 -  </ol>
  3.2284 -
  3.2285 -  <div class=example>
  3.2286 -   <table class=source-demo-pair>
  3.2287 -    <tbody>
  3.2288 -     <tr>
  3.2289 -      <td>
  3.2290 -       <pre>&lt;!DOCTYPE HTML&gt;
  3.2291 -&lt;style&gt;
  3.2292 +	
  3.2293 +   <div class="example">
  3.2294 +		
  3.2295 +    <table class="source-demo-pair">
  3.2296 +     <tbody>
  3.2297 +      <tr>
  3.2298 +       <td>
  3.2299 +        <pre>&lt;!DOCTYPE HTML>
  3.2300 +&lt;style>
  3.2301    .dark-columns {
  3.2302      overflow: fragments;
  3.2303      width: 6em;
  3.2304 @@ -1224,132 +1436,171 @@
  3.2305    .dark-columns::nth-fragment(2) :visited {
  3.2306      color: fuchsia;
  3.2307    }
  3.2308 -&lt;/style&gt;
  3.2309 -&lt;div class="dark-columns"&gt;
  3.2310 +&lt;/style>
  3.2311 +&lt;div class="dark-columns">
  3.2312    <i>...</i>
  3.2313 -&lt;/div&gt;</pre>
  3.2314 +&lt;/div></pre>
  3.2315 +       <td>
  3.2316 +			
  3.2317 +        <div class="dark-columns-demo one">In this<br><a href="http://en.wiktionary.org/wiki/example">example</a>, the<br>text flows<br>from one<br>light-colored<br>fragment into<br>another<br>dark-colored</div>
  3.2318 +        
  3.2319 +			
  3.2320 +        <div class="dark-columns-demo two">fragment.  We<br>therefore want<br>different styles<br>for <a href="http://www.w3.org/Provider/Style/IntoContext.html">hyperlinks</a><br>in the different<br>fragments.</div>
  3.2321 +        
  3.2322 +		
  3.2323 +    </table>
  3.2324 +    
  3.2325 +	
  3.2326 +   </div>
  3.2327  
  3.2328 -      <td>
  3.2329 -       <div class="dark-columns-demo one">In this<br>
  3.2330 -        <a href="http://en.wiktionary.org/wiki/example">example</a>, the<br>
  3.2331 -        text flows<br>
  3.2332 -        from one<br>
  3.2333 -        light-colored<br>
  3.2334 -        fragment into<br>
  3.2335 -        another<br>
  3.2336 -        dark-colored</div>
  3.2337  
  3.2338 -       <div class="dark-columns-demo two">fragment. We<br>
  3.2339 -        therefore want<br>
  3.2340 -        different styles<br>
  3.2341 -        for <a
  3.2342 -        href="http://www.w3.org/Provider/Style/IntoContext.html">hyperlinks</a><br>
  3.2343 -        in the different<br>
  3.2344 -        fragments.</div>
  3.2345 -   </table>
  3.2346 -  </div>
  3.2347  
  3.2348 -  <h3 id=max-lines><span class=secno>6.2. </span>The ‘<a
  3.2349 -   href="#max-lines0"><code class=property>max-lines</code></a>’ property</h3>
  3.2350 +   <h3 class="heading settled" data-level="6.2" id="max-lines"><span class="secno">6.2. </span><span class="content">The <a class="property" data-link-type="propdesc" href="#propdef-max-lines">max-lines</a> property</span><a class="self-link" href="#max-lines"></a></h3>
  3.2351  
  3.2352 -  <p> Authors may wish to style the opening lines of an element with
  3.2353 -   different styles by putting those opening lines in a separate fragment.
  3.2354 -   However, since it may be difficult to predict the exact height occupied by
  3.2355 -   those lines in order to restrict the first fragment to that height, this
  3.2356 -   specification introduces a ‘<a href="#max-lines0"><code
  3.2357 -   class=property>max-lines</code></a>’ property that forces a fragment to
  3.2358 -   break after a specified number of lines. This forces a break after the
  3.2359 -   given number of lines contained within the element or its descendants, as
  3.2360 -   long as those lines are in the same block formatting context.
  3.2361 +	
  3.2362 +   <p>
  3.2363 +		Authors may wish to style the opening lines of an element
  3.2364 +		with different styles
  3.2365 +		by putting those opening lines in a separate fragment.
  3.2366 +		However, since it may be difficult to predict the exact height
  3.2367 +		occupied by those lines
  3.2368 +		in order to restrict the first fragment to that height,
  3.2369 +		this specification introduces a <a class="property" data-link-type="propdesc" href="#propdef-max-lines">max-lines</a> property
  3.2370 +		that forces a fragment to break
  3.2371 +		after a specified number of lines.
  3.2372 +		This forces a break after the given number of lines
  3.2373 +		contained within the element or its descendants,
  3.2374 +		as long as those lines are in the same block formatting context.
  3.2375 +	</p>
  3.2376  
  3.2377 -  <table class=propdef>
  3.2378 -   <tbody>
  3.2379 -    <tr>
  3.2380 -     <th>Name:
  3.2381 -
  3.2382 -     <td><dfn id=max-lines0>max-lines</dfn>
  3.2383 -
  3.2384 -    <tr>
  3.2385 -     <th><a href="#values">Value</a>:
  3.2386 -
  3.2387 -     <td>none | &lt;integer&gt;
  3.2388 -
  3.2389 -    <tr>
  3.2390 -     <th>Initial:
  3.2391 -
  3.2392 -     <td>none
  3.2393 -
  3.2394 -    <tr>
  3.2395 -     <th>Applies to:
  3.2396 -
  3.2397 -     <td>fragment boxes
  3.2398 -
  3.2399 -    <tr>
  3.2400 -     <th>Inherited:
  3.2401 -
  3.2402 -     <td>no
  3.2403 -
  3.2404 -    <tr>
  3.2405 -     <th>Animatable:
  3.2406 -
  3.2407 -     <td>as <a
  3.2408 -      href="http://www.w3.org/TR/css3-transitions/#animatable-types">integer</a>
  3.2409 -
  3.2410 -    <tr>
  3.2411 -     <th>Percentages:
  3.2412 -
  3.2413 -     <td>N/A
  3.2414 -
  3.2415 -    <tr>
  3.2416 -     <th>Media:
  3.2417 -
  3.2418 -     <td>visual
  3.2419 -
  3.2420 -    <tr>
  3.2421 -     <th>Computed value:
  3.2422 -
  3.2423 -     <td>specified value
  3.2424 -
  3.2425 -    <tr>
  3.2426 -     <th>Canonical order:
  3.2427 -
  3.2428 -     <td><abbr title="follows order of property value definition">per
  3.2429 -      grammar</abbr>
  3.2430 -  </table>
  3.2431 -
  3.2432 -  <dl>
  3.2433 -   <dt>none
  3.2434 -
  3.2435 -   <dd>
  3.2436 -    <p> Breaks occur only as specified elsewhere.
  3.2437 -
  3.2438 -   <dt>&lt;integer&gt;
  3.2439 -
  3.2440 -   <dd>
  3.2441 -    <p> In addition to any breaks specified elsewhere, a break is forced
  3.2442 -     before any line that would exceed the given number of lines being placed
  3.2443 -     inside the element (excluding lines that are in a different block
  3.2444 -     formatting context from the block formatting context to which an
  3.2445 -     unstyled child of the element would belong).
  3.2446 -
  3.2447 -    <p class=issue> If there are multiple boundaries between this line and
  3.2448 -     the previous, where exactly (in terms of element boundaries) is the
  3.2449 -     break forced?
  3.2450 -
  3.2451 -    <p> Only positive integers are accepted. Zero or negative integers are a
  3.2452 -     parse error.
  3.2453 -  </dl>
  3.2454 -
  3.2455 -  <p class=issue>Should this apply to fragment overflow only, or also to
  3.2456 -   pagination?
  3.2457 -
  3.2458 -  <div class=example>
  3.2459 -   <table class=source-demo-pair>
  3.2460 +	
  3.2461 +   <table class="propdef">
  3.2462 +		
  3.2463      <tbody>
  3.2464       <tr>
  3.2465 -      <td>
  3.2466 -       <pre>&lt;!DOCTYPE HTML&gt;
  3.2467 -&lt;style&gt;
  3.2468 +			
  3.2469 +      <th>Name:
  3.2470 +			
  3.2471 +      <td><dfn class="css" data-dfn-type="property" data-export="" id="propdef-max-lines">max-lines<a class="self-link" href="#propdef-max-lines"></a></dfn>
  3.2472 +     <tr>
  3.2473 +			
  3.2474 +      <th>Value:
  3.2475 +			
  3.2476 +      <td>none | &lt;integer>
  3.2477 +		
  3.2478 +     <tr>
  3.2479 +			
  3.2480 +      <th>Initial:
  3.2481 +			
  3.2482 +      <td>none
  3.2483 +		
  3.2484 +     <tr>
  3.2485 +			
  3.2486 +      <th>Applies to:
  3.2487 +			
  3.2488 +      <td>fragment boxes
  3.2489 +		
  3.2490 +     <tr>
  3.2491 +			
  3.2492 +      <th>Inherited:
  3.2493 +			
  3.2494 +      <td>no
  3.2495 +		
  3.2496 +     <tr>
  3.2497 +			
  3.2498 +      <th>Animatable:
  3.2499 +			
  3.2500 +      <td>as <a href="http://www.w3.org/TR/css3-transitions/#animatable-types">integer</a>
  3.2501 +		
  3.2502 +     <tr>
  3.2503 +			
  3.2504 +      <th>Percentages:
  3.2505 +			
  3.2506 +      <td>N/A
  3.2507 +		
  3.2508 +     <tr>
  3.2509 +			
  3.2510 +      <th>Media:
  3.2511 +			
  3.2512 +      <td>visual
  3.2513 +		
  3.2514 +     <tr>
  3.2515 +			
  3.2516 +      <th>Computed value:
  3.2517 +			
  3.2518 +      <td>specified value
  3.2519 +		
  3.2520 +     <tr>
  3.2521 +			
  3.2522 +      <th>Canonical order:
  3.2523 +			
  3.2524 +      <td><abbr title="follows order of property value definition">per grammar</abbr>
  3.2525 +	
  3.2526 +   </table>
  3.2527 +
  3.2528 +	
  3.2529 +   <dl>
  3.2530 +		
  3.2531 +    <dt><dfn class="css" data-dfn-for="max-lines" data-dfn-type="value" data-export="" id="valdef-max-lines-none">none<a class="self-link" href="#valdef-max-lines-none"></a></dfn>
  3.2532 +		
  3.2533 +    <dd>
  3.2534 +			
  3.2535 +     <p>
  3.2536 +				Breaks occur only as specified elsewhere.
  3.2537 +			</p>
  3.2538 +     
  3.2539 +		
  3.2540 +    
  3.2541 +
  3.2542 +		
  3.2543 +    <dt><dfn class="css" data-dfn-for="max-lines" data-dfn-type="value" data-export="" id="valdef-max-lines-integer">&lt;integer><a class="self-link" href="#valdef-max-lines-integer"></a></dfn>
  3.2544 +		
  3.2545 +    <dd>
  3.2546 +			
  3.2547 +     <p>
  3.2548 +				In addition to any breaks specified elsewhere,
  3.2549 +				a break is forced before any line that would exceed
  3.2550 +				the given number of lines
  3.2551 +				being placed inside the element
  3.2552 +				(excluding lines that are in
  3.2553 +				a different block formatting context from
  3.2554 +				the block formatting context to which
  3.2555 +				an unstyled child of the element would belong).
  3.2556 +			</p>
  3.2557 +     
  3.2558 +
  3.2559 +			
  3.2560 +     <p class="issue" id="issue-9488ec29"><a class="self-link" href="#issue-9488ec29"></a>
  3.2561 +				If there are multiple boundaries between this line
  3.2562 +				and the previous, where exactly (in terms of element
  3.2563 +				boundaries) is the break forced?
  3.2564 +			</p>
  3.2565 +     
  3.2566 +
  3.2567 +			
  3.2568 +     <p>
  3.2569 +				Only positive integers are accepted.
  3.2570 +				Zero or negative integers are a parse error.
  3.2571 +			</p>
  3.2572 +     
  3.2573 +		
  3.2574 +    
  3.2575 +	
  3.2576 +   </dl>
  3.2577 +
  3.2578 +
  3.2579 +   <p class="issue" id="issue-1527f8dd"><a class="self-link" href="#issue-1527f8dd"></a>Should this apply to fragment overflow only, or also
  3.2580 +to pagination?</p>
  3.2581 +
  3.2582 +	
  3.2583 +   <div class="example">
  3.2584 +		
  3.2585 +    <table class="source-demo-pair">
  3.2586 +     <tbody>
  3.2587 +      <tr>
  3.2588 +       <td>
  3.2589 +        <pre>&lt;!DOCTYPE HTML>
  3.2590 +&lt;style>
  3.2591    .article {
  3.2592      overflow: fragments;
  3.2593    }
  3.2594 @@ -1364,663 +1615,543 @@
  3.2595    .article::nth-fragment(2) {
  3.2596      column-count: 2;
  3.2597    }
  3.2598 -&lt;/style&gt;
  3.2599 -&lt;div class="article"&gt;
  3.2600 +&lt;/style>
  3.2601 +&lt;div class="article">
  3.2602    <i>...</i>
  3.2603 -&lt;/div&gt;</pre>
  3.2604 +&lt;/div></pre>
  3.2605 +       <td>
  3.2606 +			
  3.2607 +        <div class="article-max-lines-demo one">The max-lines property allows<br>authors to use a larger font for the first<br>few lines of an article.  Without the</div>
  3.2608 +        
  3.2609 +			
  3.2610 +        <div class="article-max-lines-demo two">max-lines property, authors<br>might have to use the<br><a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css2/visudet.html#propdef-height">height</a> property instead, but<br>that would leave a slight gap<br>if the author miscalculated<br>how much height a given<br>number of lines would<br>occupy (which might be</div>
  3.2611 +        
  3.2612 +			
  3.2613 +        <div class="article-max-lines-demo three">particularly hard if the author<br>didn’t know what text would<br>be filling the space, exactly<br>what font would be used, or<br>exactly which platform’s font<br>rendering would be used to<br>display the font).</div>
  3.2614 +        
  3.2615 +		
  3.2616 +    </table>
  3.2617 +    
  3.2618 +	
  3.2619 +   </div>
  3.2620  
  3.2621 -      <td>
  3.2622 -       <div class="article-max-lines-demo one">The max-lines property
  3.2623 -        allows<br>
  3.2624 -        authors to use a larger font for the first<br>
  3.2625 -        few lines of an article. Without the</div>
  3.2626  
  3.2627 -       <div class="article-max-lines-demo two">max-lines property,
  3.2628 -        authors<br>
  3.2629 -        might have to use the<br>
  3.2630 -        ‘<code class=property>height</code>’ property instead, but<br>
  3.2631 -        that would leave a slight gap<br>
  3.2632 -        if the author miscalculated<br>
  3.2633 -        how much height a given<br>
  3.2634 -        number of lines would<br>
  3.2635 -        occupy (which might be</div>
  3.2636 +   <h2 class="heading settled" data-level="7" id="static-media"><span class="secno">7. </span><span class="content">Overflow in static media</span><a class="self-link" href="#static-media"></a></h2>
  3.2637  
  3.2638 -       <div class="article-max-lines-demo three">particularly hard if the
  3.2639 -        author<br>
  3.2640 -        didn't know what text would<br>
  3.2641 -        be filling the space, exactly<br>
  3.2642 -        what font would be used, or<br>
  3.2643 -        exactly which platform's font<br>
  3.2644 -        rendering would be used to<br>
  3.2645 -        display the font).</div>
  3.2646 -   </table>
  3.2647 +	
  3.2648 +   <p class="issue" id="issue-5ad703cc"><a class="self-link" href="#issue-5ad703cc"></a>
  3.2649 +		This specification should define useful behavior
  3.2650 +		for all values of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>
  3.2651 +		in static media (such as print).
  3.2652 +		Current implementation behavior is quite poor and
  3.2653 +		produces unexpected results when authors have not considered
  3.2654 +		what will happen when
  3.2655 +		the content they produce for interactive media
  3.2656 +		is printed.
  3.2657 +	</p>
  3.2658 +
  3.2659 +
  3.2660 +   <h2 class="no-num heading settled" id="acknowledgments"><span class="content">
  3.2661 +Acknowledgments</span><a class="self-link" href="#acknowledgments"></a></h2>
  3.2662 +
  3.2663 +	
  3.2664 +   <p>
  3.2665 +		Thanks especially to the feedback from
  3.2666 +		Rossen Atanassov,
  3.2667 +		Bert Bos,
  3.2668 +		Tantek Çelik,
  3.2669 +		John Daggett,
  3.2670 +		fantasai,
  3.2671 +		Daniel Glazman,
  3.2672 +		Vincent Hardy,
  3.2673 +		Håkon Wium Lie,
  3.2674 +		Peter Linss,
  3.2675 +		Robert O’Callahan,
  3.2676 +		Florian Rivoal,
  3.2677 +		Alan Stearns,
  3.2678 +		Steve Zilles,
  3.2679 +		and all the rest of the
  3.2680 +		<a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> community.
  3.2681 +	</p>
  3.2682 +
  3.2683 +</main>
  3.2684 +
  3.2685 +  <h2 class="no-ref no-num heading settled" id="conformance"><span class="content">
  3.2686 +Conformance</span><a class="self-link" href="#conformance"></a></h2>
  3.2687 +
  3.2688 +
  3.2689 +  <h3 class="no-ref heading settled" id="conventions"><span class="content">
  3.2690 +Document conventions</span><a class="self-link" href="#conventions"></a></h3>
  3.2691 +
  3.2692 +    
  3.2693 +  <p>Conformance requirements are expressed with a combination of
  3.2694 +    descriptive assertions and RFC 2119 terminology. The key words "MUST",
  3.2695 +    "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
  3.2696 +    "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
  3.2697 +    document are to be interpreted as described in RFC 2119.
  3.2698 +    However, for readability, these words do not appear in all uppercase
  3.2699 +    letters in this specification.
  3.2700 +
  3.2701 +    </p>
  3.2702 +  <p>All of the text of this specification is normative except sections
  3.2703 +    explicitly marked as non-normative, examples, and notes. <a data-link-type="biblio" href="#biblio-rfc2119">[RFC2119]</a></p>
  3.2704 +
  3.2705 +    
  3.2706 +  <p>Examples in this specification are introduced with the words "for example"
  3.2707 +    or are set apart from the normative text with <code>class="example"</code>,
  3.2708 +    like this:
  3.2709 +
  3.2710 +    </p>
  3.2711 +  <div class="example">
  3.2712 +        
  3.2713 +   <p>This is an example of an informative example.</p>
  3.2714 +   
  3.2715 +    
  3.2716    </div>
  3.2717  
  3.2718 -  <h2 id=static-media><span class=secno>7. </span>Overflow in static media</h2>
  3.2719 +    
  3.2720 +  <p>Informative notes begin with the word "Note" and are set apart from the
  3.2721 +    normative text with <code>class="note"</code>, like this:
  3.2722  
  3.2723 -  <p class=issue> This specification should define useful behavior for all
  3.2724 -   values of ‘<a href="#overflow0"><code
  3.2725 -   class=property>overflow</code></a>’ in static media (such as print).
  3.2726 -   Current implementation behavior is quite poor and produces unexpected
  3.2727 -   results when authors have not considered what will happen when the content
  3.2728 -   they produce for interactive media is printed.
  3.2729 +    </p>
  3.2730 +  <p class="note" role="note">Note, this is an informative note.</p>
  3.2731  
  3.2732 -  <h2 id=conformance><span class=secno>8. </span> Conformance</h2>
  3.2733 +    
  3.2734 +  <p>Advisements are normative sections styled to evoke special attention and are
  3.2735 +    set apart from other normative text with <code>&lt;strong class="advisement"></code>, like
  3.2736 +    this:
  3.2737  
  3.2738 -  <h3 id=placement><span class=secno>8.1. </span> Module interactions</h3>
  3.2739 +    <strong class="advisement">
  3.2740 +        UAs MUST provide an accessible alternative.
  3.2741 +    </strong>
  3.2742  
  3.2743 -  <p>This module extends the ‘<a href="#overflow0"><code
  3.2744 -   class=property>overflow</code></a>’ feature defined in <a
  3.2745 -   href="#ref-CSS21">[CSS21]<!--{{CSS21}}--></a> section 11.1.1. It defines
  3.2746 -   additional overflow handling mechanisms that implementations must
  3.2747 -   implement as described in this module in order to conform to this module.
  3.2748 +</p>
  3.2749 +  <h3 class="no-ref heading settled" id="conformance-classes"><span class="content">
  3.2750 +Conformance classes</span><a class="self-link" href="#conformance-classes"></a></h3>
  3.2751  
  3.2752 -  <p>No properties in this module apply to the <code>::first-line</code> or
  3.2753 -   <code>::first-letter</code> pseudo-elements.
  3.2754 -
  3.2755 -  <h3 id=values><span class=secno>8.2. </span> Values</h3>
  3.2756 -
  3.2757 -  <p>This specification follows the <a
  3.2758 -   href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
  3.2759 -   definition conventions</a> from <a
  3.2760 -   href="#ref-CSS21">[CSS21]<!--{{!CSS21}}--></a>. Value types not defined in
  3.2761 -   this specification are defined in CSS Level 2 Revision 1 <a
  3.2762 -   href="#ref-CSS21">[CSS21]<!--{{!CSS21}}--></a>. Other CSS modules may
  3.2763 -   expand the definitions of these value types: for example <a
  3.2764 -   href="#ref-CSS3COLOR">[CSS3COLOR]<!--{{CSS3COLOR}}--></a>, when combined
  3.2765 -   with this module, expands the definition of the &lt;color&gt; value type
  3.2766 -   as used in this specification.
  3.2767 -
  3.2768 -  <p>In addition to the property-specific values listed in their definitions,
  3.2769 -   all properties defined in this specification also accept the <a
  3.2770 -   href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a>
  3.2771 -   keyword as their property value. For readability it has not been repeated
  3.2772 -   explicitly.
  3.2773 -
  3.2774 -  <h3 id=conventions><span class=secno>8.3. </span> Document conventions</h3>
  3.2775 -
  3.2776 -  <p>Conformance requirements are expressed with a combination of descriptive
  3.2777 -   assertions and RFC 2119 terminology. The key words “MUST”, “MUST
  3.2778 -   NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
  3.2779 -   “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the
  3.2780 -   normative parts of this document are to be interpreted as described in RFC
  3.2781 -   2119. However, for readability, these words do not appear in all uppercase
  3.2782 -   letters in this specification.
  3.2783 -
  3.2784 -  <p>All of the text of this specification is normative except sections
  3.2785 -   explicitly marked as non-normative, examples, and notes. <a
  3.2786 -   href="#ref-RFC2119">[RFC2119]<!--{{!RFC2119}}--></a>
  3.2787 -
  3.2788 -  <p>Examples in this specification are introduced with the words “for
  3.2789 -   example” or are set apart from the normative text with
  3.2790 -   <code>class="example"</code>, like this:
  3.2791 -
  3.2792 -  <div class=example>
  3.2793 -   <p>This is an example of an informative example.
  3.2794 -  </div>
  3.2795 -
  3.2796 -  <p>Informative notes begin with the word “Note” and are set apart from
  3.2797 -   the normative text with <code>class="note"</code>, like this:
  3.2798 -
  3.2799 -  <p class=note>Note, this is an informative note.
  3.2800 -
  3.2801 -  <h3 id=conformance-classes><span class=secno>8.4. </span> Conformance
  3.2802 -   classes</h3>
  3.2803 -
  3.2804 -  <p>Conformance to CSS Overflow Module Level 3 is defined for three
  3.2805 -   conformance classes:
  3.2806 -
  3.2807 +    
  3.2808 +  <p>Conformance to this specification
  3.2809 +    is defined for three conformance classes:
  3.2810 +    </p>
  3.2811    <dl>
  3.2812 -   <dt><dfn id=style-sheet title="style sheet!!as conformance class">style
  3.2813 -    sheet</dfn>
  3.2814 -
  3.2815 +        
  3.2816 +   <dt>style sheet
  3.2817 +            
  3.2818     <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
  3.2819 -    style sheet</a>.
  3.2820 -
  3.2821 -   <dt><dfn id=renderer>renderer</dfn>
  3.2822 -
  3.2823 +            style sheet</a>.
  3.2824 +        
  3.2825 +   <dt>renderer
  3.2826 +            
  3.2827     <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
  3.2828 -    that interprets the semantics of a style sheet and renders documents that
  3.2829 -    use them.
  3.2830 -
  3.2831 -   <dt><dfn id=authoring-tool>authoring tool</dfn>
  3.2832 -
  3.2833 +            that interprets the semantics of a style sheet and renders
  3.2834 +            documents that use them.
  3.2835 +        
  3.2836 +   <dt>authoring tool
  3.2837 +            
  3.2838     <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
  3.2839 -    that writes a style sheet.
  3.2840 +            that writes a style sheet.
  3.2841 +    
  3.2842    </dl>
  3.2843  
  3.2844 -  <p>A style sheet is conformant to CSS Overflow Module Level 3 if all of its
  3.2845 -   statements that use syntax defined in this module are valid according to
  3.2846 -   the generic CSS grammar and the individual grammars of each feature
  3.2847 -   defined in this module.
  3.2848 +    
  3.2849 +  <p>A style sheet is conformant to this specification
  3.2850 +    if all of its statements that use syntax defined in this module are valid
  3.2851 +    according to the generic CSS grammar and the individual grammars of each
  3.2852 +    feature defined in this module.
  3.2853  
  3.2854 -  <p>A renderer is conformant to CSS Overflow Module Level 3 if, in addition
  3.2855 -   to interpreting the style sheet as defined by the appropriate
  3.2856 -   specifications, it supports all the features defined by CSS Overflow
  3.2857 -   Module Level 3 by parsing them correctly and rendering the document
  3.2858 -   accordingly. However, the inability of a UA to correctly render a document
  3.2859 -   due to limitations of the device does not make the UA non-conformant. (For
  3.2860 -   example, a UA is not required to render color on a monochrome monitor.)
  3.2861 +    </p>
  3.2862 +  <p>A renderer is conformant to this specification
  3.2863 +    if, in addition to interpreting the style sheet as defined by the
  3.2864 +    appropriate specifications, it supports all the features defined
  3.2865 +    by this specification by parsing them correctly
  3.2866 +    and rendering the document accordingly. However, the inability of a
  3.2867 +    UA to correctly render a document due to limitations of the device
  3.2868 +    does not make the UA non-conformant. (For example, a UA is not
  3.2869 +    required to render color on a monochrome monitor.)
  3.2870  
  3.2871 -  <p>An authoring tool is conformant to CSS Overflow Module Level 3 if it
  3.2872 -   writes style sheets that are syntactically correct according to the
  3.2873 -   generic CSS grammar and the individual grammars of each feature in this
  3.2874 -   module, and meet all other conformance requirements of style sheets as
  3.2875 -   described in this module.
  3.2876 +    </p>
  3.2877 +  <p>An authoring tool is conformant to this specification
  3.2878 +    if it writes style sheets that are syntactically correct according to the
  3.2879 +    generic CSS grammar and the individual grammars of each feature in
  3.2880 +    this module, and meet all other conformance requirements of style sheets
  3.2881 +    as described in this module.
  3.2882  
  3.2883 -  <h3 id=partial><span class=secno>8.5. </span> Partial implementations</h3>
  3.2884 +</p>
  3.2885 +  <h3 class="no-ref heading settled" id="partial"><span class="content">
  3.2886 +Partial implementations</span><a class="self-link" href="#partial"></a></h3>
  3.2887  
  3.2888 +    
  3.2889    <p>So that authors can exploit the forward-compatible parsing rules to
  3.2890 -   assign fallback values, CSS renderers <strong>must</strong> treat as
  3.2891 -   invalid (and <a
  3.2892 -   href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore as
  3.2893 -   appropriate</a>) any at-rules, properties, property values, keywords, and
  3.2894 -   other syntactic constructs for which they have no usable level of support.
  3.2895 -   In particular, user agents <strong>must not</strong> selectively ignore
  3.2896 -   unsupported component values and honor supported values in a single
  3.2897 -   multi-value property declaration: if any value is considered invalid (as
  3.2898 -   unsupported values must be), CSS requires that the entire declaration be
  3.2899 -   ignored.
  3.2900 +    assign fallback values, CSS renderers <strong>must</strong>
  3.2901 +    treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
  3.2902 +    as appropriate</a>) any at-rules, properties, property values, keywords,
  3.2903 +    and other syntactic constructs for which they have no usable level of
  3.2904 +    support. In particular, user agents <strong>must not</strong> selectively
  3.2905 +    ignore unsupported component values and honor supported values in a single
  3.2906 +    multi-value property declaration: if any value is considered invalid
  3.2907 +    (as unsupported values must be), CSS requires that the entire declaration
  3.2908 +    be ignored.</p>
  3.2909  
  3.2910 -  <h3 id=experimental><span class=secno>8.6. </span> Experimental
  3.2911 -   implementations</h3>
  3.2912  
  3.2913 +  <h3 class="no-ref heading settled" id="experimental"><span class="content">
  3.2914 +Experimental implementations</span><a class="self-link" href="#experimental"></a></h3>
  3.2915 +
  3.2916 +    
  3.2917    <p>To avoid clashes with future CSS features, the CSS2.1 specification
  3.2918 -   reserves a <a
  3.2919 -   href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
  3.2920 -   syntax</a> for proprietary and experimental extensions to CSS.
  3.2921 +    reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
  3.2922 +    syntax</a> for proprietary and experimental extensions to CSS.
  3.2923  
  3.2924 -  <p>Prior to a specification reaching the Candidate Recommendation stage in
  3.2925 -   the W3C process, all implementations of a CSS feature are considered
  3.2926 -   experimental. The CSS Working Group recommends that implementations use a
  3.2927 -   vendor-prefixed syntax for such features, including those in W3C Working
  3.2928 -   Drafts. This avoids incompatibilities with future changes in the draft.
  3.2929 +    </p>
  3.2930 +  <p>Prior to a specification reaching the Candidate Recommendation stage
  3.2931 +    in the W3C process, all implementations of a CSS feature are considered
  3.2932 +    experimental. The CSS Working Group recommends that implementations
  3.2933 +    use a vendor-prefixed syntax for such features, including those in
  3.2934 +    W3C Working Drafts. This avoids incompatibilities with future changes
  3.2935 +    in the draft.
  3.2936 +    </p>
  3.2937  
  3.2938 -  <h3 id=testing><span class=secno>8.7. </span> Non-experimental
  3.2939 -   implementations</h3>
  3.2940  
  3.2941 +  <h3 class="no-ref heading settled" id="testing"><span class="content">
  3.2942 +Non-experimental implementations</span><a class="self-link" href="#testing"></a></h3>
  3.2943 +
  3.2944 +    
  3.2945    <p>Once a specification reaches the Candidate Recommendation stage,
  3.2946 -   non-experimental implementations are possible, and implementors should
  3.2947 -   release an unprefixed implementation of any CR-level feature they can
  3.2948 -   demonstrate to be correctly implemented according to spec.
  3.2949 +    non-experimental implementations are possible, and implementors should
  3.2950 +    release an unprefixed implementation of any CR-level feature they
  3.2951 +    can demonstrate to be correctly implemented according to spec.
  3.2952  
  3.2953 +    </p>
  3.2954    <p>To establish and maintain the interoperability of CSS across
  3.2955 -   implementations, the CSS Working Group requests that non-experimental CSS
  3.2956 -   renderers submit an implementation report (and, if necessary, the
  3.2957 -   testcases used for that implementation report) to the W3C before releasing
  3.2958 -   an unprefixed implementation of any CSS features. Testcases submitted to
  3.2959 -   W3C are subject to review and correction by the CSS Working Group.
  3.2960 +    implementations, the CSS Working Group requests that non-experimental
  3.2961 +    CSS renderers submit an implementation report (and, if necessary, the
  3.2962 +    testcases used for that implementation report) to the W3C before
  3.2963 +    releasing an unprefixed implementation of any CSS features. Testcases
  3.2964 +    submitted to W3C are subject to review and correction by the CSS
  3.2965 +    Working Group.
  3.2966  
  3.2967 +    </p>
  3.2968    <p>Further information on submitting testcases and implementation reports
  3.2969 -   can be found from on the CSS Working Group's website at <a
  3.2970 -   href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
  3.2971 -   Questions should be directed to the <a
  3.2972 -   href="http://lists.w3.org/Archives/Public/public-css-testsuite">[email protected]</a>
  3.2973 -   mailing list.
  3.2974 +    can be found from on the CSS Working Group’s website at
  3.2975 +    <a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
  3.2976 +    Questions should be directed to the
  3.2977 +    <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">[email protected]</a>
  3.2978 +    mailing list.
  3.2979  
  3.2980 -  <h3 id=cr-exit-criteria><span class=secno>8.8. </span> CR exit criteria</h3>
  3.2981  
  3.2982 -  <p class=issue>[Change or remove the following CR exit criteria if the spec
  3.2983 -   is not a module, but, e.g., a Note or a profile. This text was <a
  3.2984 -   href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on
  3.2985 -   2008-06-04.</a>]
  3.2986  
  3.2987 -  <p> For this specification to be advanced to Proposed Recommendation, there
  3.2988 -   must be at least two independent, interoperable implementations of each
  3.2989 -   feature. Each feature may be implemented by a different set of products,
  3.2990 -   there is no requirement that all features be implemented by a single
  3.2991 -   product. For the purposes of this criterion, we define the following
  3.2992 -   terms:
  3.2993 -
  3.2994 +</p>
  3.2995 +  <h2 class="no-num heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
  3.2996 +  <h3 class="no-num heading settled" id="normative"><span class="content">Normative References</span><a class="self-link" href="#normative"></a></h3>
  3.2997    <dl>
  3.2998 -   <dt>independent
  3.2999 -
  3.3000 -   <dd>each implementation must be developed by a different party and cannot
  3.3001 -    share, reuse, or derive from code used by another qualifying
  3.3002 -    implementation. Sections of code that have no bearing on the
  3.3003 -    implementation of this specification are exempt from this requirement.
  3.3004 -
  3.3005 -   <dt>interoperable
  3.3006 -
  3.3007 -   <dd>passing the respective test case(s) in the official CSS test suite,
  3.3008 -    or, if the implementation is not a Web browser, an equivalent test. Every
  3.3009 -    relevant test in the test suite should have an equivalent test created if
  3.3010 -    such a user agent (UA) is to be used to claim interoperability. In
  3.3011 -    addition if such a UA is to be used to claim interoperability, then there
  3.3012 -    must one or more additional UAs which can also pass those equivalent
  3.3013 -    tests in the same way for the purpose of interoperability. The equivalent
  3.3014 -    tests must be made publicly available for the purposes of peer review.
  3.3015 -
  3.3016 -   <dt>implementation
  3.3017 -
  3.3018 -   <dd>a user agent which:
  3.3019 -    <ol class=inline>
  3.3020 -     <li>implements the specification.
  3.3021 -
  3.3022 -     <li>is available to the general public. The implementation may be a
  3.3023 -      shipping product or other publicly available version (i.e., beta
  3.3024 -      version, preview release, or “nightly build”). Non-shipping product
  3.3025 -      releases must have implemented the feature(s) for a period of at least
  3.3026 -      one month in order to demonstrate stability.
  3.3027 -
  3.3028 -     <li>is not experimental (i.e., a version specifically designed to pass
  3.3029 -      the test suite and is not intended for normal usage going forward).
  3.3030 -    </ol>
  3.3031 +   <dt id="biblio-css21"><a class="self-link" href="#biblio-css21"></a>[CSS21]
  3.3032 +   <dd>Bert Bos; et al. <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607">Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification</a>. 7 June 2011. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a>
  3.3033 +   <dt id="biblio-css3-flexbox"><a class="self-link" href="#biblio-css3-flexbox"></a>[CSS3-FLEXBOX]
  3.3034 +   <dd>Tab Atkins Jr.; Elika J. Etemad; Alex Mogilevsky. <a href="http://www.w3.org/TR/2012/CR-css3-flexbox-20120918/">CSS Flexible Box Layout Module</a>. 18 September 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/CR-css3-flexbox-20120918/">http://www.w3.org/TR/2012/CR-css3-flexbox-20120918/</a>
  3.3035 +   <dt id="biblio-css3-grid-layout"><a class="self-link" href="#biblio-css3-grid-layout"></a>[CSS3-GRID-LAYOUT]
  3.3036 +   <dd>Tab Atkins Jr.; Elika J. Etemad; Rossen Atanassov. <a href="http://www.w3.org/TR/2013/WD-css3-grid-layout-20130402/">CSS Grid Layout</a>. 2 April 2013. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2013/WD-css3-grid-layout-20130402/">http://www.w3.org/TR/2013/WD-css3-grid-layout-20130402/</a>
  3.3037 +   <dt id="biblio-css3-transforms"><a class="self-link" href="#biblio-css3-transforms"></a>[CSS3-TRANSFORMS]
  3.3038 +   <dd>Simon Fraser; et al. <a href="http://www.w3.org/TR/2012/WD-css3-transforms-20120911/">CSS Transforms</a>. 11 September 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-css3-transforms-20120911/">http://www.w3.org/TR/2012/WD-css3-transforms-20120911/</a>
  3.3039 +   <dt id="biblio-css3-writing-modes"><a class="self-link" href="#biblio-css3-writing-modes"></a>[CSS3-WRITING-MODES]
  3.3040 +   <dd>Elika J. Etemad; Koji Ishii. <a href="http://www.w3.org/TR/2012/WD-css3-writing-modes-20121115/">CSS Writing Modes Module Level 3</a>. 15 November 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-css3-writing-modes-20121115/">http://www.w3.org/TR/2012/WD-css3-writing-modes-20121115/</a>
  3.3041 +   <dt id="biblio-css3cascade"><a class="self-link" href="#biblio-css3cascade"></a>[CSS3CASCADE]
  3.3042 +   <dd>Håkon Wium Lie; Elika J. Etemad; Tab Atkins Jr.. <a href="http://www.w3.org/TR/2013/CR-css-cascade-3-20131003/">CSS Cascading and Inheritance Level 3</a>. 3 October 2013. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2013/CR-css-cascade-3-20131003/">http://www.w3.org/TR/2013/CR-css-cascade-3-20131003/</a>
  3.3043 +   <dt id="biblio-css3col"><a class="self-link" href="#biblio-css3col"></a>[CSS3COL]
  3.3044 +   <dd>Håkon Wium Lie. <a href="http://www.w3.org/TR/css3-multicol/">CSS3 module: Multi-column layout</a>. 12 April 2011. CR. URL: <a href="http://www.w3.org/TR/css3-multicol/">http://www.w3.org/TR/css3-multicol/</a>
  3.3045 +   <dt id="biblio-select"><a class="self-link" href="#biblio-select"></a>[SELECT]
  3.3046 +   <dd>Tantek Çelik; et al. <a href="http://www.w3.org/TR/2011/REC-css3-selectors-20110929/">Selectors Level 3</a>. 29 September 2011. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2011/REC-css3-selectors-20110929/">http://www.w3.org/TR/2011/REC-css3-selectors-20110929/</a>
  3.3047 +   <dt id="biblio-css3-break"><a class="self-link" href="#biblio-css3-break"></a>[css3-break]
  3.3048 +   <dd>Rossen Atanassov; Elika Etemad. <a href="http://www.w3.org/TR/css3-break/">CSS Fragmentation Module Level 3</a>. 16 January 2014. WD. URL: <a href="http://www.w3.org/TR/css3-break/">http://www.w3.org/TR/css3-break/</a>
  3.3049 +   <dt id="biblio-rfc2119"><a class="self-link" href="#biblio-rfc2119"></a>[rfc2119]
  3.3050 +   <dd>S. Bradner. <a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>. March 1997. Best Current Practice. URL: <a href="https://tools.ietf.org/html/rfc2119">https://tools.ietf.org/html/rfc2119</a>
  3.3051    </dl>
  3.3052 -
  3.3053 -  <p>The specification will remain Candidate Recommendation for at least six
  3.3054 -   months.
  3.3055 -
  3.3056 -  <h2 class=no-num id=acknowledgments> Acknowledgments</h2>
  3.3057 -
  3.3058 -  <p> Thanks especially to the feedback from Rossen Atanassov, Bert Bos,
  3.3059 -   Tantek Çelik, John Daggett, fantasai, Daniel Glazman, Vincent Hardy,
  3.3060 -   Håkon Wium Lie, Peter Linss, Robert O'Callahan, Florian Rivoal, Alan
  3.3061 -   Stearns, Steve Zilles, and all the rest of the <a
  3.3062 -   href="http://lists.w3.org/Archives/Public/www-style/">www-style</a>
  3.3063 -   community.
  3.3064 -
  3.3065 -  <h2 class=no-num id=references> References</h2>
  3.3066 -
  3.3067 -  <h3 class=no-num id=normative-references> Normative references</h3>
  3.3068 -  <!--begin-normative-->
  3.3069 -  <!-- Sorted by label -->
  3.3070 -
  3.3071 -  <dl class=bibliography><!---->
  3.3072 -
  3.3073 -   <dt id=CSS-GRID-1>[CSS-GRID-1]
  3.3074 -
  3.3075 -   <dd>Tab Atkins Jr.; fantasai; Rossen Atanassov. <a
  3.3076 -    href="http://www.w3.org/TR/2014/WD-css-grid-1-20140513/"><cite>CSS Grid
  3.3077 -    Layout Module Level 1.</cite></a> 13 May 2014. W3C Working Draft. (Work
  3.3078 -    in progress.) URL: <a
  3.3079 -    href="http://www.w3.org/TR/2014/WD-css-grid-1-20140513/">http://www.w3.org/TR/2014/WD-css-grid-1-20140513/</a>
  3.3080 -   </dd>
  3.3081 -   <!---->
  3.3082 -
  3.3083 -   <dt id=CSS-WRITING-MODES-3>[CSS-WRITING-MODES-3]
  3.3084 -
  3.3085 -   <dd>fantasai; Koji Ishii. <a
  3.3086 -    href="http://www.w3.org/TR/2014/CR-css-writing-modes-3-20140320/"><cite>CSS
  3.3087 -    Writing Modes Level 3.</cite></a> 20 March 2014. W3C Candidate
  3.3088 -    Recommendation. (Work in progress.) URL: <a
  3.3089 -    href="http://www.w3.org/TR/2014/CR-css-writing-modes-3-20140320/">http://www.w3.org/TR/2014/CR-css-writing-modes-3-20140320/</a>
  3.3090 -   </dd>
  3.3091 -   <!---->
  3.3092 -
  3.3093 -   <dt id=CSS21>[CSS21]
  3.3094 -
  3.3095 -   <dd>Bert Bos; et al. <a
  3.3096 -    href="http://www.w3.org/TR/2011/REC-CSS2-20110607"><cite>Cascading Style
  3.3097 -    Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 7 June
  3.3098 -    2011. W3C Recommendation. URL: <a
  3.3099 -    href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a>
  3.3100 -   </dd>
  3.3101 -   <!---->
  3.3102 -
  3.3103 -   <dt id=CSS3-BREAK>[CSS3-BREAK]
  3.3104 -
  3.3105 -   <dd>Rossen Atanassov; Elika J. Etemad. <a
  3.3106 -    href="http://www.w3.org/TR/2014/WD-css3-break-20140116/"><cite>CSS
  3.3107 -    Fragmentation Module Level 3.</cite></a> 16 January 2014. W3C Working
  3.3108 -    Draft. (Work in progress.) URL: <a
  3.3109 -    href="http://www.w3.org/TR/2014/WD-css3-break-20140116/">http://www.w3.org/TR/2014/WD-css3-break-20140116/</a>
  3.3110 -   </dd>
  3.3111 -   <!---->
  3.3112 -
  3.3113 -   <dt id=CSS3-FLEXBOX>[CSS3-FLEXBOX]
  3.3114 -
  3.3115 -   <dd>Tab Atkins Jr.; fantasai; Rossen Atanassov. <a
  3.3116 -    href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140925/"><cite>CSS
  3.3117 -    Flexible Box Layout Module Level 1.</cite></a> 25 September 2014. W3C
  3.3118 -    Last Call Working Draft. (Work in progress.) URL: <a
  3.3119 -    href="http://www.w3.org/TR/2014/WD-css-flexbox-1-20140925/">http://www.w3.org/TR/2014/WD-css-flexbox-1-20140925/</a>
  3.3120 -   </dd>
  3.3121 -   <!---->
  3.3122 -
  3.3123 -   <dt id=CSS3-TRANSFORMS>[CSS3-TRANSFORMS]
  3.3124 -
  3.3125 -   <dd>Simon Fraser; et al. <a
  3.3126 -    href="http://www.w3.org/TR/2013/WD-css-transforms-1-20131126/"><cite>CSS
  3.3127 -    Transforms Module Level 1.</cite></a> 26 November 2013. W3C Working
  3.3128 -    Draft. (Work in progress.) URL: <a
  3.3129 -    href="http://www.w3.org/TR/2013/WD-css-transforms-1-20131126/">http://www.w3.org/TR/2013/WD-css-transforms-1-20131126/</a>
  3.3130 -   </dd>
  3.3131 -   <!---->
  3.3132 -
  3.3133 -   <dt id=CSS3CASCADE>[CSS3CASCADE]
  3.3134 -
  3.3135 -   <dd>Håkon Wium Lie; fantasai; Tab Atkins Jr. <a
  3.3136 -    href="http://www.w3.org/TR/2013/CR-css-cascade-3-20131003/"><cite>CSS
  3.3137 -    Cascading and Inheritance Level 3.</cite></a> 3 October 2013. W3C
  3.3138 -    Candidate Recommendation. (Work in progress.) URL: <a
  3.3139 -    href="http://www.w3.org/TR/2013/CR-css-cascade-3-20131003/">http://www.w3.org/TR/2013/CR-css-cascade-3-20131003/</a>
  3.3140 -   </dd>
  3.3141 -   <!---->
  3.3142 -
  3.3143 -   <dt id=CSS3COL>[CSS3COL]
  3.3144 -
  3.3145 -   <dd>Håkon Wium Lie. <a
  3.3146 -    href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412"><cite>CSS
  3.3147 -    Multi-column Layout Module.</cite></a> 12 April 2011. W3C Candidate
  3.3148 -    Recommendation. (Work in progress.) URL: <a
  3.3149 -    href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412">http://www.w3.org/TR/2011/CR-css3-multicol-20110412</a>
  3.3150 -   </dd>
  3.3151 -   <!---->
  3.3152 -
  3.3153 -   <dt id=RFC2119>[RFC2119]
  3.3154 -
  3.3155 -   <dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key
  3.3156 -    words for use in RFCs to Indicate Requirement Levels.</cite></a> 2119.
  3.3157 -    RFC. URL: <a
  3.3158 -    href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
  3.3159 -   </dd>
  3.3160 -   <!---->
  3.3161 -
  3.3162 -   <dt id=SELECT>[SELECT]
  3.3163 -
  3.3164 -   <dd>Tantek Çelik; et al. <a
  3.3165 -    href="http://www.w3.org/TR/2011/REC-css3-selectors-20110929/"><cite>Selectors
  3.3166 -    Level 3.</cite></a> 29 September 2011. W3C Recommendation. URL: <a
  3.3167 -    href="http://www.w3.org/TR/2011/REC-css3-selectors-20110929/">http://www.w3.org/TR/2011/REC-css3-selectors-20110929/</a>
  3.3168 -   </dd>
  3.3169 -   <!---->
  3.3170 +  <h3 class="no-num heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
  3.3171 +  <dl>
  3.3172 +   <dt id="biblio-css1"><a class="self-link" href="#biblio-css1"></a>[CSS1]
  3.3173 +   <dd>Håkon Wium Lie; Bert Bos. <a href="http://www.w3.org/TR/CSS1/">Cascading Style Sheets (CSS1) Level 1 Specification</a>. 11 April 2008. REC. URL: <a href="http://www.w3.org/TR/CSS1/">http://www.w3.org/TR/CSS1/</a>
  3.3174 +   <dt id="biblio-css3-regions"><a class="self-link" href="#biblio-css3-regions"></a>[CSS3-REGIONS]
  3.3175 +   <dd>Vincent Hardy; Rossen Atanassov; Alan Stearns. <a href="http://www.w3.org/TR/2013/WD-css3-regions-20130528/">CSS Regions Module Level 1</a>. 28 May 2013. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2013/WD-css3-regions-20130528/">http://www.w3.org/TR/2013/WD-css3-regions-20130528/</a>
  3.3176 +   <dt id="biblio-css3bg"><a class="self-link" href="#biblio-css3bg"></a>[CSS3BG]
  3.3177 +   <dd>Bert Bos; Elika J. Etemad; Brad Kemper. <a href="http://www.w3.org/TR/2012/CR-css3-background-20120724/">CSS Backgrounds and Borders Module Level 3</a>. 24 July 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/CR-css3-background-20120724/">http://www.w3.org/TR/2012/CR-css3-background-20120724/</a>
  3.3178 +   <dt id="biblio-css3box"><a class="self-link" href="#biblio-css3box"></a>[CSS3BOX]
  3.3179 +   <dd>Bert Bos. <a href="http://www.w3.org/TR/2007/WD-css3-box-20070809">CSS basic box model</a>. 9 August 2007. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2007/WD-css3-box-20070809">http://www.w3.org/TR/2007/WD-css3-box-20070809</a>
  3.3180 +   <dt id="biblio-css3gcpm"><a class="self-link" href="#biblio-css3gcpm"></a>[CSS3GCPM]
  3.3181 +   <dd>Håkon Wium Lie. <a href="http://www.w3.org/TR/2011/WD-css3-gcpm-20111129/">CSS Generated Content for Paged Media Module</a>. 29 November 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/WD-css3-gcpm-20111129/">http://www.w3.org/TR/2011/WD-css3-gcpm-20111129/</a>
  3.3182 +   <dt id="biblio-css3text"><a class="self-link" href="#biblio-css3text"></a>[CSS3TEXT]
  3.3183 +   <dd>Elika J. Etemad; Koji Ishii. <a href="http://www.w3.org/TR/2012/WD-css3-text-20121113/">CSS Text Module Level 3</a>. 13 November 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-css3-text-20121113/">http://www.w3.org/TR/2012/WD-css3-text-20121113/</a>
  3.3184 +   <dt id="biblio-css3-marquee"><a class="self-link" href="#biblio-css3-marquee"></a>[css3-marquee]
  3.3185 +   <dd>Bert Bos. <a href="http://www.w3.org/TR/css3-marquee">CSS Marquee Module Level 3</a>. 14 October 2014. NOTE. URL: <a href="http://www.w3.org/TR/css3-marquee">http://www.w3.org/TR/css3-marquee</a>
  3.3186    </dl>
  3.3187 -  <!--end-normative-->
  3.3188 -
  3.3189 -  <h3 class=no-num id=other-references> Other references</h3>
  3.3190 -  <!--begin-informative-->
  3.3191 -  <!-- Sorted by label -->
  3.3192 -
  3.3193 -  <dl class=bibliography><!---->
  3.3194 -
  3.3195 -   <dt id=CSS-REGIONS-1>[CSS-REGIONS-1]
  3.3196 -
  3.3197 -   <dd>Rossen Atanassov; Alan Stearns. <a
  3.3198 -    href="http://www.w3.org/TR/2014/WD-css-regions-1-20141009/"><cite>CSS
  3.3199 -    Regions Module Level 1.</cite></a> 9 October 2014. W3C Working Draft.
  3.3200 -    (Work in progress.) URL: <a
  3.3201 -    href="http://www.w3.org/TR/2014/WD-css-regions-1-20141009/">http://www.w3.org/TR/2014/WD-css-regions-1-20141009/</a>
  3.3202 -   </dd>
  3.3203 -   <!---->
  3.3204 -
  3.3205 -   <dt id=CSS-TEXT-3>[CSS-TEXT-3]
  3.3206 -
  3.3207 -   <dd>Elika J. Etemad; Koji Ishii. <a
  3.3208 -    href="http://www.w3.org/TR/2013/WD-css-text-3-20131010/"><cite>CSS Text
  3.3209 -    Module Level 3.</cite></a> 10 October 2013. W3C Last Call Working Draft.
  3.3210 -    (Work in progress.) URL: <a
  3.3211 -    href="http://www.w3.org/TR/2013/WD-css-text-3-20131010/">http://www.w3.org/TR/2013/WD-css-text-3-20131010/</a>
  3.3212 -   </dd>
  3.3213 -   <!---->
  3.3214 -
  3.3215 -   <dt id=CSS1>[CSS1]
  3.3216 -
  3.3217 -   <dd>Håkon Wium Lie; Bert Bos. <a
  3.3218 -    href="http://www.w3.org/TR/2008/REC-CSS1-20080411"><cite>Cascading Style
  3.3219 -    Sheets (CSS1) Level 1 Specification.</cite></a> 11 April 2008. W3C
  3.3220 -    Recommendation. URL: <a
  3.3221 -    href="http://www.w3.org/TR/2008/REC-CSS1-20080411">http://www.w3.org/TR/2008/REC-CSS1-20080411</a>
  3.3222 -   </dd>
  3.3223 -   <!---->
  3.3224 -
  3.3225 -   <dt id=CSS3-MARQUEE>[CSS3-MARQUEE]
  3.3226 -
  3.3227 -   <dd>Bert Bos. <a
  3.3228 -    href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205"><cite>CSS
  3.3229 -    Marquee Module Level 3.</cite></a> 5 December 2008. W3C Candidate
  3.3230 -    Recommendation. (Work in progress.) URL: <a
  3.3231 -    href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205">http://www.w3.org/TR/2008/CR-css3-marquee-20081205</a>
  3.3232 -   </dd>
  3.3233 -   <!---->
  3.3234 -
  3.3235 -   <dt id=CSS3BG>[CSS3BG]
  3.3236 -
  3.3237 -   <dd>Bert Bos; Elika J. Etemad; Brad Kemper. <a
  3.3238 -    href="http://www.w3.org/TR/2014/CR-css3-background-20140909/"><cite>CSS
  3.3239 -    Backgrounds and Borders Module Level 3.</cite></a> 9 September 2014. W3C
  3.3240 -    Candidate Recommendation. (Work in progress.) URL: <a
  3.3241 -    href="http://www.w3.org/TR/2014/CR-css3-background-20140909/">http://www.w3.org/TR/2014/CR-css3-background-20140909/</a>
  3.3242 -   </dd>
  3.3243 -   <!---->
  3.3244 -
  3.3245 -   <dt id=CSS3BOX>[CSS3BOX]
  3.3246 -
  3.3247 -   <dd>Bert Bos. <a
  3.3248 -    href="http://www.w3.org/TR/2007/WD-css3-box-20070809"><cite>CSS basic box
  3.3249 -    model.</cite></a> 9 August 2007. W3C Working Draft. (Work in progress.)
  3.3250 -    URL: <a
  3.3251 -    href="http://www.w3.org/TR/2007/WD-css3-box-20070809">http://www.w3.org/TR/2007/WD-css3-box-20070809</a>
  3.3252 -   </dd>
  3.3253 -   <!---->
  3.3254 -
  3.3255 -   <dt id=CSS3COLOR>[CSS3COLOR]
  3.3256 -
  3.3257 -   <dd>Tantek Çelik; Chris Lilley; L. David Baron. <a
  3.3258 -    href="http://www.w3.org/TR/2011/REC-css3-color-20110607"><cite>CSS Color
  3.3259 -    Module Level 3.</cite></a> 7 June 2011. W3C Recommendation. URL: <a
  3.3260 -    href="http://www.w3.org/TR/2011/REC-css3-color-20110607">http://www.w3.org/TR/2011/REC-css3-color-20110607</a>
  3.3261 -   </dd>
  3.3262 -   <!---->
  3.3263 -
  3.3264 -   <dt id=CSS3GCPM>[CSS3GCPM]
  3.3265 -
  3.3266 -   <dd>Dave Cramer. <a
  3.3267 -    href="http://www.w3.org/TR/2014/WD-css-gcpm-3-20140513/"><cite>CSS
  3.3268 -    Generated Content for Paged Media Module.</cite></a> 13 May 2014. W3C
  3.3269 -    Working Draft. (Work in progress.) URL: <a
  3.3270 -    href="http://www.w3.org/TR/2014/WD-css-gcpm-3-20140513/">http://www.w3.org/TR/2014/WD-css-gcpm-3-20140513/</a>
  3.3271 -   </dd>
  3.3272 -   <!---->
  3.3273 -  </dl>
  3.3274 -  <!--end-informative-->
  3.3275 -
  3.3276 -  <h2 class=no-num id=index> Index</h2>
  3.3277 -  <!--begin-index-->
  3.3278 -
  3.3279 -  <ul class=indexlist>
  3.3280 -   <li>3d-preserving child, <a href="#d-preserving-child"
  3.3281 -    title="section 2.2."><strong>2.2.</strong></a>
  3.3282 -
  3.3283 -   <li>3d-preserving descendant, <a href="#d-preserving-descendant"
  3.3284 -    title="section 2.2."><strong>2.2.</strong></a>
  3.3285 -
  3.3286 -   <li>authoring tool, <a href="#authoring-tool"
  3.3287 -    title="section 8.4."><strong>8.4.</strong></a>
  3.3288 -
  3.3289 -   <li>auto, <a href="#auto" title="section 3."><strong>3.</strong></a>
  3.3290 -
  3.3291 -   <li>border-box overflow, <a href="#border-box-overflow0"
  3.3292 -    title="section 2.3."><strong>2.3.</strong></a>
  3.3293 -
  3.3294 -   <li>border-box overflow rectangle, <a
  3.3295 -    href="#border-box-overflow-rectangle"
  3.3296 -    title="section 2.3."><strong>2.3.</strong></a>
  3.3297 -
  3.3298 -   <li>border-box overflow region, <a href="#border-box-overflow-region"
  3.3299 -    title="section 2.3."><strong>2.3.</strong></a>
  3.3300 -
  3.3301 -   <li>fragment box, <a href="#fragment-box"
  3.3302 -    title="section 6."><strong>6.</strong></a>
  3.3303 -
  3.3304 -   <li>fragmenting values, <a href="#fragmenting-values"
  3.3305 -    title="section 3."><strong>3.</strong></a>
  3.3306 -
  3.3307 -   <li>fragments, <a href="#fragments"
  3.3308 -    title="section 3."><strong>3.</strong></a>
  3.3309 -
  3.3310 -   <li>hidden, <a href="#hidden" title="section 3."><strong>3.</strong></a>
  3.3311 -
  3.3312 -   <li>ink overflow, <a href="#ink-overflow0"
  3.3313 -    title="section 2.1."><strong>2.1.</strong></a>
  3.3314 -
  3.3315 -   <li>ink overflow rectangle, <a href="#ink-overflow-rectangle"
  3.3316 -    title="section 2.1."><strong>2.1.</strong></a>
  3.3317 -
  3.3318 -   <li>ink overflow region, <a href="#ink-overflow-region"
  3.3319 -    title="section 2.1."><strong>2.1.</strong></a>
  3.3320 -
  3.3321 -   <li>max-lines, <a href="#max-lines0"
  3.3322 -    title="section 6.2."><strong>6.2.</strong></a>
  3.3323 -
  3.3324 -   <li>non-3d-preserving child, <a href="#non-3d-preserving-child"
  3.3325 -    title="section 2.2."><strong>2.2.</strong></a>
  3.3326 -
  3.3327 -   <li>overflow, <a href="#overflow"
  3.3328 -    title="section 2."><strong>2.</strong></a>, <a href="#overflow0"
  3.3329 -    title="section 3."><strong>3.</strong></a>
  3.3330 -
  3.3331 -   <li>overflow-x, <a href="#overflow-x"
  3.3332 -    title="section 3."><strong>3.</strong></a>
  3.3333 -
  3.3334 -   <li>overflow-y, <a href="#overflow-y"
  3.3335 -    title="section 3."><strong>3.</strong></a>
  3.3336 -
  3.3337 -   <li>paged-x, <a href="#paged-x" title="section 3."><strong>3.</strong></a>
  3.3338 -
  3.3339 -   <li>paged-x-controls, <a href="#paged-x-controls"
  3.3340 -    title="section 3."><strong>3.</strong></a>
  3.3341 -
  3.3342 -   <li>paged-y, <a href="#paged-y" title="section 3."><strong>3.</strong></a>
  3.3343 -
  3.3344 -   <li>paged-y-controls, <a href="#paged-y-controls"
  3.3345 -    title="section 3."><strong>3.</strong></a>
  3.3346 -
  3.3347 -   <li>renderer, <a href="#renderer"
  3.3348 -    title="section 8.4."><strong>8.4.</strong></a>
  3.3349 -
  3.3350 -   <li>scroll, <a href="#scroll" title="section 3."><strong>3.</strong></a>
  3.3351 -
  3.3352 -   <li>scrollable overflow, <a href="#scrollable-overflow0"
  3.3353 -    title="section 2.2."><strong>2.2.</strong></a>
  3.3354 -
  3.3355 -   <li>scrollable overflow rectangle, <a
  3.3356 -    href="#scrollable-overflow-rectangle"
  3.3357 -    title="section 2.2."><strong>2.2.</strong></a>
  3.3358 -
  3.3359 -   <li>scrollable overflow region, <a href="#scrollable-overflow-region"
  3.3360 -    title="section 2.2."><strong>2.2.</strong></a>
  3.3361 -
  3.3362 -   <li>scrolling values, <a href="#scrolling-values"
  3.3363 -    title="section 3."><strong>3.</strong></a>
  3.3364 -
  3.3365 -   <li>style sheet
  3.3366 +  <h2 class="no-num heading settled" id="index"><span class="content">Index</span><a class="self-link" href="#index"></a></h2>
  3.3367 +  <ul class="indexlist">
  3.3368 +   <li>3d-preserving child, <a href="#3d_preserving-child">2.2</a>
  3.3369 +   <li>3d-preserving descendant, <a href="#3d_preserving-descendant">2.2</a>
  3.3370 +   <li>auto, <a href="#valdef-overflow-auto">3</a>
  3.3371 +   <li>border-box overflow, <a href="#border_box-overflow">2.3</a>
  3.3372 +   <li>border-box overflow rectangle, <a href="#border_box-overflow-rectangle">2.3</a>
  3.3373 +   <li>border-box overflow region, <a href="#border_box-overflow-region">2.3</a>
  3.3374 +   <li>fragment box, <a href="#fragment-box">6</a>
  3.3375 +   <li>fragmenting values, <a href="#fragmenting-values">3</a>
  3.3376 +   <li>fragments, <a href="#valdef-overflow-fragments">3</a>
  3.3377 +   <li>hidden, <a href="#valdef-overflow-hidden">3</a>
  3.3378 +   <li>ink overflow, <a href="#ink-overflow0">2.1</a>
  3.3379 +   <li>ink overflow rectangle, <a href="#ink-overflow-rectangle">2.1</a>
  3.3380 +   <li>ink overflow region, <a href="#ink-overflow-region">2.1</a>
  3.3381 +   <li>&lt;integer>, <a href="#valdef-max-lines-integer">6.2</a>
  3.3382 +   <li>max-lines, <a href="#propdef-max-lines">6.2</a>
  3.3383 +   <li>non-3d-preserving child, <a href="#non_3d_preserving-child">2.2</a>
  3.3384 +   <li>none, <a href="#valdef-max-lines-none">6.2</a>
  3.3385 +   <li>overflow
  3.3386      <ul>
  3.3387 -     <li>as conformance class, <a href="#style-sheet"
  3.3388 -      title="section 8.4."><strong>8.4.</strong></a>
  3.3389 +     <li>definition of, <a href="#overflow">2</a>
  3.3390 +     <li>(property), <a href="#propdef-overflow">3</a>
  3.3391      </ul>
  3.3392 -
  3.3393 -   <li>visible, <a href="#visible" title="section 3."><strong>3.</strong></a>
  3.3394 +   <li>overflow-x, <a href="#propdef-overflow-x">3</a>
  3.3395 +   <li>overflow-y, <a href="#propdef-overflow-y">3</a>
  3.3396 +   <li>paged-x, <a href="#valdef-overflow-paged-x">3</a>
  3.3397 +   <li>paged-x-controls, <a href="#valdef-overflow-paged-x-controls">3</a>
  3.3398 +   <li>paged-y, <a href="#valdef-overflow-paged-y">3</a>
  3.3399 +   <li>paged-y-controls, <a href="#valdef-overflow-paged-y-controls">3</a>
  3.3400 +   <li>scroll, <a href="#valdef-overflow-scroll">3</a>
  3.3401 +   <li>scrollable overflow, <a href="#scrollable-overflow0">2.2</a>
  3.3402 +   <li>scrollable overflow rectangle, <a href="#scrollable-overflow-rectangle">2.2</a>
  3.3403 +   <li>scrollable overflow region, <a href="#scrollable-overflow-region">2.2</a>
  3.3404 +   <li>scrolling values, <a href="#scrolling-values">3</a>
  3.3405 +   <li>visible, <a href="#valdef-overflow-visible">3</a>
  3.3406    </ul>
  3.3407 -  <!--end-index-->
  3.3408 -
  3.3409 -  <h2 class=no-num id=property-index> Property index</h2>
  3.3410 -  <!--begin-properties-->
  3.3411 -
  3.3412 -  <table class=proptable>
  3.3413 +  <h2 class="no-num heading settled" id="property-index"><span class="content">Property Index</span><a class="self-link" href="#property-index"></a></h2>
  3.3414 +  <table class="proptable data">
  3.3415     <thead>
  3.3416      <tr>
  3.3417 -     <th>Property
  3.3418 -
  3.3419 -     <th>Values
  3.3420 -
  3.3421 -     <th>Initial
  3.3422 -
  3.3423 -     <th>Applies to
  3.3424 -
  3.3425 -     <th>Inh.
  3.3426 -
  3.3427 -     <th>Percentages
  3.3428 -
  3.3429 -     <th>Media
  3.3430 -
  3.3431 +     <th scope="col">Name
  3.3432 +     <th scope="col">Value
  3.3433 +     <th scope="col">Initial
  3.3434 +     <th scope="col">Applies to
  3.3435 +     <th scope="col">Inh.
  3.3436 +     <th scope="col">%ages
  3.3437 +     <th scope="col">Media
  3.3438 +     <th scope="col">Animatable
  3.3439 +     <th scope="col">Canonical order
  3.3440 +     <th scope="col">Computed value
  3.3441     <tbody>
  3.3442      <tr>
  3.3443 -     <th><a class=property href="#max-lines0">max-lines</a>
  3.3444 -
  3.3445 -     <td>none | &lt;integer&gt;
  3.3446 -
  3.3447 +     <th scope="row"><a class="css" data-link-type="property" href="#propdef-overflow-x">overflow-x</a>
  3.3448 +     <td>visible | hidden | scroll | auto | paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
  3.3449 +     <td>visible
  3.3450 +     <td>block containers [CSS21], flex containers [CSS3-FLEXBOX], and grid containers [CSS3-GRID-LAYOUT]
  3.3451 +     <td>no
  3.3452 +     <td>N/A
  3.3453 +     <td>visual
  3.3454 +     <td>no
  3.3455 +     <td>per grammar
  3.3456 +     <td>see below
  3.3457 +    <tr>
  3.3458 +     <th scope="row"><a class="css" data-link-type="property" href="#propdef-overflow-y">overflow-y</a>
  3.3459 +     <td>visible | hidden | scroll | auto | paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
  3.3460 +     <td>visible
  3.3461 +     <td>block containers [CSS21], flex containers [CSS3-FLEXBOX], and grid containers [CSS3-GRID-LAYOUT]
  3.3462 +     <td>no
  3.3463 +     <td>N/A
  3.3464 +     <td>visual
  3.3465 +     <td>no
  3.3466 +     <td>per grammar
  3.3467 +     <td>see below
  3.3468 +    <tr>
  3.3469 +     <th scope="row"><a class="css" data-link-type="property" href="#propdef-overflow">overflow</a>
  3.3470 +     <td>visible | hidden | scroll | auto | paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
  3.3471 +     <td>see individual properties
  3.3472 +     <td>block containers [CSS21], flex containers [CSS3-FLEXBOX], and grid containers [CSS3-GRID-LAYOUT]
  3.3473 +     <td>no
  3.3474 +     <td>N/A
  3.3475 +     <td>visual
  3.3476 +     <td>no
  3.3477 +     <td>per grammar
  3.3478 +     <td>see individual properties
  3.3479 +    <tr>
  3.3480 +     <th scope="row"><a class="css" data-link-type="property" href="#propdef-max-lines">max-lines</a>
  3.3481 +     <td>none | &lt;integer>
  3.3482       <td>none
  3.3483 -
  3.3484       <td>fragment boxes
  3.3485 -
  3.3486       <td>no
  3.3487 -
  3.3488       <td>N/A
  3.3489 -
  3.3490       <td>visual
  3.3491 -
  3.3492 -    <tr>
  3.3493 -     <th><a class=property href="#overflow0">overflow</a>
  3.3494 -
  3.3495 -     <td>visible | hidden | scroll | auto | paged-x | paged-y |
  3.3496 -      paged-x-controls | paged-y-controls | fragments
  3.3497 -
  3.3498 -     <td>see individual properties
  3.3499 -
  3.3500 -     <td>block containers [CSS21], flex containers [CSS3-FLEXBOX], and grid
  3.3501 -      containers [CSS-GRID-1]
  3.3502 -
  3.3503 -     <td>no
  3.3504 -
  3.3505 -     <td>N/A
  3.3506 -
  3.3507 -     <td>visual
  3.3508 -
  3.3509 -    <tr>
  3.3510 -     <th><a class=property href="#overflow-x">overflow-x</a>
  3.3511 -
  3.3512 -     <td>visible | hidden | scroll | auto | paged-x | paged-y |
  3.3513 -      paged-x-controls | paged-y-controls | fragments
  3.3514 -
  3.3515 -     <td>visible
  3.3516 -
  3.3517 -     <td>block containers [CSS21], flex containers [CSS3-FLEXBOX], and grid
  3.3518 -      containers [CSS-GRID-1]
  3.3519 -
  3.3520 -     <td>no
  3.3521 -
  3.3522 -     <td>N/A
  3.3523 -
  3.3524 -     <td>visual
  3.3525 -
  3.3526 -    <tr>
  3.3527 -     <th><a class=property href="#overflow-y">overflow-y</a>
  3.3528 -
  3.3529 -     <td>visible | hidden | scroll | auto | paged-x | paged-y |
  3.3530 -      paged-x-controls | paged-y-controls | fragments
  3.3531 -
  3.3532 -     <td>visible
  3.3533 -
  3.3534 -     <td>block containers [CSS21], flex containers [CSS3-FLEXBOX], and grid
  3.3535 -      containers [CSS-GRID-1]
  3.3536 -
  3.3537 -     <td>no
  3.3538 -
  3.3539 -     <td>N/A
  3.3540 -
  3.3541 -     <td>visual
  3.3542 +     <td>as integer
  3.3543 +     <td>per grammar
  3.3544 +     <td>specified value
  3.3545    </table>
  3.3546 -  <!--end-properties-->
  3.3547 -</html>
  3.3548 -<!-- Keep this comment at the end of the file
  3.3549 -Local variables:
  3.3550 -mode: sgml
  3.3551 -sgml-declaration:"~/SGML/HTML4.decl"
  3.3552 -sgml-default-doctype-name:"html"
  3.3553 -sgml-minimize-attributes:t
  3.3554 -sgml-nofill-elements:("pre" "style" "br")
  3.3555 -sgml-live-element-indicator:t
  3.3556 -sgml-omittag:nil
  3.3557 -sgml-shorttag:nil
  3.3558 -sgml-namecase-general:t
  3.3559 -sgml-general-insert-case:lower
  3.3560 -sgml-always-quote-attributes:t
  3.3561 -sgml-indent-step:nil
  3.3562 -sgml-indent-data:t
  3.3563 -sgml-parent-document:nil
  3.3564 -sgml-exposed-tags:nil
  3.3565 -sgml-local-catalogs:nil
  3.3566 -sgml-local-ecat-files:nil
  3.3567 -End:
  3.3568 --->
  3.3569 +  <h2 class="no-num heading settled" id="issues-index"><span class="content">Issues Index</span><a class="self-link" href="#issues-index"></a></h2>
  3.3570 +  <div style="counter-reset:issue">
  3.3571 +   <div class="issue">undefined term?<a href="#issue-18c1c008"> ↵ </a></div>
  3.3572 +   <div class="issue">
  3.3573 +		Should we try to define it at all and just leave pieces undefined?
  3.3574 +	<a href="#issue-1baddb1e"> ↵ </a></div>
  3.3575 +   <div class="issue">
  3.3576 +		The following definition should be rewritten to use
  3.3577 +		the concept of <a href="http://dev.w3.org/csswg/css-transforms/#3d-rendering-context">3D rendering context</a> <a data-link-type="biblio" href="#biblio-css3-transforms">[CSS3-TRANSFORMS]</a>
  3.3578 +		and related terms,
  3.3579 +		particularly once those concepts stabilize following changes
  3.3580 +		proposed in the CSS WG meeting on the morning of 2014-01-28.
  3.3581 +	<a href="#issue-36f1a23e"> ↵ </a></div>
  3.3582 +   <div class="issue">which belong in <a data-link-type="biblio" href="#biblio-css3-transforms">[CSS3-TRANSFORMS]</a><a href="#issue-172bf444"> ↵ </a></div>
  3.3583 +   <div class="issue">undefined concept!<a href="#issue-1b139c15"> ↵ </a></div>
  3.3584 +   <div class="issue">undefined term!<a href="#issue-2d1dc4f9"> ↵ </a></div>
  3.3585 +   <div class="issue">MORE HERE!<a href="#issue-75780f3f"> ↵ </a></div>
  3.3586 +   <div class="issue">
  3.3587 +		I wrote this definition off the top of my head,
  3.3588 +		so it can’t possibly be right.
  3.3589 +		It’s missing tons of pieces!
  3.3590 +	<a href="#issue-e889eac0"> ↵ </a></div>
  3.3591 +   <div class="issue">
  3.3592 +		The handling of preserve-3d subtrees here is probably wrong;
  3.3593 +		the elements should probably count
  3.3594 +		only towards the overflow of the element that flattens them.
  3.3595 +	<a href="#issue-521d48c7"> ↵ </a></div>
  3.3596 +   <div class="issue">
  3.3597 +		This concept has been proposed for some uses, such as for
  3.3598 +		determining what the <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-ui-3/#propdef-outline">outline</a> property goes around, and
  3.3599 +		as the basis of a coordinate system for specifying clips and masks,
  3.3600 +		but it’s not clear if it’s needed.
  3.3601 +	<a href="#issue-3930f393"> ↵ </a></div>
  3.3602 +   <div class="issue">
  3.3603 +		If needed, define more formally, as for scrollable overflow above.
  3.3604 +		(Maybe even share the definitions in an appropriate way!)
  3.3605 +	<a href="#issue-42ea3c29"> ↵ </a></div>
  3.3606 +   <div class="issue">
  3.3607 +		Are all 4 of the <span class="css">paged-*</span> values really needed?
  3.3608 +	<a href="#issue-45d3d9aa"> ↵ </a></div>
  3.3609 +   <div class="issue">Is this the right behavior?<a href="#issue-ef127061"> ↵ </a></div>
  3.3610 +   <div class="issue">Give example.<a href="#issue-78cdbe9b"> ↵ </a></div>
  3.3611 +   <div class="issue">
  3.3612 +		<a data-link-type="biblio" href="#biblio-css3-marquee">[CSS3-MARQUEE]</a> describes an <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> property,
  3.3613 +		but it has not picked up implementation experience
  3.3614 +		that the working group is aware of.
  3.3615 +		Should this document treat <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> as a defunct proposal,
  3.3616 +		or should this document describe the <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> property
  3.3617 +		and attempt to revive it,
  3.3618 +		despite that implementations have implemented
  3.3619 +		<a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> and <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> instead?
  3.3620 +	<a href="#issue-2c53acbd"> ↵ </a></div>
  3.3621 +   <div class="issue">
  3.3622 +		There are <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussions</a>
  3.3623 +		about how overflow, overflow-style, overflow-x and overflow-y
  3.3624 +		should work and interact with each other.
  3.3625 +		Until consensus on this topic is reached,
  3.3626 +		it is not completely clear which of these
  3.3627 +		should be used for
  3.3628 +		paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
  3.3629 +	<a href="#issue-a8b88d7e"> ↵ </a></div>
  3.3630 +   <div class="issue">
  3.3631 +		Move material from <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a> and <a data-link-type="biblio" href="#biblio-css3box">[CSS3BOX]</a> here.
  3.3632 +	<a href="#issue-726ed205"> ↵ </a></div>
  3.3633 +   <div class="issue">
  3.3634 +		Explain which directions allow scrolling and which don’t,
  3.3635 +		as a function of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-writing-modes-3/#propdef-direction">direction</a>
  3.3636 +		(including propagation of <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-writing-modes-3/#propdef-direction">direction</a> to the ICB).
  3.3637 +	<a href="#issue-c318b1c1"> ↵ </a></div>
  3.3638 +   <div class="issue">overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> has?)<a href="#issue-03349ce5"> ↵ </a></div>
  3.3639 +   <div class="issue">Ability to display N pages at once
  3.3640 +rather than just one page at once?<a href="#issue-22961e25"> ↵ </a></div>
  3.3641 +   <div class="issue">
  3.3642 +		The current implementation of paginated overflow uses
  3.3643 +		the <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>/<a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a>/<a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a> properties
  3.3644 +		rather than the <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a> property as proposed
  3.3645 +		in the <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> draft
  3.3646 +		(which also matches the <a data-link-type="biblio" href="#biblio-css3-marquee">[CSS3-MARQUEE]</a> proposal).
  3.3647 +		We should probably switch away from <a class="property" data-link-type="propdesc" href="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style">overflow-style</a>,
  3.3648 +		but that’s not 100% clear.
  3.3649 +	<a href="#issue-7328bc11"> ↵ </a></div>
  3.3650 +   <div class="issue">Or is it as though it’s a next sibling of
  3.3651 +		the element?  Need to figure out exactly how this interacts with
  3.3652 +		other box-level fixup.<a href="#issue-74f423ed"> ↵ </a></div>
  3.3653 +   <div class="issue">though it defines <i>multi-column element</i><a href="#issue-928903ce"> ↵ </a></div>
  3.3654 +   <div class="issue">Should a forced break that breaks to
  3.3655 +		an outer fragmentation context cause a new fragment of a single
  3.3656 +		fragment box or a new fragment box?<a href="#issue-060b1de8"> ↵ </a></div>
  3.3657 +   <div class="issue">Should we find a term other than
  3.3658 +		<a data-link-type="dfn" href="#fragment-box">fragment box</a> here to make this a little less confusing?<a href="#issue-5b4b087c"> ↵ </a></div>
  3.3659 +   <div class="issue">
  3.3660 +		What if we want to be able to style the pieces of an element
  3.3661 +		split within another type of fragmentation context?
  3.3662 +		These rules prevent ever using <span class="css">::nth-fragment()</span> for that,
  3.3663 +		despite that the name seems the most logical name for such a feature.
  3.3664 +	<a href="#issue-89a60b9c"> ↵ </a></div>
  3.3665 +   <div class="issue">
  3.3666 +		We should specify that <a class="css" data-link-type="propdesc" href="#propdef-overflow">overflow: fragments</a> does not apply
  3.3667 +		to at least some table parts,
  3.3668 +		and perhaps other elements as well.
  3.3669 +		We need to determine exactly which ones.
  3.3670 +	<a href="#issue-f590932f"> ↵ </a></div>
  3.3671 +   <div class="issue">
  3.3672 +		This specification needs to say which type of
  3.3673 +		fragmentation context is created
  3.3674 +		so that it’s clear which values of the <a class="property" data-link-type="propdesc">break-*</a> properties
  3.3675 +		cause breaks within this context.
  3.3676 +		We probably want <span class="css">break-*: region</span> to apply.
  3.3677 +	<a href="#issue-54f95309"> ↵ </a></div>
  3.3678 +   <div class="issue">
  3.3679 +		This specification needs a processing model
  3.3680 +		that will apply in cases where the layout containing the
  3.3681 +		fragments has characteristics that use the intrinsic size of the fragments
  3.3682 +		to change the amount of space available for them,
  3.3683 +		such as <a data-link-type="biblio" href="#biblio-css3-grid-layout">[CSS3-GRID-LAYOUT]</a>.
  3.3684 +		There has already been some work on such a processing model
  3.3685 +		in <a data-link-type="biblio" href="#biblio-css3-regions">[CSS3-REGIONS]</a>,
  3.3686 +		and the work done on a model there,
  3.3687 +		and the editors of that specification,
  3.3688 +		should inform what happens in this specification.
  3.3689 +	<a href="#issue-e784096c"> ↵ </a></div>
  3.3690 +   <div class="issue">
  3.3691 +		Depending on future discussions,
  3.3692 +		this <span class="css">::nth-fragment(an+b)</span> syntax
  3.3693 +		may be replaced with
  3.3694 +		the new <span class="css">::fragment:nth(an+b)</span> syntax.
  3.3695 +	<a href="#issue-4cfde272"> ↵ </a></div>
  3.3696 +   <div class="issue">
  3.3697 +		Should this apply to fragment overflow only,
  3.3698 +		or also to paginated overflow?
  3.3699 +		(If it applies,
  3.3700 +		then stricter property restrictions would be needed
  3.3701 +		for paginated overflow.)
  3.3702 +	<a href="#issue-27c56696"> ↵ </a></div>
  3.3703 +   <div class="issue">Does this need to be specified in
  3.3704 +		the cascading module as well?<a href="#issue-8f881f96"> ↵ </a></div>
  3.3705 +   <div class="issue">Need to reword this to refer to the
  3.3706 +		appropriate choice of <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> or <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>,
  3.3707 +		and then point to rule about the handling of the other one
  3.3708 +		of <a class="property" data-link-type="propdesc" href="#propdef-overflow-x">overflow-x</a> or <a class="property" data-link-type="propdesc" href="#propdef-overflow-y">overflow-y</a>.<a href="#issue-1c902202"> ↵ </a></div>
  3.3709 +   <div class="issue">Need to specify exactly how this works,
  3.3710 +		but it depends on
  3.3711 +		having <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-inside">display-inside</a> and <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-display-3/#propdef-display-outside">display-outside</a> specified.<a href="#issue-d98e732d"> ↵ </a></div>
  3.3712 +   <div class="issue">
  3.3713 +		This inheritance rule allows specifying styles indirectly
  3.3714 +		(by using explicit <a class="css" data-link-type="maybe" href="http://dev.w3.org/csswg/css-cascade-3/#valuedef-inherit">inherit</a> or using default inheritance
  3.3715 +		on properties that don’t apply to <span class="css">:first-letter</span>)
  3.3716 +		that can’t be specified directly
  3.3717 +		(based on the rules in the next section).
  3.3718 +		This is a problem.
  3.3719 +		The restrictions that apply to styling inside fragments
  3.3720 +		should also apply to inheritance from fragments.
  3.3721 +	<a href="#issue-5862943f"> ↵ </a></div>
  3.3722 +   <div class="issue">
  3.3723 +		Should this apply to fragment overflow only,
  3.3724 +		or also to paginated overflow,
  3.3725 +		or even to pagination across pages?
  3.3726 +	<a href="#issue-b1e468e3"> ↵ </a></div>
  3.3727 +   <div class="issue">
  3.3728 +				If there are multiple boundaries between this line
  3.3729 +				and the previous, where exactly (in terms of element
  3.3730 +				boundaries) is the break forced?
  3.3731 +			<a href="#issue-9488ec29"> ↵ </a></div>
  3.3732 +   <div class="issue">Should this apply to fragment overflow only, or also
  3.3733 +to pagination?<a href="#issue-1527f8dd"> ↵ </a></div>
  3.3734 +   <div class="issue">
  3.3735 +		This specification should define useful behavior
  3.3736 +		for all values of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a>
  3.3737 +		in static media (such as print).
  3.3738 +		Current implementation behavior is quite poor and
  3.3739 +		produces unexpected results when authors have not considered
  3.3740 +		what will happen when
  3.3741 +		the content they produce for interactive media
  3.3742 +		is printed.
  3.3743 +	<a href="#issue-5ad703cc"> ↵ </a></div>
  3.3744 +  </div></body>
  3.3745 +</html>
  3.3746 \ No newline at end of file