Overview.bs

<pre class='metadata'>
Title: CSS Text Module Level 3
Shortname: css-text
Level: 3
Status: ED
Work Status: Testing
Group: csswg
ED: https://drafts.csswg.org/css-text-3/
TR: https://www.w3.org/TR/css-text-3/
Previous version: https://www.w3.org/TR/2021/CRD-css-text-3-20210422/
Test Suite: http://test.csswg.org/suites/css3-text/nightly-unstable/
!Test Coverage Analysis: <a href="https://drafts.csswg.org/css-text-3/test-coverage">https://drafts.csswg.org/css-text-3/test-coverage</a>
Implementation Report: https://test.csswg.org/harness/results/css-text-3_dev/grouped/
Editor: Elika J. Etemad / fantasai, Invited Expert, http://fantasai.inkedblade.net/contact, w3cid 35400
Editor: Koji Ishii, Invited Expert, kojiishi@gluesoft.co.jp, w3cid 45369
Editor: Florian Rivoal, Invited Expert, https://florian.rivoal.net, w3cid 43241
Abstract: This CSS module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, and text transformation.
At Risk: the ''full-width'' value of 'text-transform'
At Risk: the ''full-size-kana'' value of 'text-transform'
At Risk: the &lt;length> values of the 'tab-size' property
At Risk: the 'text-justify' property
At Risk: the 'hanging-punctuation' property
At Risk: Writing-system specific adjustments to line-breaking
At Risk: Trimming trailing Ogham space marks
Ignored Vars: letter-spacing
Status Text: This publication fully addresses the issues raised since the <a href="https://www.w3.org/TR/2013/WD-css-text-3-20131010/">October 2013 Last Call Working Draft</a>, which are documented in the <a href="https://drafts.csswg.org/css-text-3/issues-lc-2013">disposition of comments</a>.
WPT Path Prefix: /css/css-text/
</pre>
<pre class=link-defaults>
spec:css-display-3; type:property; text:display
spec:css-fonts-4; type:property; text:font-feature-settings
</pre>

<style type="text/css">
	img { vertical-align: middle; }
	span[lang] {
		font-size: 125%;
		line-height: 1;
		vertical-align: middle;
	}

	/* Bidi & spaces example */
	.egbidiwsaA,.egbidiwsbB,.egbidiwsaB,.egbidiwsbC {
		white-space: pre;
		font-size: 80%;
		font-family: monospace;
		vertical-align: 2px;
		margin: 1px;
	}
	.egbidiwsaA {
		background: lime;
		padding: 2px;
	}
	.egbidiwsbB { border: 2px solid blue; }
	.egbidiwsaB {
		background: yellow;
		border: 2px dotted white;
	}
	.egbidiwsbC { border:2px dotted red; }

	.hyphens-ex {
		border: thin solid black;
		display: inline-block;
		padding: 4pt;
	}

	/* Start Letter-spacing Tutorial */
	.ls-ex {
		font-size: 200%;
		margin-left: 1em;
		margin-right: 1em;
	}
	.ls-fixed-width {
		width: 10em;
	}
	.color-box { background: rgb(224, 203, 82); }
	.bad { color: red; }
	.good { color: green; }
	/* End Letter-spacing Tutorial */

	.char { border: 1px dotted gray; }
	.quarter { font-size: 25%; }
	tt[lang="ja"] { font-family: "MS Gothic", "Osaka", monospace; }
	div.figure table {
		margin: auto;
	}
	.feedback {
		background: #FFEECC;
		border-color: orange;
	}
	.feedback:before {
		content: "Info Needed";
		color: #FF8800;
	}
	.data .no { color: red; }
	.data .ok { color: green; }
	.data th em {
		display: block;
		font-size: smaller;
		font-weight: normal;
		font-style: italic;
	}
	.no-quote.no-quote::before,
	.no-quote.no-quote::after {
		content: none;
	}
</style>

<h2 id="intro">
Introduction</h2>

	<wpt title="
		The test coverage information in this specification
		covers <a href='https://github.com/web-platform-tests/wpt/tree/master/css/css-text/'>wpt/css/css-text/</a> and subdirectories,
		as well as those tests in <a href='https://github.com/web-platform-tests/wpt/tree/master/css/CSS2/'>wpt/css/CSS2/</a> and subdirectories
		that relate to this specification.

		Missing tests:
		* Throughout the spec, tests for <a href=https://github.com/w3c/csswg-drafts/issues/5303>distinguishing between applying to inlines and applying to text</a> should be added."></wpt>

	This module describes the typesetting controls of CSS;
	that is, the features of CSS that control the translation of
	source text to formatted, line-wrapped text.
	Various CSS properties provide control over
	[[#transforming|case transformation]],
	[[#white-space-processing|white space collapsing]],
	[[#white-space-property|text wrapping]],
	[[#line-breaking|line breaking rules]]
	and [[#hyphenation|hyphenation]],
	[[#justification|alignment and justification]],
	[[#spacing|spacing]],
	and [[#edge-effects|indentation]].

	<div class="note">
		Note: Font selection is covered in the <a href="https://www.w3.org/TR/css-fonts-3/"><cite>CSS Fonts Module</cite></a>.
		[[CSS-FONTS-3]]

		<span id="decoration"></span>
		<span id="text-decoration"></span>
		<span id="line-decoration"></span>
		<span id="text-decoration-line"></span>
		<span id="text-decoration-color"></span>
		<span id="text-decoration-style"></span>
		<span id="text-decoration-skip"></span>
		<span id="text-underline-position"></span>
		<span id="emphasis-marks"></span>
		<span id="text-emphasis-style"></span>
		<span id="text-emphasis-color"></span>
		<span id="text-emphasis"></span>
		<span id="text-emphasis-position"></span>
		<span id="text-shadow"></span>
		Features for decorating text,
		such as [[css-text-decor-3#line-decoration|underlines]],
		[[css-text-decor-3#emphasis-marks|emphasis marks]],
		and [[css-text-decor-3#text-shadow-property|shadows]],
		(previously part of this module)
		are covered in the
		<a href="https://www.w3.org/TR/css-text-decor-3/"><cite>CSS Text Decoration Module</cite></a>.
		[[CSS-TEXT-DECOR-3]]

		[[css-writing-modes-4#text-direction|Bidirectional]] and
		[[css-writing-modes-4#vertical-intro|vertical]] text
		are addressed in the
		<a href="https://www.w3.org/TR/css-writing-modes-4/"><cite>CSS Writing Modes Module</cite></a>.
		[[CSS-WRITING-MODES-4]].
	</div>

	Further information about the typesetting requirements
	of various languages and writing systems around the world
	can be found in the <a href="https://www.w3.org/International/core/">Internationalization Working Group</a>’s
	<a href="https://www.w3.org/TR/typography/"><cite>Language Enablement Index</cite></a>.
	[[TYPOGRAPHY]]

	<wpt title="
		The following tests are crash tests
		that relate to general usage
		of the features described in this specification
		but are not tied to any particular normative statement.">
	removing-collapsible-crash.html
	removing-collapsible-spaces-before-float-crash.html
	crashtests/line-break-float-crash.html
	crashtests/trailing-space-with-cr-crash.html
	ellisize-rtl-text-crash.html
	altering-dom-crash.html
	whitespace-followed-by-cham-symbol-crash.html
	white-space/append-whitespace-only-node-crash-001.html
	crashtests/rendering-rtl-bidi-override-crash.html
	crashtests/rendering-table-caption-with-list-item-and-svg-crash.html
	crashtests/rendering-table-caption-with-negative-margins-crash.html
	</wpt>

<h3 id="placement">
Module Interactions</h3>

	<wpt title="Tests not needed for this section."></wpt>

	This module, together with the <cite><a href="https://www.w3.org/TR/css-text-decor-3/">CSS Text Decoration Module</a></cite>,
	replaces and extends the text-level features defined in
	<a href="https://www.w3.org/TR/CSS2/text.html"><cite>Cascading Style Sheets Level 2</cite> chapter 16</a>.
	[[CSS-TEXT-DECOR-3]]
	[[!CSS2]]

	In addition to the terms defined below,
	other terminology and concepts used in this specification are defined
	in <a href="https://www.w3.org/TR/CSS2/"><cite>Cascading Style Sheets Level 2</cite></a>
	and the <a href="https://www.w3.org/TR/css-writing-modes-4/"><cite>CSS Writing Modes Module</cite></a>.
	[[!CSS2]] and [[!CSS-WRITING-MODES-4]].

<h3 id="values">
Value Definitions</h3>

	<wpt title="
		Tests not really needed for this section;
		could possibly test that css-wide keywords apply to every property."></wpt>

	This specification follows the [[CSS2/about#property-defs|CSS property definition conventions]] from [[!CSS2]]
	using the [[css-values-3#value-defs|value definition syntax]] from [[!CSS-VALUES-3]].
	Value types not defined in this specification are defined in CSS Values &amp; Units [[!CSS-VALUES-3]].
	Combination with other CSS modules may expand the definitions of these value types.

	In addition to the property-specific values listed in their definitions,
	all properties defined in this specification
	also accept the [=CSS-wide keywords=] as their property value.
	For readability they have not been repeated explicitly.

<h3 id="languages">
Languages and Typesetting</h3>

	<wpt title="
		Tests not needed for this section:
		these are definitions,
		they get tested through their application,
		not by themselves."></wpt>

	<p class="advisement">
	<strong>Authors should accurately language-tag their content
	for the best typographic behavior.</strong>

	Many typographic effects vary by linguistic context.
	Language and writing system conventions can affect
	line breaking, hyphenation, justification, glyph selection,
	and many other typographic effects.
	<strong>In CSS, language-specific typographic tailorings
	are only applied when the [=content language=] is known (declared).</strong>
	Therefore,
	higher quality typography requires authors to communicate to the UA
	the correct linguistic context of the text in the document.

	The <dfn export>content language</dfn> of an element is the (human) language
	the element is declared to be in, according to the rules of the
	[=document language=].
	Note that it is possible for the [=content language=] of an element
	to be unknown--
	e.g. untagged content,
	or content in a [=document language=] that does not have a language-tagging facility,
	is considered to have an unknown [=content language=].

	Note: Authors can declare the [=content language=]
	using the global <code>lang</code> attribute in HTML
	or the universal <code>xml:lang</code> attribute in XML.
	See the <a spec=html lt=language>rules for determining the content language of an HTML element</a>
	in <cite>HTML</cite>,
	and the [[XML#sec-lang-tag|rules for determining the content language of an XML element]] in <cite>XML 1.0</cite>.
	[[HTML]]
	[[XML10]]

	The [=content language=] an element is declared to be in
	also identifies the specific written form of that language used in that element,
	known as the <dfn export local-lt="writing system">content writing system</dfn>.
	Depending on the [=document language=]’s facilities for identifying the [=content language=],
	this information can be explicit or implied.
	See the normative [[#script-tagging]].

	Note: Some languages have more than one writing system tradition;
	in other cases a language can be transliterated into a foreign writing system.
	Authors should [[#script-tagging|subtag]] such cases
	so that the UA can adapt appropriately.

	<div class=example>
		For example, Korean (<code>ko</code>) can be written in
		Hangul (<code>-Hang</code>),
		Hanja (<code>-Hani</code>),
		or a combination (<code>-Kore</code>).
		Historical documents written solely in Hanja
		do not use word spaces and
		are formatted more like modern Chinese than modern Korean.
		In other words, for typographic purposes <code>ko-Hani</code>
		behaves more like <code>zh-Hant</code>
		than <code>ko</code> (<code>ko-Kore</code>).

		As another example Japanese (<code>ja</code>) is typically written
		in a combination (<code>-Japn</code>) of Hiragana (<code>-Hira</code>),
		Katakana (<code>-Kana</code>), and Kanji (<code>-Hani</code>).
		However, it can also be ”romanized” into Latin (<code>-Latn</code>)
		for special purposes like language-learning textbooks,
		in which case it should be formatted more like English than Japanese.

		As a third example contemporary Mongolian is written in two scripts:
		Cyrillic (<code>-Cyrl</code>, officially used in Mongolia)
		and Mongolian (<code>-Mong</code>, more common in Inner Mongolia, part of China).
		These have very different formatting requirements,
		with Cyrillic behaving similar to Latin and Greek,
		and Mongolian deriving from both Arabic and Chinese writing conventions.
	</div>

<h3 id="characters">
Characters and Letters</h3>

	<wpt title="
		For the most part, tests not really needed for this section:
		these are definitions,
		they get tested through their applications,
		by themselves.
		The few testable assertions that are made have coverage.

		Possible additions:
		* turning the content of example 1 into tests (first, check that it’s not already done)."></wpt>

	The basic unit of typesetting is the <dfn export>character</dfn>.
	However, because writing systems are not always as simple as the basic English alphabet,
	what a [=character=] actually is depends on the context in which the term is used.
	For example, in Hangul (the Korean writing system),
	each square representation of a syllable
	(e.g. <span lang=ko-hang title="Hangul syllable HAN">한</span>=<span lang=ko-Latn>Han</span>)
	can be considered a <a>character</a>.
	However, the square symbol is really composed of multiple letters each representing a phoneme
	(e.g. <span lang=ko-hang title="Hangul letter HIEUH">ㅎ</span>=<span lang=ko-Latn>h</span>,
	<span lang=ko-hang title="Hangul letter HIEUH">ㅏ</span>=<span lang=ko-Latn>a</span>,
	<span lang=ko-hang title="Hangul letter HIEUH">ㄴ</span>=<span lang=ko-Latn>n</span>)
	and these also could each be considered a <a>character</a>.

	A basic unit of computer text encoding, for any given encoding,
	is also called a [=character=],
	and depending on the encoding,
	a single encoding [=character=] might correspond
	to the entire pre-composed syllabic [=character=] (e.g. <span lang=ko-hang title="Hangul syllable HAN">한</span>),
	to the individual phonemic [=character=] (e.g. <span lang=ko-hang title="Hangul letter HIEUH">ㅎ</span>),
	or to smaller units such as
	a base letterform (e.g. <span lang=ko-hang title="Hangul letter IEUNG">ㅇ</span>)
	and any combining marks that vary it (e.g. extra strokes that represent aspiration).

	In turn, a single encoding [=character=] can be represented in the data stream as one or more bytes;
	and in programming environments one byte is sometimes also called a [=character=].

	Therefore the term [=character=] is fairly ambiguous where technical precision is required.

	For text layout, we will refer to the <dfn export lt="typographic character unit|typographic character">typographic character unit</dfn>
	as the basic unit of text.
	Even within the realm of text layout,
	the relevant [=character=] unit depends on the operation.
	For example, line-breaking and letter-spacing will segment
	a sequence of Thai characters that include U+0E33 &nbsp;ำ THAI CHARACTER SARA AM differently;
	or the behavior of a conjunct consonant in a script such as Devanagari
	may depend on the font in use.
	So the [=typographic character=] represents a unit of the writing system--
	such as a Latin alphabetic letter (including its diacritics),
	Hangul syllable,
	Chinese ideographic character,
	Myanmar syllable cluster--
	that is indivisible with respect to a particular typographic operation
	(line-breaking, first-letter effects, tracking, justification, vertical arrangement, etc.).

	<wpt>
	word-break/word-break-break-all-007.html
	word-break/word-break-break-all-008.html
	</wpt>

	<a href="http://www.unicode.org/reports/tr29/"><cite>Unicode Standard Annex #29: Text Segmentation</cite></a>
	defines a unit called the <dfn>grapheme cluster</dfn>
	which approximates the [=typographic character=].
	[[!UAX29]]
	A UA must use the <em>extended grapheme cluster</em>
	(not <em>legacy grapheme cluster</em>), as defined in <cite>UAX29</cite>,
	as the basis for its [=typographic character unit=].
	However, the UA should tailor the definitions
	as required by typographic tradition
	since the default rules are not always appropriate or ideal--
	and is expected to tailor them differently
	depending on the operation as needed.

	<wpt>
	line-breaking/line-breaking-013.html
	line-breaking/line-breaking-014.html
	</wpt>

	Note: The rules for such tailorings are out of scope for CSS.

	<div class="example">
		The following are some examples of [=typographic character unit=] tailorings
		required by standard typesetting practice:

		<ul>
			<li>
				In some scripts such as Myanmar or Devanagari,
				the [=typographic character unit=] for both justification and line-breaking
				is an entire syllable,
				which can include more than one Unicode [=grapheme cluster=].
				[[!UAX29]]

			<li>
				In other scripts such as Thai or Lao,
				even though for line-breaking the [=typographic character=]
				matches Unicode’s default [=grapheme clusters=],
				for letter-spacing the relevant unit
				is <em>less</em> than a Unicode [=grapheme cluster=],
				and may require decomposition or other substitutions
				before spacing can be inserted.
				[[!UAX29]]

				For instance,
				to properly letter-space the Thai word คำ (U+0E04 + U+0E33),
				the U+0E33 needs to be decomposed into U+0E4D + U+0E32,
				and then the extra letter-space inserted before the U+0E32: คํ า.

				A slightly more complex example is น้ำ (U+0E19 + U+0E49 + U+0E33).
				In this case, normal Thai shaping will first decompose the U+0E33 into U+0E4D + U+0E32
				and then swap the U+0E4D with the U+0E49, giving U+0E19 + U+0E4D + U+0E49 + U+0E32.
				As before the extra letter-space is then inserted before the U+0E32: นํ้ า.

			<li>
				Vertical typesetting can also require tailoring.
				For example, when typesetting ''text-orientation/upright'' text,
				Tibetan tsek and shad marks are kept with the preceding grapheme cluster,
				rather than treated as an independent [=typographic character unit=].
				[[!CSS-WRITING-MODES-4]]
		</ul>
	</div>

	A <dfn export>typographic letter unit</dfn>
	(or <dfn noexport>letter</dfn> for the purpose of this specification)
	is a [=typographic character unit=] belonging to one of the Letter or Number
	[=general categories=].
	See [[#character-properties]]
	for how to determine the Unicode properties of a [=typographic character unit=].

	The rendering characteristics of a [=typographic character unit=] divided
	by an element boundary is undefined.
	Ideally each component should be rendered
	according to the formatting requirements of its respective element’s properties
	while maintaining correct shaping and positioning
	of the [=typographic character unit=] as a whole.
	However, depending on the nature of the formatting differences between its parts
	and the capabilities of the font technology in use,
	this is not always possible.
	Therefore such a [=typographic character unit=]
	may be rendered as belonging to either side of the boundary,
	or as some approximation of belonging to both.
	Authors are forewarned that dividing [=grapheme clusters=]
	or ligatures
	by element boundaries may give inconsistent or undesired results.

<h3 id="text-encoding">
Text Processing</h3>

	<wpt title="
		This section has adequate coverage.
		Exhaustive coverage unrealistic,
		since this section is effectively a dependency on all of Unicode.
		Some tests nonetheless provided for key functionality
		(such as the effect of certain control characters on Arabic shaping)."></wpt>

	CSS is built on <a href="https://www.unicode.org/versions/latest/">Unicode</a>.
	[[UNICODE]]
	UAs that support Unicode must adhere to all normative requirements
	of the Unicode Core Standard,
	except where explicitly overridden by CSS.
	UAs implemented on the basis of a non-Unicode text encoding model are still
	expected to fulfill the same text handling requirements
	by assuming an appropriate mapping and analogous behavior.

	<wpt>
	text-encoding/shaping-join-001.html
	text-encoding/shaping-join-002.html
	text-encoding/shaping-join-003.html
	text-encoding/shaping-no-join-001.html
	text-encoding/shaping-no-join-002.html
	text-encoding/shaping-no-join-003.html
	text-encoding/shaping-tatweel-001.html
	text-encoding/shaping-tatweel-002.html
	text-encoding/shaping-tatweel-003.html
	shaping/shaping-arabic-diacritics-001.html
	shaping/shaping-arabic-diacritics-002.html
	white-space/full-width-leading-spaces-005.html
	</wpt>

	For the purpose of determining adjacency for text processing
	(such as white space processing, text transformation, line-breaking, etc.),
	and thus in general within this specification,
	intervening [=inline box=] boundaries and [=out-of-flow=] elements
	must be ignored.
	With respect to text shaping, however, see [[#boundary-shaping]].

	<wpt>
	line-breaking/line-breaking-002.html
	line-breaking/line-breaking-003.html
	line-breaking/line-breaking-004.html
	line-breaking/line-breaking-005.html
	line-breaking/line-breaking-006.html
	line-breaking/line-breaking-007.html
	line-breaking/line-breaking-008.html
	<!-- to be moved/removed together with the segment break transformation text
	white-space/seg-break-transformation-018.html
	white-space/seg-break-transformation-019.html
	-->
	word-break/word-break-min-content-002.html
	word-break/word-break-min-content-003.html
	word-break/word-break-min-content-004.html
	word-break/word-break-min-content-005.html
	overflow-wrap/overflow-wrap-anywhere-010.html
	</wpt>

	<wpt pathprefix="css/CSS2/text"/>
	white-space-processing-048.xht
	white-space-processing-049.xht
	</wpt>

<h2 id="transforming">
Transforming Text</h2>

	<wpt title="
		This section and its subsections have good test coverage overall,
		and very good i18n coverage in particular.

		Missing tests:
		* no test of Amimation type.

		Possible additions:
		* An automated test for plain text copy&amp;paste not applying transforms. Not clear such an <em>automated</em> test is possible, but it would be nice to have one if it were."></wpt>

<h3 id="text-transform-property" oldids="text-transform,caps-prop">
Case Transforms: the 'text-transform' property</h3>

	<pre class="propdef">
	Name: text-transform
	Value: none | [capitalize | uppercase | lowercase ] || full-width || full-size-kana
	Initial: none
	Applies to: text
	Inherited: yes
	Canonical order: n/a
	Computed value: specified keyword
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/text-transform-valid.html
	parsing/text-transform-invalid.html
	parsing/text-transform-computed.html
	text-transform/text-transform-multiple-001.html
	</wpt>

	<wpt pathprefix="/css/CSS2/css1">
	c545-txttrans-000.xht
	</wpt>

	<wpt pathprefix="/css/CSS2/text/">
	text-transform-005.xht
	text-transform-applies-to-001.xht
	text-transform-applies-to-002.xht
	text-transform-applies-to-003.xht
	text-transform-applies-to-005.xht
	text-transform-applies-to-006.xht
	text-transform-applies-to-007.xht
	text-transform-applies-to-008.xht
	text-transform-applies-to-009.xht
	text-transform-applies-to-010.xht
	text-transform-applies-to-011.xht
	text-transform-applies-to-012.xht
	text-transform-applies-to-013.xht
	text-transform-applies-to-014.xht
	text-transform-applies-to-015.xht
	</wpt>

	This property transforms text for styling purposes.
	It has no effect on the underlying content,
	and must not affect the content of a plain text copy &amp; paste operation.

	Note: The 'text-transform' property only affects the presentation layer;
	correct casing for semantic purposes is expected to be represented
	in the source document.

	<wpt>
	text-transform/text-transform-copy-paste-001-manual.html
	</wpt>

	Values have the following meanings:

	<dl dfn-for=text-transform dfn-type=value>
		<dt><dfn>none</dfn>
		<dd>
			No effects.

			<wpt>
			text-transform/text-transform-none-001.xht
			</wpt>

			<wpt pathprefix="/css/CSS2/text/">
			text-transform-004.xht
			</wpt>

		<dt><dfn>capitalize</dfn>
		<dd>
			Puts the first [=typographic letter unit=] of each word, if lowercase, in titlecase;
			other characters are unaffected.

			<wpt>
			text-transform/text-transform-capitalize-001.html
			text-transform/text-transform-capitalize-003.html
			text-transform/text-transform-capitalize-005.html
			text-transform/text-transform-capitalize-007.html
			text-transform/text-transform-capitalize-009.html
			text-transform/text-transform-capitalize-010.html
			text-transform/text-transform-capitalize-011.html
			text-transform/text-transform-capitalize-014.html
			text-transform/text-transform-capitalize-016.html
			text-transform/text-transform-capitalize-018.html
			text-transform/text-transform-capitalize-020.html
			text-transform/text-transform-capitalize-022.html
			text-transform/text-transform-capitalize-024.html
			text-transform/text-transform-capitalize-026.html
			text-transform/text-transform-capitalize-028.html
			text-transform/text-transform-capitalize-030.html
			text-transform/text-transform-capitalize-031.html
			text-transform/text-transform-capitalize-032.xht
			</wpt>

			<wPt pathprefix="/css/CSS2/text/">
			text-transform-001.xht
			text-transform-cap-001.xht
			text-transform-cap-002.xht
			text-transform-cap-003.xht
			</wpt>

		<dt><dfn>uppercase</dfn>
		<dd>
			Puts all [=letters=] in uppercase.

			<wpt>
			text-transform/text-transform-uppercase-101.xht
			text-transform/text-transform-upperlower-001.html
			text-transform/text-transform-upperlower-003.html
			text-transform/text-transform-upperlower-005.html
			text-transform/text-transform-upperlower-007.html
			text-transform/text-transform-upperlower-009.html
			text-transform/text-transform-upperlower-011.html
			text-transform/text-transform-upperlower-015.html
			text-transform/text-transform-upperlower-017.html
			text-transform/text-transform-upperlower-019.html
			text-transform/text-transform-upperlower-021.html
			text-transform/text-transform-upperlower-023.html
			text-transform/text-transform-upperlower-025.html
			text-transform/text-transform-upperlower-027.html
			text-transform/text-transform-upperlower-029.html
			text-transform/text-transform-upperlower-031.html
			text-transform/text-transform-upperlower-044.html
			text-transform/text-transform-upperlower-101.html
			text-transform/text-transform-upperlower-103.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text/">
			text-transform-003.xht
			text-transform-bicameral-001.xht
			text-transform-bicameral-003.xht
			text-transform-bicameral-005.xht
			text-transform-bicameral-007.xht
			text-transform-bicameral-009.xht
			text-transform-bicameral-011.xht
			text-transform-bicameral-013.xht
			text-transform-bicameral-015.xht
			text-transform-bicameral-017.xht
			text-transform-bicameral-019.xht
			text-transform-bicameral-021.xht
			text-transform-unicase-001.xht
			text-transform-uppercase-001.xht
			text-transform-uppercase-002.xht
			</wpt>

		<dt><dfn>lowercase</dfn>
		<dd>
			Puts all [=letters=] in lowercase.

			<wpt>
			text-transform/text-transform-lowercase-101.xht
			text-transform/text-transform-lowercase-102.xht
			text-transform/text-transform-upperlower-002.html
			text-transform/text-transform-upperlower-004.html
			text-transform/text-transform-upperlower-006.html
			text-transform/text-transform-upperlower-008.html
			text-transform/text-transform-upperlower-010.html
			text-transform/text-transform-upperlower-012.html
			text-transform/text-transform-upperlower-014.html
			text-transform/text-transform-upperlower-016.html
			text-transform/text-transform-upperlower-018.html
			text-transform/text-transform-upperlower-020.html
			text-transform/text-transform-upperlower-022.html
			text-transform/text-transform-upperlower-024.html
			text-transform/text-transform-upperlower-026.html
			text-transform/text-transform-upperlower-028.html
			text-transform/text-transform-upperlower-030.html
			text-transform/text-transform-upperlower-102.html
			text-transform/text-transform-upperlower-104.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text/">
			text-transform-002.xht
			text-transform-bicameral-002.xht
			text-transform-bicameral-004.xht
			text-transform-bicameral-006.xht
			text-transform-bicameral-008.xht
			text-transform-bicameral-010.xht
			text-transform-bicameral-012.xht
			text-transform-bicameral-014.xht
			text-transform-bicameral-016.xht
			text-transform-bicameral-018.xht
			text-transform-bicameral-020.xht
			text-transform-bicameral-022.xht
			text-transform-lowercase-001.xht
			</wpt>

		<dt><dfn>full-width</dfn>
		<dd>
			Puts all [=typographic character units=] in [=full-width=] form.
			If a character does not have a corresponding [=full-width=] form,
			it is left as is.
			This value is typically used to typeset Latin letters and digits
			as if they were ideographic characters.

			<wpt>
			text-transform/text-transform-fullwidth-001.xht
			text-transform/text-transform-fullwidth-002.xht
			text-transform/text-transform-fullwidth-004.xht
			text-transform/text-transform-fullwidth-005.xht
			</wpt>

		<dt><dfn>full-size-kana</dfn>
		<dd>
			Converts all [=small Kana=] characters to the equivalent [=full-size Kana=].
			This value is typically used for ruby annotation text,
			where authors may want all small Kana to be drawn as large Kana
			to compensate for legibility issues at the small font sizes typically used in ruby.

			<wpt>
			text-transform/text-transform-full-size-kana-001.html
			text-transform/text-transform-full-size-kana-002.html
			text-transform/text-transform-full-size-kana-003.html
			text-transform/text-transform-full-size-kana-004.html
			text-transform/text-transform-full-size-kana-005.html
			text-transform/text-transform-full-size-kana-006.html
			text-transform/text-transform-full-size-kana-007.html
			</wpt>
	</dl>

	<div class="example">
		The following example converts the ASCII characters
		used in abbreviations in Japanese text to their full-width variants
		so that they lay out and line break like ideographs:

		<pre highlight=css>abbr:lang(ja) { text-transform: full-width; }</pre>
	</div>

	Note: The purpose of 'text-transform' is
	to allow for presentational casing transformations
	without affecting the semantics of the document.
	Note in particular that 'text-transform' casing operations are lossy,
	and can distort the meaning of a text.
	While accessibility interfaces may wish to convey
	the apparent casing of the rendered text to the user,
	the transformed text cannot be relied on to accurately represent
	the underlying meaning of the document.

	<div class="example">
		In this example,
		the first line of text is capitalized as a visual effect.

		<pre highlight=css>
			section > p:first-of-type::first-line {
				text-transform: uppercase;
			}
		</pre>

		This effect cannot be written into the source document
		because the position of the line break depends on layout.
		But also, the capitalization is not reflecting a semantic distinction
		and is not intended to affect the paragraph’s reading;
		therefore it belongs in the presentation layer.
	</div>

	<div class="example">
		In this example,
		the [=ruby=] annotations,
		which are half the size of the main paragraph text,
		are transformed to use regular-size kana
		in place of [=small kana=].

		<pre highlight=css>
			rt { font-size: 50%; text-transform: full-size-kana; }
			:is(h1, h2, h3, h4) rt { text-transform: none; /* unset for large text*/ }
		</pre>

		Note that while this makes such letters easier to see at small type sizes,
		the transformation distorts the text:
		the reader needs to mentally substitute [=small kana=]
		in the appropriate places--
		not unlike reading a Latin inscription
		where all “U”s look like “V”s.

		For example, if ''text-transform: full-size-kana'' were applied to the following source,
		the annotation would read “じゆう” (jiyū), which means “liberty”,
		instead of “じゅう” (jū), which means “ten”,
		the correct reading and meaning for the annotated “十”.
		<xmp highlight=html>
			<ruby>十<rt>じゅう</ruby>
		</xmp>
	</div>

<h4 id="text-transform-mapping">
Mapping Rules</h4>

	For ''capitalize'', what constitutes a “word“ is UA-dependent;
	[[!UAX29]] is suggested (but not required)
	for determining such word boundaries.
	Out-of-flow elements and inline element boundaries
	must not introduce a 'text-transform' word boundary
	and must be ignored when determining such word boundaries.

	<wpt>
	text-transform/text-transform-capitalize-033.html
	</wpt>

	Note: Authors cannot depend on ''capitalize'' to follow
	language-specific titlecasing conventions
	(such as skipping articles in English).

	The UA must use the full case mappings for Unicode characters,
	including any conditional casing rules,
	as defined in the <cite>Default Case Algorithms</cite> section of <cite>The Unicode Standard</cite>.
	[[!UNICODE]]
	If (and only if) the [=content language=] of the element is,
	according to the rules of the [=document language=],
	known,
	then any appropriate language-specific rules must be applied as well.
	These minimally include,
	but are not limited to,
	the language-specific rules in Unicode’s
	<a href="http://www.unicode.org/Public/UNIDATA/SpecialCasing.txt">SpecialCasing.txt</a>.

	<wpt>
	writing-system/writing-system-text-transform-001.html
	text-transform/text-transform-tailoring-001.html
	text-transform/text-transform-tailoring-002.html
	text-transform/text-transform-tailoring-002a.html
	text-transform/text-transform-tailoring-003.html
	text-transform/text-transform-tailoring-004.html
	text-transform/text-transform-tailoring-005.html
	text-transform/text-transform-upperlower-032.html
	text-transform/text-transform-upperlower-033.html
	text-transform/text-transform-upperlower-034.html
	text-transform/text-transform-upperlower-035.html
	text-transform/text-transform-upperlower-038.html
	text-transform/text-transform-upperlower-039.html
	text-transform/text-transform-upperlower-040.html
	text-transform/text-transform-upperlower-041.html
	text-transform/text-transform-upperlower-042.html
	text-transform/text-transform-upperlower-043.html
	</wpt>

	<div class="example">
		For example, in Turkish there are two &ldquo;i&rdquo;s,
		one with a dot--
		&ldquo;İ&rdquo; and &ldquo;i&rdquo;--
		and one without--
		&ldquo;I&rdquo; and &ldquo;ı&rdquo;.
		Thus the usual case mappings between &ldquo;I&rdquo; and &ldquo;i&rdquo;
		are replaced with a different set of mappings
		to their respective dotless/dotted counterparts,
		which do not exist in English.
		This mapping must only take effect
		if the [=content language=] is Turkish
		written in its modern Latin-based [=writing system=]
		(or another Turkic language that uses Turkish casing rules);
		in other languages,
		the usual mapping of &ldquo;I&rdquo; and &ldquo;i&rdquo; is required.
		This rule is thus conditionally defined in Unicode’s SpecialCasing.txt file.
    </div>

	<wpt pathprefix="/css/CSS2/text/">
	text-transform-bicameral-005.xht
	text-transform-bicameral-006.xht
	</wpt>

	The definition of <dfn>full-width</dfn> and <dfn noexport>half-width</dfn> forms
	can be found in <a href="https://www.unicode.org/reports/tr11/"><cite></cite>Unicode Standard Annex #11: East Asian Width</a>.
	[[!UAX11]]
	The mapping to [=full-width=] form is defined
	by taking code points with the <code>&lt;wide&gt;</code>
	or the <code>&lt;narrow&gt;</code> tag
	in their <code>Decomposition_Mapping</code>
	in <a href="https://www.unicode.org/reports/tr44/"><cite></cite>Unicode Standard Annex #44: Unicode Character Database</a>.
	[[!UAX44]]
	For the <code>&lt;narrow&gt;</code> tag,
	the mapping is from the code point to the decomposition
	(minus <code>&lt;narrow&gt;</code> tag),
	and for the <code>&lt;wide&gt;</code> tag,
	the mapping is from the decomposition
	(minus the <code>&lt;wide&gt;</code> tag)
	back to the original code point.

	<wpt>
	text-transform/text-transform-fullwidth-001.xht
	text-transform/text-transform-fullwidth-002.xht
	text-transform/text-transform-fullwidth-004.xht
	text-transform/text-transform-fullwidth-005.xht
	text-transform/text-transform-fullwidth-006.html
	text-transform/text-transform-fullwidth-007.html
	</wpt>

	The mappings for [=small Kana=] to [=full-size Kana=] are defined in [[#small-kana]].

<h4 id="text-transform-order">
Order of Operations</h4>

	When multiple values are specified
	and therefore multiple transformations need to be applied,
	they are applied in the following order:

	<ol>
		<li>''capitalize'', ''uppercase'', and ''lowercase''
		<li>''full-width''
		<li>''full-size-kana''
	</ol>

	<wpt>
	text-transform/text-transform-multiple-001.html
	</wpt>

	Text transformation happens after [[#white-space-phase-1]]
	but before [[#white-space-phase-2]].
	This means that ''full-width'' only transforms
	spaces (U+0020) to U+3000 IDEOGRAPHIC SPACE within [=preserved=] [=white space=].

	<wpt>
	text-transform/text-transform-fullwidth-006.html
	text-transform/text-transform-fullwidth-007.html
	text-transform/text-transform-fullwidth-008.html
	text-transform/text-transform-fullwidth-009.html
	</wpt>

	Note: As defined in [[#order]],
	transforming text affects line-breaking and other formatting operations.

<h2 id="white-space-property" oldids="white-space-collapsing,text-wrap">
White Space and Wrapping: the 'white-space' property</h2>

	<wpt title="
		This section has good overall test coverage,
		particularly through tests for [[#white-space-processing]] and subsections.

		Missing tests:
		* No test of Namimation type
		* Intrinsic (min and max) sizing tests for normal and nowrap."></wpt>

	<pre class="propdef">
	Name: white-space
	Value: normal | pre | nowrap | pre-wrap | break-spaces | pre-line
	Initial: normal
	Applies to: text
	Inherited: yes
	Canonical order: n/a
	Computed value: specified keyword
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/white-space-valid.html
	parsing/white-space-invalid.html
	parsing/white-space-computed.html
	white-space/ws-break-spaces-applies-to-001.html
	white-space/ws-break-spaces-applies-to-002.html
	white-space/ws-break-spaces-applies-to-003.html
	white-space/ws-break-spaces-applies-to-005.html
	white-space/ws-break-spaces-applies-to-006.html
	white-space/ws-break-spaces-applies-to-007.html
	white-space/ws-break-spaces-applies-to-008.html
	white-space/ws-break-spaces-applies-to-009.html
	white-space/ws-break-spaces-applies-to-010.html
	white-space/ws-break-spaces-applies-to-011.html
	white-space/ws-break-spaces-applies-to-012.html
	white-space/ws-break-spaces-applies-to-013.html
	white-space/ws-break-spaces-applies-to-014.html
	white-space/ws-break-spaces-applies-to-015.html
	white-space/white-space-pre-031.html
	white-space/white-space-pre-032.html
	white-space/white-space-pre-034.html
	white-space/white-space-pre-035.html
	</wpt>

	<wpt pathprefix="/css/CSS2/css1/">
	c562-white-sp-000.xht
	</wpt>

	<wpt pathprefix="/css/CSS2/text/">
	white-space-006.xht
	white-space-007.xht
	white-space-applies-to-001.xht
	white-space-applies-to-002.xht
	white-space-applies-to-002.xht
	white-space-applies-to-003.xht
	white-space-applies-to-005.xht
	white-space-applies-to-006.xht
	white-space-applies-to-007.xht
	white-space-applies-to-008.xht
	white-space-applies-to-009.xht
	white-space-applies-to-010.xht
	white-space-applies-to-011.xht
	white-space-applies-to-012.xht
	white-space-applies-to-013.xht
	white-space-applies-to-014.xht
	white-space-applies-to-015.xht
	white-space-mixed-001.xht
	white-space-mixed-002.xht
	white-space-mixed-003.xht
	white-space-mixed-004.xht
	</wpt>

	This property specifies two things:

	<ul>
		<li>whether and how [=white space=] is collapsed
		<li>whether lines may [=wrap=] at unforced [=soft wrap opportunities=]
	</ul>

	Values have the following meanings,
	which must be interpreted according to
	the [[#white-space-rules|White Space Processing]] and
	[[#line-breaking|Line Breaking]] rules:

	<dl dfn-for=white-space dfn-type=value>
		<dt><dfn>normal</dfn>
		<dd>
			This value directs user agents to collapse sequences of [=white space=]
			into a single character
			(or [[#line-break-transform|in some cases]], no character).
			Lines may wrap at allowed [=soft wrap opportunities=],
			as determined by the line-breaking rules in effect,
			in order to minimize inline-axis overflow.

			<wpt>
			white-space/white-space-normal-011.html
			white-space/white-space-pre-031.html
			white-space/white-space-wrap-after-nowrap-001.html
			line-break/line-break-anywhere-and-white-space-004.html
			line-break/line-break-anywhere-and-white-space-005.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text/">
			white-space-normal-001.xht
			white-space-normal-002.xht
			white-space-normal-003.xht
			white-space-normal-004.xht
			white-space-normal-005.xht
			white-space-normal-006.xht
			white-space-normal-007.xht
			white-space-normal-008.xht
			white-space-normal-009.xht
			white-space-p-element-001.xht
			</wpt>

		<dt><dfn>pre</dfn>
		<dd>
			This value prevents user agents from collapsing sequences of [=white space=].
			[=Segment breaks=] such as line feeds
			are preserved as [=forced line breaks=].
			Lines only break at [=forced line breaks=];
			content that does not fit within the block container overflows it.

			<wpt pathprefix="/css/CSS2/text/">
			white-space-pre-001.xht
			white-space-pre-002.xht
			white-space-pre-005.xht
			white-space-pre-006.xht
			white-space-pre-007.xht
			white-space-pre-element-001.xht
			</wpt>

			<wpt>
			white-space/white-space-pre-031.html
			white-space/white-space-pre-032.html
			white-space/white-space-pre-034.html
			white-space/white-space-pre-035.html
			white-space/white-space-pre-011.html
			white-space/white-space-pre-051.html
			white-space/white-space-pre-052.html
			line-break/line-break-anywhere-and-white-space-001.html
			line-break/line-break-anywhere-and-white-space-003.html
			white-space/white-space-zero-fontsize-001.html
			white-space/white-space-zero-fontsize-002.html
			white-space/white-space-intrinsic-size-015.html
			white-space/white-space-intrinsic-size-016.html
			white-space/white-space-intrinsic-size-018.html
			white-space/pre-with-whitespace-crash.html
			word-break/break-boundary-2-chars-002.html
			</wpt>

		<dt><dfn>nowrap</dfn>
		<dd>
			Like ''white-space/normal'',
			this value collapses [=white space=];
			but like ''pre'', it does not allow wrapping.

			<wpt>
			white-space/white-space-nowrap-011.html
			white-space/white-space-wrap-after-nowrap-001.html
			line-break/line-break-anywhere-and-white-space-002.html
			overflow-wrap/overflow-wrap-anywhere-008.html
			white-space/nowrap-wbr-and-space-crash.html
			word-break/break-boundary-2-chars-002.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text/">
			white-space-nowrap-001.xht
			white-space-nowrap-005.xht
			white-space-nowrap-006.xht
			text-align-white-space-004.xht
			text-align-white-space-008.xht
			white-space-nowrap-attribute-001.xht
			white-space-processing-006.xht
			</wpt>

		<dt><dfn>pre-wrap</dfn>
		<dd>
			Like ''pre'',
			this value preserves [=white space=];
			but like ''white-space/normal'',
			it allows wrapping.

			<wpt>
			white-space/pre-wrap-001.html
			white-space/pre-wrap-002.html
			white-space/pre-wrap-003.html
			white-space/pre-wrap-004.html
			white-space/pre-wrap-005.html
			white-space/pre-wrap-006.html
			white-space/pre-wrap-007.html
			white-space/pre-wrap-009.html
			white-space/pre-wrap-010.html
			white-space/pre-wrap-011.html
			white-space/pre-wrap-012.html
			white-space/pre-wrap-013.html
			white-space/pre-wrap-014.html
			white-space/pre-wrap-051.html
			white-space/pre-wrap-052.html
			white-space/textarea-pre-wrap-001.html
			white-space/textarea-pre-wrap-002.html
			white-space/textarea-pre-wrap-003.html
			white-space/textarea-pre-wrap-004.html
			white-space/textarea-pre-wrap-005.html
			white-space/textarea-pre-wrap-006.html
			white-space/textarea-pre-wrap-007.html
			white-space/textarea-pre-wrap-011.html
			white-space/textarea-pre-wrap-012.html
			white-space/textarea-pre-wrap-013.html
			white-space/textarea-pre-wrap-014.html
			white-space/white-space-pre-032.html
			white-space/pre-wrap-leading-spaces-001.html
			white-space/pre-wrap-leading-spaces-002.html
			white-space/pre-wrap-leading-spaces-003.html
			white-space/pre-wrap-leading-spaces-004.html
			white-space/pre-wrap-leading-spaces-005.html
			white-space/pre-wrap-leading-spaces-006.html
			white-space/pre-wrap-leading-spaces-007.html
			white-space/pre-wrap-leading-spaces-008.html
			white-space/pre-wrap-leading-spaces-009.html
			white-space/pre-wrap-leading-spaces-010.html
			white-space/pre-wrap-leading-spaces-011.html
			white-space/pre-wrap-leading-spaces-012.html
			white-space/pre-wrap-leading-spaces-013.html
			white-space/pre-wrap-leading-spaces-014.html
			white-space/pre-wrap-leading-spaces-015.html
			white-space/pre-wrap-leading-spaces-016.html
			white-space/pre-wrap-leading-spaces-017.html
			white-space/white-space-pre-wrap-trailing-spaces-001.html
			white-space/white-space-pre-wrap-trailing-spaces-002.html
			white-space/white-space-pre-wrap-trailing-spaces-003.html
			white-space/white-space-pre-wrap-trailing-spaces-004.html
			white-space/white-space-pre-wrap-trailing-spaces-005.html
			white-space/white-space-pre-wrap-trailing-spaces-006.html
			white-space/white-space-pre-wrap-trailing-spaces-007.html
			white-space/white-space-pre-wrap-trailing-spaces-008.html
			white-space/white-space-pre-wrap-trailing-spaces-010.html
			white-space/white-space-pre-wrap-trailing-spaces-011.html
			white-space/trailing-other-space-separators-002.html
			white-space/pre-wrap-tab-001.html
			white-space/pre-wrap-tab-002.html
			white-space/pre-wrap-tab-003.html
			white-space/pre-wrap-tab-004.html
			white-space/pre-wrap-tab-005.html
			white-space/pre-wrap-tab-006.html
			line-break/line-break-anywhere-and-white-space-006.html
			line-break/line-break-anywhere-and-white-space-007.html
			white-space/white-space-intrinsic-size-013.html
			white-space/white-space-intrinsic-size-014.html
			white-space/white-space-intrinsic-size-017.html
			</wpt>

		<dt><dfn>break-spaces</dfn>
		<dd>
			The behavior is identical to that of ''white-space/pre-wrap'',
			except that:

			<ul>
				<li>
					Any sequence of [=preserved=] [=white space=]
					or [=other space separators=]
					always takes up space,
					including at the end of the line.

					<wpt>
					white-space/white-space-intrinsic-size-001.html
					white-space/white-space-intrinsic-size-002.html
					</wpt>

				<li>
					A line breaking opportunity exists
					after every [=preserved=] [=white space=] character
					and after every [=other space separator=]
					(including between adjacent spaces).

					<wpt>
					overflow-wrap/overflow-wrap-break-word-002.html
					overflow-wrap/overflow-wrap-anywhere-002.html
					white-space/break-spaces-001.html
					white-space/break-spaces-002.html
					white-space/break-spaces-003.html
					white-space/break-spaces-004.html
					white-space/break-spaces-005.html
					white-space/break-spaces-006.html
					white-space/break-spaces-007.html
					white-space/break-spaces-008.html
					white-space/break-spaces-009.html
					white-space/break-spaces-010.html
					white-space/break-spaces-051.html
					white-space/break-spaces-052.html
					white-space/white-space-pre-034.html
					white-space/textarea-break-spaces-001.html
					white-space/textarea-break-spaces-002.html
					white-space/break-spaces-before-first-char-001.html
					white-space/break-spaces-before-first-char-002.html
					white-space/break-spaces-before-first-char-003.html
					white-space/break-spaces-before-first-char-004.html
					white-space/break-spaces-before-first-char-005.html
					white-space/break-spaces-before-first-char-006.html
					white-space/break-spaces-before-first-char-007.html
					white-space/break-spaces-before-first-char-008.html
					white-space/break-spaces-before-first-char-009.html
					white-space/break-spaces-before-first-char-010.html
					white-space/break-spaces-before-first-char-011.html
					white-space/break-spaces-before-first-char-012.html
					white-space/break-spaces-before-first-char-013.html
					white-space/break-spaces-before-first-char-014.html
					white-space/break-spaces-before-first-char-015.html
					white-space/break-spaces-before-first-char-016.html
					white-space/break-spaces-before-first-char-017.html
					white-space/break-spaces-before-first-char-018.html
					white-space/break-spaces-before-first-ideographic-char-001.html
					white-space/break-spaces-before-first-ideographic-char-002.html
					white-space/break-spaces-before-first-ideographic-char-003.html
					white-space/break-spaces-before-first-ideographic-char-004.html
					white-space/break-spaces-before-first-ideographic-char-005.html
					white-space/break-spaces-before-first-ideographic-char-006.html
					white-space/break-spaces-before-first-ideographic-char-007.html
					white-space/break-spaces-before-first-ideographic-char-008.html
					white-space/break-spaces-before-first-ideographic-char-009.html
					white-space/break-spaces-before-first-ideographic-char-010.html
					white-space/break-spaces-before-first-ideographic-char-011.html
					white-space/break-spaces-before-first-ideographic-char-012.html
					white-space/break-spaces-before-first-ideographic-char-013.html
					white-space/break-spaces-before-first-ideographic-char-014.html
					white-space/break-spaces-before-first-ideographic-char-015.html
					white-space/break-spaces-before-first-ideographic-char-016.html
					white-space/break-spaces-before-first-ideographic-char-017.html
					white-space/break-spaces-before-first-ideographic-char-018.html
					white-space/tab-stop-threshold-005.html
					white-space/tab-stop-threshold-006.html
					word-break/word-break-break-all-017.html
					white-space/break-spaces-tab-001.html
					white-space/break-spaces-tab-002.html
					white-space/break-spaces-tab-003.html
					white-space/break-spaces-tab-004.html
					white-space/break-spaces-tab-005.html
					white-space/break-spaces-tab-006.html
					white-space/break-spaces-with-overflow-wrap-001.html
					white-space/break-spaces-with-overflow-wrap-002.html
					white-space/break-spaces-with-overflow-wrap-003.html
					white-space/break-spaces-with-overflow-wrap-004.html
					white-space/break-spaces-with-overflow-wrap-005.html
					white-space/break-spaces-with-overflow-wrap-006.html
					white-space/break-spaces-with-overflow-wrap-007.html
					white-space/break-spaces-with-overflow-wrap-008.html
					white-space/break-spaces-with-overflow-wrap-009.html
					white-space/break-spaces-with-overflow-wrap-010.html
					white-space/break-spaces-with-ideographic-space-001.html
					white-space/break-spaces-with-ideographic-space-002.html
					white-space/break-spaces-with-ideographic-space-003.html
					white-space/break-spaces-with-ideographic-space-004.html
					white-space/break-spaces-with-ideographic-space-005.html
					white-space/break-spaces-with-ideographic-space-006.html
					white-space/break-spaces-with-ideographic-space-007.html
					white-space/break-spaces-with-ideographic-space-008.html
					white-space/break-spaces-with-ideographic-space-009.html
					white-space/break-spaces-with-ideographic-space-010.html
					line-break/line-break-anywhere-and-white-space-008.html
					line-break/line-break-anywhere-and-white-space-009.html
					white-space/ws-break-spaces-applies-to-001.html
					white-space/ws-break-spaces-applies-to-002.html
					white-space/ws-break-spaces-applies-to-003.html
					white-space/ws-break-spaces-applies-to-005.html
					white-space/ws-break-spaces-applies-to-006.html
					white-space/ws-break-spaces-applies-to-007.html
					white-space/ws-break-spaces-applies-to-008.html
					white-space/ws-break-spaces-applies-to-009.html
					white-space/ws-break-spaces-applies-to-010.html
					white-space/ws-break-spaces-applies-to-011.html
					white-space/ws-break-spaces-applies-to-012.html
					white-space/ws-break-spaces-applies-to-013.html
					white-space/ws-break-spaces-applies-to-014.html
					white-space/ws-break-spaces-applies-to-015.html
					white-space/break-spaces-newline-011.html
					white-space/break-spaces-newline-012.html
					white-space/break-spaces-newline-013.html
					white-space/break-spaces-newline-014.html
					white-space/break-spaces-newline-015.html
					white-space/break-spaces-newline-016.html
					white-space/trailing-ideographic-space-break-spaces-001.html
					white-space/trailing-ideographic-space-break-spaces-002.html
					white-space/trailing-ideographic-space-break-spaces-003.html
					white-space/trailing-ideographic-space-break-spaces-004.html
					white-space/trailing-ideographic-space-break-spaces-005.html
					white-space/trailing-ideographic-space-break-spaces-006.html
					white-space/trailing-ideographic-space-break-spaces-007.html
					white-space/trailing-ideographic-space-break-spaces-008.html
					</wpt>

			</ul>

			Note: This value does not guarantee
			that there will never be any overflow due to white space:
			for example, if the line length is so short
			that even a single white space character does not fit,
			overflow is unavoidable.

			<dt><dfn>pre-line</dfn>
			<dd>
				Like ''white-space/normal'',
				this value collapses consecutive [=white space characters=]
				and allows wrapping,
				but it preserves [=segment breaks=] in the source as [=forced line breaks=].

				<wpt pathprefix="/css/CSS2/text/">
				white-space-005.xht
				white-space-generated-content-before-001.xht
				white-space-processing-004.xht
				white-space-processing-007.xht
				white-space-processing-010.xht
				white-space-processing-017.xht
				white-space-processing-021.xht
				white-space-processing-024.xht
				white-space-processing-027.xht
				white-space-processing-028.xht
				white-space-processing-029.xht
				white-space-processing-030.xht
				white-space-processing-035.xht
				white-space-processing-036.xht
				white-space-processing-045.xht
				white-space-processing-053.xht
				text-align-white-space-002.xht
				text-align-white-space-006.xht
				</wpt>

				<wpt>
				white-space/pre-line-051.html
				white-space/pre-line-052.html
				white-space/white-space-pre-035.html
				white-space/white-space-intrinsic-size-019.html
				white-space/white-space-intrinsic-size-020.html
				white-space/pre-line-br-with-whitespace-child-crash.html
				white-space/pre-line-with-space-and-newline.html
				</wpt>
	</dl>

	[=White space=] that was not removed or collapsed due to white space processing
	is called <dfn export local-lt="preserved">preserved white space</dfn>.

	Note: In some cases,
	[=preserved white space=] and [=other space separators=]
	can [=hang=] when at the end of the line;
	this can affect whether they are measured for [=intrinsic sizing=].

	The following informative table summarizes the behavior
	of various 'white-space' values:

	<table class="data">
		<colgroup class="header"></colgroup>
		<colgroup span=5></colgroup>
		<thead>
			<tr>
				<th>
				<th>New Lines
				<th>Spaces and Tabs
				<th>Text Wrapping
				<th>End-of-line [=spaces=]
				<th>End-of-line [=other space separators=]

		<tbody>
			<tr>
				<th>''white-space/normal''
				<td>Collapse
				<td>Collapse
				<td>Wrap
				<td>Remove
				<td>Hang

			<tr>
				<th>''pre''
				<td>Preserve
				<td>Preserve
				<td>No wrap
				<td>Preserve
				<td>No wrap

			<tr>
				<th>''nowrap''
				<td>Collapse
				<td>Collapse
				<td>No wrap
				<td>Remove
				<td>Hang

			<tr>
				<th>''pre-wrap''
				<td>Preserve
				<td>Preserve
				<td>Wrap
				<td>Hang
				<td>Hang

			<tr>
				<th>''break-spaces''
				<td>Preserve
				<td>Preserve
				<td>Wrap
				<td>Wrap
				<td>Wrap

			<tr>
				<th>''pre-line''
				<td>Preserve
				<td>Collapse
				<td>Wrap
				<td>Remove
				<td>Hang
	</table>

	See [[#white-space-processing|White Space Processing Rules]]
	for details on how [=white space=] collapses.

<!-- This is part of segment break transformation
	An informative summary of collapsing (''white-space/normal'' and ''nowrap'') is presented below:
	<ul class=non-normative>
		<li>
			A sequence of segment breaks and other [=white space=]
			between two Chinese, Japanese, or Yi characters
			collapses into nothing.

		<li>
			A zero width space before or after a [=white space=] sequence
			containing a segment break
			causes the entire sequence of [=white space=]
			to collapse into a zero width space.

		<li>
			Otherwise,
			consecutive [=white space=] collapses into a single [=space=].
	</ul>
-->

	See [[#line-breaking|Line Breaking]]
	for details on wrapping behavior.

<h2 id="white-space-processing">
White Space Processing &amp; Control Characters</h2>

	<wpt title="
		This section has reasonably good test coverage.

		Missing tests:
		* “As required by Unicode, unsupported Default_ignorable characters must be ignored for text rendering”"></wpt>

	The source text of a document often contains formatting
	that is not relevant to the final rendering:
	for example,
	<a href="https://rhodesmill.org/brandon/2012/one-sentence-per-line/">breaking the source into segments</a>
	(lines) for ease of editing
	or adding [=white space characters=] such as [=tabs=] and [=spaces=]
	to indent the source code.
	CSS white space processing allows the author
	to control interpretation of such formatting:
	to preserve or collapse it away when rendering the document.
	White space processing in CSS
	(which is controlled with the 'white-space' property)
	interprets [=white space characters=] only for rendering:
	it has no effect on the underlying document data.

	Note: Depending on the document language,
	segments can be separated by a particular newline sequence
	(such as a line feed or CRLF pair),
	or delimited by some other mechanism,
	such as the SGML <code>RECORD-START</code> and <code>RECORD-END</code> tokens.

	<p id="segment-normalization">
	For CSS processing,
	each document language&ndash;defined “segment break” or “newline sequence”--
	or if none are defined,  each line feed (U+000A)--
	in the text is treated as a <dfn export>segment break</dfn>,
	which is then interpreted for rendering as specified by the 'white-space' property.

	In the case of HTML,
	each [[html#newlines|newline sequence is normalized]] to a single line feed (U+000A)
	for representation in the DOM,
	so when an HTML document is represented as a DOM tree
	each line feed (U+000A)
	is treated as a [=segment break=].
	[[HTML]]
	[[DOM]]

	Note: In most common CSS implementations,
	HTML does not get styled directly.
	Instead, it is processed into a DOM tree,
	which is then styled.
	Unlike HTML,
	the DOM does not give any particular meaning to carriage returns (U+000D),
	so they are not treated as [=segment breaks=].
	If carriage returns (U+000D) are inserted into the DOM
	by means other than HTML parsing,
	they then get treated as defined below.

	<wpt pathprefix="/css/CSS2/text">
	white-space-processing-005.xht
	white-space-processing-006.xht
	white-space-processing-007.xht
	</wpt>

	Note: A document parser might
	not only normalize any [=segment breaks=],
	but also collapse other space characters or
	otherwise process white space according to markup rules.
	Because CSS processing occurs <em>after</em> the parsing stage,
	it is not possible to restore these characters for styling.
	Therefore, some of the behavior specified below
	can be affected by these limitations and
	may be user agent dependent.

	Note: Anonymous blocks consisting entirely of [=collapsible=] [=white space=]
	are removed from the rendering tree.
	Thus any such [=white space=] surrounding a block-level element is collapsed away.
	See [[CSS2/visuren#anonymous]].
	[[CSS2]]

	Control characters ([=Unicode category=] <code>Cc</code>)--
	other than tabs (U+0009),
	line feeds (U+000A),
	carriage returns (U+000D)
	and sequences that form a [=segment break=]--
	must be rendered as a visible glyph
	which the UA must synthesize if the glyphs found in the font are not visible,
	and must be otherwise treated as any other character
	of the Other Symbols (<code>So</code>) [=general category=] and Common [=Unicode Script|script=].
	The UA may use a glyph provided by a font specifically for the control character,
	substitute the glyphs provided for the corresponding symbol in the Control Pictures block,
	generate a visual representation of its code point value,
	or use some other method to provide an appropriate visible glyph.
	As required by Unicode,
	unsupported <code>Default_ignorable</code> characters
	must be ignored for text rendering.
	[[!UNICODE]]

	<wpt>
	white-space/control-chars-000.html
	white-space/control-chars-001.html
	white-space/control-chars-002.html
	white-space/control-chars-003.html
	white-space/control-chars-004.html
	white-space/control-chars-005.html
	white-space/control-chars-006.html
	white-space/control-chars-007.html
	white-space/control-chars-008.html
	white-space/control-chars-00B.html
	white-space/control-chars-00C.html
	white-space/control-chars-00D.html
	white-space/control-chars-00E.html
	white-space/control-chars-00F.html
	white-space/control-chars-010.html
	white-space/control-chars-011.html
	white-space/control-chars-012.html
	white-space/control-chars-013.html
	white-space/control-chars-014.html
	white-space/control-chars-015.html
	white-space/control-chars-016.html
	white-space/control-chars-017.html
	white-space/control-chars-018.html
	white-space/control-chars-019.html
	white-space/control-chars-01A.html
	white-space/control-chars-01B.html
	white-space/control-chars-01C.html
	white-space/control-chars-01D.html
	white-space/control-chars-01E.html
	white-space/control-chars-01F.html
	white-space/control-chars-07F.html
	white-space/control-chars-080.html
	white-space/control-chars-081.html
	white-space/control-chars-082.html
	white-space/control-chars-083.html
	white-space/control-chars-084.html
	white-space/control-chars-085.html
	white-space/control-chars-086.html
	white-space/control-chars-087.html
	white-space/control-chars-088.html
	white-space/control-chars-089.html
	white-space/control-chars-08A.html
	white-space/control-chars-08B.html
	white-space/control-chars-08C.html
	white-space/control-chars-08D.html
	white-space/control-chars-08E.html
	white-space/control-chars-08F.html
	white-space/control-chars-090.html
	white-space/control-chars-091.html
	white-space/control-chars-092.html
	white-space/control-chars-093.html
	white-space/control-chars-094.html
	white-space/control-chars-095.html
	white-space/control-chars-096.html
	white-space/control-chars-097.html
	white-space/control-chars-098.html
	white-space/control-chars-099.html
	white-space/control-chars-09A.html
	white-space/control-chars-09B.html
	white-space/control-chars-09C.html
	white-space/control-chars-09D.html
	white-space/control-chars-09E.html
	white-space/control-chars-09F.html
	</wpt>

	<wpt pathprefix="/css/CSS2/other-formats">
	control-characters-001.html
	</wpt>

	<wpt pathprefix="/css/CSS2/text">
	control-characters-002.xht
	white-space-control-characters-001.xht
	</wpt>

	Carriage returns (U+000D) are treated identically to spaces (U+0020) in all respects.

	<wpt>
	white-space/control-chars-00D.html
	</wpt>

	<wpt pathprefix="/css/CSS2/text">
	white-space-processing-005.xht
	white-space-processing-006.xht
	white-space-processing-007.xht
	</wpt>

	Note: For HTML documents,
	carriage returns present in the source code
	are converted to line feeds at the parsing stage
	(see [[HTML#preprocessing-the-input-stream]]
	and the definition of [=normalize newlines=] in <a href="https://infra.spec.whatwg.org/"><cite>Infra</cite></a>
	and therefore do no appear as U+000D CARRIAGE RETURN to CSS.
	[[HTML]]
	[[INFRA]])
	However, the character <em>is</em> preserved--
	and the above rule observable--
	when encoded using an escape sequence (<code highlight=html>&amp;#x0d;</code>).

<h3 id="white-space-rules">
The White Space Processing Rules</h3>

	<wpt title="
		This section has good test coverage,
		all parts are well exercised.
		Most tests to be found in subsections."></wpt>

	Except where specified otherwise,
	white space processing in CSS affects only
	the <dfn export lt="white space|white space characters| document white space|document white space characters">document white space characters</dfn>:
	<dfn>spaces</dfn> (U+0020), <dfn>tabs</dfn> (U+0009), and [[#white-space-processing|segment breaks]].

	<wpt pathprefix="/css/CSS2/text/">
	white-space-normal-003.xht
	white-space-normal-004.xht
	white-space-normal-005.xht
	white-space-normal-006.xht
	white-space-normal-007.xht
	white-space-normal-008.xht
	white-space-nowrap-005.xht
	white-space-nowrap-006.xht
	white-space-pre-005.xht
	white-space-pre-006.xht
	white-space-processing-054.xht
	white-space-processing-055.xht
	white-space-processing-056.xht
	</wpt>

	Note: The set of characters considered [=document white space=]
	(part of the document content)
	and those considered syntactic white space
	(part of the CSS syntax)
	are not necessarily identical.
	However, since both include spaces (U+0020), tabs (U+0009), and line feeds (U+000A)
	most authors won’t notice any differences.

	Besides space (U+0020)
	and no-break space (U+00A0),
	Unicode defines a number of additional space separator characters.
	[[UNICODE]]
	In this specification
	all characters in the Unicode [=general category=] Zs
	except space (U+0020)
	and no-break space (U+00A0)
	are collectively referred to as
	<dfn>other space separators</dfn>.

	<wpt>
	white-space/trailing-other-space-separators-001.html
	white-space/trailing-other-space-separators-002.html
	white-space/trailing-other-space-separators-003.html
	white-space/trailing-other-space-separators-004.html
	white-space/trailing-other-space-separators-break-spaces-001.html
	white-space/trailing-other-space-separators-break-spaces-002.html
	white-space/trailing-other-space-separators-break-spaces-003.html
	white-space/trailing-other-space-separators-break-spaces-004.html
	white-space/trailing-other-space-separators-break-spaces-005.html
	white-space/trailing-other-space-separators-break-spaces-006.html
	white-space/trailing-other-space-separators-break-spaces-007.html
	white-space/trailing-other-space-separators-break-spaces-008.html
	white-space/trailing-other-space-separators-break-spaces-009.html
	white-space/trailing-other-space-separators-break-spaces-010.html
	white-space/trailing-other-space-separators-break-spaces-011.html
	white-space/trailing-other-space-separators-break-spaces-012.html
	white-space/trailing-other-space-separators-break-spaces-013.html
	white-space/trailing-other-space-separators-break-spaces-014.html
	white-space/trailing-other-space-separators-break-spaces-015.html
	</wpt>

<h4 id="white-space-phase-1">
Phase I: Collapsing and Transformation</h4>

	<wpt title="
		This section has good test coverage,
		all parts are well exercised."></wpt>

	For each inline
	(including anonymous inlines;
	see [[CSS2/visuren#anonymous]] [[CSS2]])
	within an [=inline formatting context=],
	[=white space characters=] are processed as follows
	prior to [=line breaking=] and [[css-writing-modes-4#text-direction|bidi reordering]],
	ignoring <dfn noexport>bidi formatting characters</dfn>
	(characters with the <code>Bidi_Control</code> property [[!UAX9]])
	as if they were not there:

	<wpt>
	white-space/white-space-collapse-002.html
	white-space/white-space-normal-011.html
	white-space/white-space-nowrap-011.html
	</wpt>

	<ul>
		<li id="collapse">
			If 'white-space' is set to ''white-space/normal'', ''nowrap'', or ''pre-line'',
			[=white space characters=] are considered <dfn export lt="collapsible white space" local-lt="collapsible">collapsible</dfn>
			and are processed by performing the following steps:

			<ol>
				<li>
					Any sequence of collapsible [=spaces=] and [=tabs=]
					immediately preceding or following a [=segment break=]
					is removed.

					<wpt>
<!-- to be moved/removed together with the segment break transformation text
					 white-space/seg-break-transformation-000.html
-->
					white-space/white-space-normal-011.html
					white-space/white-space-nowrap-011.html
					</wpt>

					<wpt pathprefix="/css/CSS2/text/">
					white-space-processing-002.xht
					white-space-processing-003.xht
					white-space-processing-004.xht
					white-space-processing-008.xht
					white-space-processing-009.xht
					white-space-processing-010.xht
					white-space-processing-005.xht
					white-space-processing-006.xht
					white-space-processing-007.xht
					</wpt>

				<li>
					Collapsible [=segment breaks=] are transformed for rendering
					according to the [[#line-break-transform|segment break transformation rules]].

				<li>
					Every [=collapsible=] [=tab=] is converted to a collapsible space (U+0020).

					<wpt>
					white-space/white-space-collapse-000.html
					white-space/white-space-normal-011.html
					white-space/white-space-nowrap-011.html
					</wpt>

					<wpt pathprefix="/css/CSS2/text/">
					white-space-processing-019.xht
					white-space-processing-020.xht
					white-space-processing-021.xht
					</wpt>

				<li>
					Any [=collapsible=] [=space=] immediately following another [=collapsible=] [=space=]--
					even one outside the boundary of the inline containing that [=space=],
					provided both [=spaces=] are within the same inline formatting context--
					is collapsed to have zero advance width.
					(It is invisible,
					but retains its [=soft wrap opportunity=],
					if any.)

					<wpt>
					white-space/white-space-collapse-001.html
					white-space/white-space-empty-text-sibling.html
					white-space/white-space-normal-011.html
					white-space/white-space-nowrap-011.html
					</wpt>

					<wpt pathprefix="/css/CSS2/text/">
					white-space-001.xht
					white-space-003.xht
					white-space-005.xht
					white-space-collapsing-001.xht
					white-space-collapsing-002.xht
					white-space-collapsing-004.xht
					white-space-collapsing-005.xht
					white-space-collapsing-breaks-001.xht
					white-space-mixed-001.xht
					white-space-mixed-002.xht
					white-space-normal-001.xht
					white-space-processing-001.xht
					white-space-processing-022.xht
					white-space-processing-023.xht
					white-space-processing-024.xht
					white-space-processing-025.xht
					white-space-processing-026.xht
					white-space-processing-027.xht
					white-space-processing-028.xht
					white-space-processing-029.xht
					white-space-processing-030.xht
					white-space-processing-031.xht
					white-space-processing-032.xht
					white-space-processing-033.xht
					white-space-processing-034.xht
					white-space-processing-035.xht
					white-space-processing-036.xht
					white-space-processing-050.xht
					white-space-processing-051.xht
					white-space-processing-053.xht
					</wpt>
			</ol>

		<li>
			If 'white-space' is set to ''pre'', ''pre-wrap'', or ''break-spaces'',
			any sequence of spaces is treated as a sequence of non-breaking spaces.
			However, for ''pre-wrap'',
			a [=soft wrap opportunity=] exists at the end of a sequence of [=spaces=] and/or [=tabs=],
			while for ''break-spaces'',
			a [=soft wrap opportunity=] exists after every [=space=] and every [=tab=].

			<wpt>
			white-space/white-space-pre-011.html
			overflow-wrap/overflow-wrap-break-word-004.html
			overflow-wrap/overflow-wrap-break-word-005.html
			overflow-wrap/overflow-wrap-break-word-006.html
			overflow-wrap/overflow-wrap-break-word-007.html
			overflow-wrap/overflow-wrap-anywhere-004.html
			overflow-wrap/overflow-wrap-anywhere-005.html
			word-break/word-break-break-all-011.html
			word-break/word-break-break-all-012.html
			word-break/word-break-break-all-013.html
			word-break/word-break-break-all-015.html
			white-space/break-spaces-006.html
			white-space/break-spaces-007.html
			white-space/break-spaces-008.html
			white-space/break-spaces-009.html
			white-space/break-spaces-010.html
			white-space/break-spaces-before-first-char-001.html
			white-space/break-spaces-before-first-char-002.html
			white-space/break-spaces-before-first-char-003.html
			white-space/break-spaces-before-first-char-004.html
			white-space/break-spaces-before-first-char-005.html
			white-space/break-spaces-before-first-char-006.html
			white-space/break-spaces-before-first-char-011.html
			white-space/break-spaces-before-first-ideographic-char-001.html
			white-space/break-spaces-before-first-ideographic-char-002.html
			white-space/break-spaces-before-first-ideographic-char-003.html
			white-space/break-spaces-before-first-ideographic-char-004.html
			white-space/break-spaces-before-first-ideographic-char-005.html
			white-space/break-spaces-before-first-ideographic-char-006.html
			white-space/break-spaces-before-first-ideographic-char-011.html
			white-space/pre-wrap-008.html
			white-space/pre-wrap-015.html
			white-space/pre-wrap-016.html
			white-space/pre-wrap-leading-spaces-001.html
			white-space/pre-wrap-leading-spaces-002.html
			white-space/pre-wrap-leading-spaces-003.html
			white-space/pre-wrap-leading-spaces-004.html
			white-space/pre-wrap-leading-spaces-005.html
			white-space/pre-wrap-leading-spaces-006.html
			white-space/pre-wrap-leading-spaces-007.html
			white-space/pre-wrap-leading-spaces-008.html
			white-space/pre-wrap-leading-spaces-009.html
			white-space/pre-wrap-leading-spaces-010.html
			white-space/pre-wrap-leading-spaces-011.html
			white-space/pre-wrap-leading-spaces-012.html
			white-space/pre-wrap-leading-spaces-013.html
			white-space/pre-wrap-leading-spaces-014.html
			white-space/break-spaces-tab-001.html
			white-space/break-spaces-tab-002.html
			white-space/break-spaces-tab-003.html
			white-space/break-spaces-tab-004.html
			white-space/pre-wrap-tab-001.html
			white-space/pre-wrap-tab-002.html
			white-space/pre-wrap-tab-003.html
			white-space/pre-wrap-tab-004.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text/">
			white-space-002.xht
			white-space-004.xht
			white-space-processing-011.xht
			white-space-processing-012.xht
			white-space-processing-013.xht
			white-space-processing-052.xht
			</wpt>
	</ul>

	<wpt pathprefix="/css/CSS2/">
	bidi-text/bidi-002.xht
	bidi-text/bidi-004.xht
	bidi-text/line-breaking-bidi-001.xht
	bidi-text/line-breaking-bidi-002.xht
	bidi-text/line-breaking-bidi-003.xht
	</wpt>

	<wpt pathprefix="/css/CSS2/text/">
	white-space-collapsing-bidi-001.xht
	white-space-collapsing-bidi-002.xht
	</wpt>

	<div class="example" id="egbidiwscollapse">
		The following example illustrates
		the interaction of white-space collapsing and bidirectionality.
		Consider the following markup fragment, taking special note of [=spaces=]
		(with varied backgrounds and borders for emphasis and identification):

		<pre><code>&lt;ltr&gt;A<span class="egbidiwsaA">&#160;</span>&lt;rtl&gt;<span class="egbidiwsbB">&#160;</span>B<span class="egbidiwsaB">&#160;</span>&lt;/rtl&gt;<span class="egbidiwsbC">&#160;</span>C&lt;/ltr&gt;</code></pre>

		where the <code>&lt;ltr&gt;</code> element represents a left-to-right embedding
		and the <code>&lt;rtl&gt;</code> element represents a right-to-left embedding.
		If the 'white-space' property is set to ''white-space/normal'',
		the white-space processing model will result in the following:

		<ul style="line-height:1.3">
			<li>
				The [=space=] before the B (<span class="egbidiwsbB">&#160;</span>)
				will collapse with the [=space=] after the A (<span class="egbidiwsaA">&#160;</span>).
			<li>
				The [=space=] before the C (<span class="egbidiwsbC">&#160;</span>)
				will collapse with the [=space=] after the B (<span class="egbidiwsaB">&#160;</span>).
		</ul>

		This will leave two [=spaces=],
		one after the A in the left-to-right embedding level,
		and one after the B in the right-to-left embedding level.
		The text will then be ordered according to the Unicode bidirectional algorithm,
		with the end result being:

		<pre>A<span class="egbidiwsaA">&#160;</span><span class="egbidiwsaB">&#160;</span>BC</pre>

		Note that there will be two [=spaces=] between A and B,
		and none between B and C.
		This is best avoided by putting [=spaces=] outside the element
		instead of just inside the opening and closing tags
		and, where practical,
		by relying on implicit bidirectionality instead of explicit embedding levels.
	</div>

	<wpt pathprefix="/css/CSS2/text/">
	white-space-bidirectionality-001.xht
	</wpt>

<h4 id="white-space-phase-2">
Phase II: Trimming and Positioning</h4>

	<wpt title="
		This section has good test coverage,
		all parts are well exercised."></wpt>

	Then, the entire block is rendered.
	Inlines are laid out,
	taking [[css-writing-modes-4#text-direction|bidi reordering]] into account,
	and [=wrapping=] as specified by the 'white-space' property.
	As each line is laid out,

	<ol>
		<li>
			A sequence of [=collapsible=] [=spaces=] at the beginning of a line
			is removed.

			<wpt>
			white-space/line-edge-white-space-collapse-002.html
			white-space/break-spaces-051.html
			white-space/break-spaces-052.html
			white-space/pre-line-051.html
			white-space/pre-line-052.html
			white-space/pre-wrap-051.html
			white-space/pre-wrap-052.html
			white-space/white-space-pre-051.html
			white-space/white-space-pre-052.html
			white-space/full-width-leading-spaces-001.html
			white-space/full-width-leading-spaces-002.html
			white-space/full-width-leading-spaces-003.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text/">
			white-space-collapsing-003.xht
			white-space-collapsing-bidi-003.xht
			white-space-normal-001.xht
			white-space-normal-002.xht
			white-space-processing-037.xht
			white-space-processing-038.xht
			white-space-processing-039.xht
			white-space-processing-040.xht
			white-space-processing-041.xht
			</wpt>

		<li>
			If the [=tab size=] is zero,
			[=preserved=] [=tabs=] are not rendered.
			Otherwise, each [=preserved=] [=tab=] is rendered
			as a horizontal shift that lines up
			the start edge of the next glyph with the next [=tab stop=].
			If this distance is less than 0.5<a value class=no-quote>ch</a>,
			then the subsequent [=tab stop=] is used instead.
			<dfn lt="tab stop">Tab stops</dfn> occur at points
			that are multiples of the [=tab size=]
			from the starting content edge
			of the [=preserved=] [=tab=]’s nearest [=block container=] ancestor.
			The [=tab size=] is given by the 'tab-size' property.

			<wpt>
			white-space/tab-stop-threshold-001.html
			white-space/tab-stop-threshold-002.html
			white-space/tab-stop-threshold-003.html
			white-space/tab-stop-threshold-004.html
			white-space/tab-stop-threshold-005.html
			white-space/tab-stop-threshold-006.html
			white-space/white-space-pre-011.html
			tab-size/tab-min-rendered-width-1.html
			tab-size/tab-size-integer-003.html
			text-indent/text-indent-tab-positions-001.html
			tab-size/tab-size-inline-002.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text/">
			white-space-processing-042.xht
			</wpt>

			Note: See the Unicode <a href="http://unicode.org/reports/tr9/#L1">rules on how tabulation (U+0009) interacts with bidi</a>. [[UAX9]]

			<wpt>
			white-space/tab-bidi-001.html
			</wpt>

		<li>
			A sequence at the end of a line
			of [=collapsible=] [=spaces=]
			is removed,
			as well as any trailing U+1680 &#x1680; OGHAM SPACE MARK
			whose 'white-space' property is ''white-space/normal'', ''nowrap'', or ''pre-line''.

			<wpt>
			white-space/line-edge-white-space-collapse-001.html
			white-space/pre-float-001.html
			white-space/pre-wrap-float-001.html
			white-space/trailing-space-before-br-001.html
			white-space/trailing-ogham-001.html
			white-space/trailing-ogham-002.html
			white-space/trailing-ogham-003.html
			overflow-wrap/overflow-wrap-anywhere-011.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text/">
			white-space-collapsing-003.xht
			white-space-collapsing-bidi-003.xht
			white-space-normal-001.xht
			white-space-normal-002.xht
			white-space-processing-005.xht
			white-space-processing-043.xht
			white-space-processing-044.xht
			white-space-processing-045.xht
			white-space-processing-046.xht
			white-space-processing-047.xht
			</wpt>

			Note: Due to <cite>Unicode Bidirectional Algorithm</cite> rule <a href="http://unicode.org/reports/tr9/#L1">L1</a>,
			a sequence of [=collapsible=] [=spaces=] located at the end of the line
			prior to [[css-writing-modes-4#text-direction|bidi reordering]]
			will also be at the end of the line after reordering.
			[[UAX9]]
			[[CSS-WRITING-MODES-4]]

			<wpt>
			white-space/eol-spaces-bidi-001.html
			white-space/eol-spaces-bidi-003.html
			white-space/trailing-space-rtl-001.html
			</wpt>

		<li>
			If there remains any sequence of [=white space=],
			[=other space separators=],
			and/or [=preserved=] [=tabs=]
			at the end of a line
			(after [[css-writing-modes-4#text-direction|bidi reordering]] [[CSS-WRITING-MODES-4]]):

			<ul>
				<li>
					If 'white-space' is set to ''white-space/normal'',
					''white-space/nowrap'',
					or ''white-space/pre-line'',
					the UA must [=hang=] this sequence (unconditionally).

					<wpt>
					white-space/trailing-ideographic-space-001.html
					white-space/trailing-ideographic-space-002.html
					white-space/trailing-ideographic-space-005.html
					white-space/trailing-ideographic-space-006.html
					white-space/trailing-ideographic-space-007.html
					white-space/trailing-ideographic-space-008.html
					white-space/trailing-ideographic-space-009.html
					white-space/trailing-ideographic-space-010.html
					white-space/trailing-ideographic-space-011.html
					white-space/trailing-ideographic-space-012.html
					white-space/trailing-ideographic-space-013.html
					white-space/trailing-ideographic-space-014.html
					white-space/trailing-ideographic-space-015.html
					white-space/trailing-ideographic-space-016.html
					white-space/trailing-ideographic-space-017.html
					white-space/trailing-ideographic-space-018.html
					white-space/trailing-ideographic-space-019.html
					white-space/trailing-ideographic-space-020.html
					white-space/trailing-ideographic-space-021.html
					white-space/trailing-ideographic-space-022.html
					white-space/trailing-ideographic-space-023.html
					white-space/trailing-ideographic-space-024.html
					white-space/trailing-ideographic-space-025.html
					white-space/trailing-other-space-separators-001.html
					white-space/trailing-other-space-separators-003.html
					white-space/trailing-other-space-separators-004.html
					text-transform/text-transform-fullwidth-008.html
					white-space/white-space-intrinsic-size-019.html
					white-space/white-space-intrinsic-size-020.html
					</wpt>

				<li>
					If 'white-space' is set to ''pre-wrap'',
					the UA must (unconditionally) [=hang=] this sequence,
					unless the sequence is followed by a [=forced line break=],
					in which case it must [=conditionally hang=] the sequence is instead.
					It may also visually collapse the character advance widths
					of any that would otherwise overflow.

					<wpt>
					white-space/pre-wrap-001.html
					white-space/pre-wrap-002.html
					white-space/pre-wrap-003.html
					white-space/pre-wrap-004.html
					white-space/pre-wrap-005.html
					white-space/pre-wrap-006.html
					white-space/pre-wrap-007.html
					white-space/pre-wrap-011.html
					white-space/pre-wrap-012.html
					white-space/pre-wrap-013.html
					white-space/pre-wrap-014.html
					white-space/pre-wrap-017.html
					white-space/pre-wrap-018.html
					white-space/pre-wrap-019.html
					white-space/pre-wrap-020.html
					white-space/textarea-pre-wrap-001.html
					white-space/textarea-pre-wrap-002.html
					white-space/textarea-pre-wrap-003.html
					white-space/textarea-pre-wrap-004.html
					white-space/textarea-pre-wrap-005.html
					white-space/textarea-pre-wrap-006.html
					white-space/textarea-pre-wrap-007.html
					white-space/textarea-pre-wrap-011.html
					white-space/textarea-pre-wrap-012.html
					white-space/textarea-pre-wrap-013.html
					white-space/textarea-pre-wrap-014.html
					white-space/trailing-ideographic-space-003.html
					white-space/trailing-ideographic-space-004.html
					white-space/white-space-pre-wrap-trailing-spaces-001.html
					white-space/white-space-pre-wrap-trailing-spaces-002.html
					white-space/white-space-pre-wrap-trailing-spaces-003.html
					white-space/white-space-pre-wrap-trailing-spaces-004.html
					white-space/white-space-pre-wrap-trailing-spaces-005.html
					white-space/white-space-pre-wrap-trailing-spaces-006.html
					white-space/white-space-pre-wrap-trailing-spaces-007.html
					white-space/white-space-pre-wrap-trailing-spaces-008.html
					white-space/white-space-pre-wrap-trailing-spaces-010.html
					white-space/white-space-pre-wrap-trailing-spaces-011.html
					white-space/white-space-pre-wrap-trailing-spaces-012.html
					white-space/white-space-pre-wrap-trailing-spaces-013.html
					white-space/white-space-pre-wrap-trailing-spaces-014.html
					white-space/white-space-pre-wrap-trailing-spaces-015.html
					white-space/white-space-intrinsic-size-003.html
					white-space/white-space-intrinsic-size-004.html
					white-space/pre-wrap-tab-005.html
					white-space/pre-wrap-tab-006.html
					white-space/trailing-other-space-separators-002.html
					text-transform/text-transform-fullwidth-009.html
					white-space/trailing-space-position-001.html
					line-break/line-break-anywhere-and-white-space-006.html
					line-break/line-break-anywhere-and-white-space-007.html
					white-space/white-space-intrinsic-size-013.html
					white-space/white-space-intrinsic-size-014.html
					white-space/white-space-intrinsic-size-017.html
					white-space/eol-spaces-bidi-002.html
					white-space/trailing-space-in-inline-box.html
					</wpt>

					Note: [=Hanging=] the white space rather than collapsing it
					allows users to see the space when selecting or editing text.

				<li>
					If 'white-space' is set to ''break-spaces'',
					[=spaces=], [=tabs=], and [=other space separators=]
					are treated the same as other visible characters:
					they cannot [=hang=] nor have their advance width collapsed.

					<wpt>
					white-space/break-spaces-001.html
					white-space/break-spaces-005.html
					white-space/textarea-break-spaces-001.html
					white-space/break-spaces-tab-005.html
					white-space/break-spaces-tab-006.html
					white-space/trailing-other-space-separators-break-spaces-001.html
					white-space/trailing-other-space-separators-break-spaces-002.html
					white-space/trailing-other-space-separators-break-spaces-003.html
					white-space/trailing-other-space-separators-break-spaces-004.html
					white-space/trailing-other-space-separators-break-spaces-005.html
					white-space/trailing-other-space-separators-break-spaces-006.html
					white-space/trailing-other-space-separators-break-spaces-007.html
					white-space/trailing-other-space-separators-break-spaces-008.html
					white-space/trailing-other-space-separators-break-spaces-009.html
					white-space/trailing-other-space-separators-break-spaces-010.html
					white-space/trailing-other-space-separators-break-spaces-011.html
					white-space/trailing-other-space-separators-break-spaces-012.html
					white-space/trailing-other-space-separators-break-spaces-013.html
					white-space/trailing-other-space-separators-break-spaces-014.html
					white-space/trailing-other-space-separators-break-spaces-015.html
					line-break/line-break-anywhere-and-white-space-008.html
					line-break/line-break-anywhere-and-white-space-009.html
					white-space/break-spaces-with-ideographic-space-001.html
					white-space/break-spaces-with-ideographic-space-001.html
					white-space/break-spaces-with-ideographic-space-005.html
					white-space/break-spaces-with-ideographic-space-007.html
					white-space/break-spaces-with-ideographic-space-008.html
					white-space/break-spaces-with-ideographic-space-009.html
					white-space/break-spaces-with-ideographic-space-010.html
					white-space/trailing-ideographic-space-break-spaces-001.html
					white-space/trailing-ideographic-space-break-spaces-002.html
					white-space/trailing-ideographic-space-break-spaces-003.html
					white-space/trailing-ideographic-space-break-spaces-004.html
					white-space/trailing-ideographic-space-break-spaces-005.html
					white-space/trailing-ideographic-space-break-spaces-006.html
					white-space/trailing-ideographic-space-break-spaces-007.html
					white-space/trailing-ideographic-space-break-spaces-008.html
					</wpt>

					Note: Such characters therefore take up space,
					and depending on the available space
					and applicable line breaking controls
					will either overflow or cause the line to wrap.
			</ul>

	</ol>

	<div class=example>
		This example shows that [=conditionally hanging=] white space
		at the end of lines with forced breaks
		provides symmetry with the start of the line.
		An underline is added to help visualize the spaces.

		<pre><code highlight=css>
			p {
				white-space: pre-wrap;
				width: 5ch;
				border: solid 1px;
				font-family: monospace;
				text-align: center;
			}
		</code></pre>

		<xmp highlight=html>
			<p> 0 </p>
		</xmp>

		The sample above would be rendered as follows:
		<div style="word-wrap: normal; font-size: 2em; font-family: monospace; width: 5ch; border: solid 1px; white-space: pre;"> <span style="text-decoration: underline; text-decoration: underline orange"> 0 </span> </div>

		Since the final [=space=] is before a forced line break
		and does not overflow,
		it does not hang,
		and centering works as expected.
	</div>

	<div class=example>
		This example illustrates the difference
		between [=hanging=] [=spaces=]
		at the end of lines without forced breaks,
		and [=conditionally hanging=] them at the end of lines with forced breaks.
		An underline is added to help visualize the [=spaces=].

		<pre><code highlight=css>
			p {
				white-space: pre-wrap;
				width: 3ch;
				border: solid 1px;
				font-family: monospace;
			}
		</code></pre>

		<xmp highlight=html>
			<p> 0 0 0 0 </p>
		</xmp>

		The sample above would be rendered as follows:
		<div style="word-wrap: normal; font-size: 2em; font-family: monospace; width: 3ch; border: solid 1px; white-space: pre; text-decoration: underline; text-decoration: underline orange"> 0 <br>0 0 <br>0 </div>

		If <code highlight=css>p { text-align: right; }</code> was added,
		the result would be as follows:

		<div style="word-wrap: normal; font-size: 2em; font-family: monospace; width: 3ch; border: solid 1px; white-space: pre;"> <span style="text-decoration: underline; text-decoration: underline orange"> 0 </span><br><span style="text-decoration: underline; text-decoration: underline orange">0 0 </span><br> <span style="text-decoration: underline; text-decoration: underline orange">0 </span></div>

		As the [=preserved=] [=spaces=] at the end of lines without a forced break must [=hang=],
		they are not considered when placing the rest of the line during text alignment.
		When aligning towards the end,
		this means any such [=spaces=] will overflow,
		and will not prevent the rest of the line’s content from being flush with the edge of the line.
		On the other hand,
		preserved spaces at the end of a line <em>with</em> a forced break
		[=conditionally hang=].
		Since the space at the end of the last line would not overflow in this example,
		it does not [=hang=]
		and therefore is considered during text alignment.
	</div>

	<div class=example>
		In the following example,
		there is not enough room on any line to fit the end-of-line spaces,
		so they [=hang=] on all lines:
		the one on the line without a forced break because it must,
		as well as the one on the line with a forced break,
		because it [=conditionally hangs=] and overflows.
		An underline is added to help visualize the spaces.

		<pre><code highlight=css>
			p {
				white-space: pre-wrap;
				width: 3ch;
				border: solid 1px;
				font-family: monospace;
			}
		</code></pre>

		<xmp highlight=html>
			<p>0 0 0 0 </p>
		</xmp>

		<div style="word-wrap: normal; font-size: 2em; font-family: monospace; width: 3ch; border: solid 1px; white-space: pre; text-decoration: underline; text-decoration: underline orange">0 0 <br>0 0 </div>

		The last line is not wrapped before the last <code>0</code>
		because characters that [=conditionally hang=] are not considered
		when measuring the line’s contents for fit.
	</div>


<h4 id="line-break-transform">
Segment Break Transformation Rules</h4>

	<wpt title="
		This section has reasonable test coverage,
		though some assertions are only tested indirectly through
		test for other features that rely on this,
		rather than by dedicated tests."></wpt>

	When 'white-space' is ''pre'', ''pre-wrap'', ''break-spaces'', or ''pre-line'',
	[=segment breaks=] are not [=collapsible=]
	and are instead transformed into a preserved line feed (U+000A).

	<wpt pathprefix="/css/CSS2/text/">
	white-space-008.xht
	white-space-processing-016.xht
	white-space-processing-017.xht
	white-space-processing-018.xht
	</wpt>

	For other values of 'white-space',
	[=segment breaks=] are [=collapsible=],
	and are collapsed as follows:

	<ol>
		<li>
			First, any collapsible [=segment break=]
			immediately following another collapsible [=segment break=]
			is removed.

		<li>
			Then any remaining [=segment break=]
			is either transformed into a space (U+0020)
			or removed
			depending on the context before and after the break.
			The rules for this operation are UA-defined in this level.

<!-- CUT SEGMENT BREAK TRANSFORM
			<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
			segment-break-transformation-removable-2.html
			segment-break-transformation-removable-4.html
			</wpt>
			<wpt>
			white-space/seg-break-transformation-000.html
			</wpt>

			<ul>
			<li>
				If the character immediately before or immediately after the [=segment break=]
				is the zero-width space character (U+200B), then the break
				is removed, leaving behind the zero-width space.

				<wpt>
				white-space/seg-break-transformation-016.html
				white-space/seg-break-transformation-017.html
				white-space/seg-break-transformation-018.html
				white-space/seg-break-transformation-019.html
				</wpt>

				<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
				segment-break-transformation-removable-1.html
				segment-break-transformation-removable-3.html
				</wpt>

			<li>
				Otherwise,
				if both the characters before and after the [=segment break=]
				belong to the [=space-discarding character set=]
				(see [[#space-discard-set]]),
				then the [=segment break=] is removed.

			<li>
				Otherwise,
				if the [=East Asian Width property=]
				of both the character before and after the [=segment break=]
				is <code>Fullwidth</code>,
				<code>Wide</code>,
				or <code>Halfwidth</code>
				(not <code>Ambiguous</code>),
				and neither side is Hangul,
				then the [=segment break=] is removed.
				[[!UAX11]]

				<wpt>
				white-space/seg-break-transformation-001.html
				white-space/seg-break-transformation-002.html
				white-space/seg-break-transformation-003.html
				white-space/seg-break-transformation-004.html
				white-space/seg-break-transformation-005.html
				white-space/seg-break-transformation-006.html
				white-space/seg-break-transformation-007.html
				white-space/seg-break-transformation-008.html
				white-space/seg-break-transformation-009.html
				white-space/seg-break-transformation-010.html
				white-space/seg-break-transformation-011.html
				white-space/seg-break-transformation-012.html
				white-space/seg-break-transformation-014.html
				white-space/seg-break-transformation-015.html
				</wpt>

				<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
				segment-break-transformation-rules-001.html
				segment-break-transformation-rules-002.html
				segment-break-transformation-rules-003.html
				segment-break-transformation-rules-004.html
				segment-break-transformation-rules-005.html
				segment-break-transformation-rules-006.html
				segment-break-transformation-rules-007.html
				segment-break-transformation-rules-008.html
				segment-break-transformation-rules-009.html
				segment-break-transformation-rules-010.html
				segment-break-transformation-rules-011.html
				segment-break-transformation-rules-012.html
				segment-break-transformation-rules-013.html
				segment-break-transformation-rules-014.html
				segment-break-transformation-rules-015.html
				segment-break-transformation-rules-016.html
				segment-break-transformation-rules-017.html
				segment-break-transformation-rules-018.html
				segment-break-transformation-rules-019.html
				segment-break-transformation-rules-020.html
				segment-break-transformation-rules-021.html
				segment-break-transformation-rules-022.html
				segment-break-transformation-rules-023.html
				segment-break-transformation-rules-024.html
				segment-break-transformation-rules-025.html
				segment-break-transformation-rules-026.html
				segment-break-transformation-rules-027.html
				segment-break-transformation-rules-028.html
				segment-break-transformation-rules-029.html
				segment-break-transformation-rules-030.html
				segment-break-transformation-rules-031.html
				segment-break-transformation-rules-032.html
				segment-break-transformation-rules-033.html
				segment-break-transformation-rules-034.html
				segment-break-transformation-rules-035.html
				segment-break-transformation-rules-036.html
				segment-break-transformation-rules-037.html
				segment-break-transformation-rules-038.html
				segment-break-transformation-rules-039.html
				segment-break-transformation-rules-040.html
				segment-break-transformation-rules-041.html
				segment-break-transformation-rules-042.html
				segment-break-transformation-rules-043.html
				segment-break-transformation-rules-044.html
				segment-break-transformation-rules-045.html
				segment-break-transformation-rules-046.html
				segment-break-transformation-rules-047.html
				segment-break-transformation-rules-048.html
				segment-break-transformation-rules-049.html
				</wpt>

			<li>
				Otherwise,
				if the <a>writing system</a> of the <a>segment break</a> is
				<a for=writing-system>Chinese</a>,
				<a for=writing-system>Japanese</a>,
				or Yi,
				and the character before or after the [=segment break=]
				is punctuation or a symbol (Unicode [=general category=] P* or S*)
				and has an [=East Asian Width property=] of <code>Ambiguous</code>,
				and the character on the other side of the [=segment break=] is
				<code>Fullwidth</code>,
				<code>Wide</code>,
				or <code>Halfwidth</code>,
				and not Hangul,
				then the [=segment break=] is removed.

				<wpt>
				writing-system/writing-system-segment-break-001.html
				</wpt>

			<li>
				Otherwise, the [=segment break=] is converted to a space (U+0020).

				<wpt>
				white-space/seg-break-transformation-000.html
				</wpt>

				<wpt pathprefix="/css/CSS2/text/">
				white-space-processing-005.xht
				white-space-processing-014.xht
				white-space-processing-015.xht
				</wpt>

		</ul>

		For this purpose,
		Emoji (Unicode property <code>Emoji</code>)
		with an [=East Asian Width property=] of
		<code>Wide</code> or <code>Neutral</code>
		are treated as having an [=East Asian Width property=] of
		<code>Ambiguous</code>.


		ISSUE(5086): Should space-discarding punctuation have a stronger influence over mismatched before/after contexts?

		ISSUE(5017): Should we classify punctuation and/or symbols as a category of space-ambiguous characters? (Currently spaces are discarded only if both sides are space-discarding; ambiguous characters would defer to the other side.)

CUT SEGMENT BREAK TRANSFORM -->

		Note: The white space processing rules have already
		removed any [=tabs=] and [=spaces=] around the [=segment break=]
		before this context is evaluated.
	</ol>

	<div class="example">
		The purpose of the segment break transformation rules
		(and white space collapsing in general)
		is to “unbreak” text that has been
		[[#white-space-processing|broken into segments]]
		to make the document source code easier to work with.
		In languages that use word separators, such as English and Korean,
		“unbreaking” a line requires joining the two lines with a [=space=].

		<figure>
			<pre>
				Here is an English paragraph
				that is broken into multiple lines
				in the source code so that it can
				be more easily read and edited
				in a text editor.
			</pre>

			Here is an English paragraph that is broken into multiple lines in the source code so that it can be more easily read and edited in a text editor.

			<figcaption>
				Eliminating a line break in English
				requires maintaining a [=space=] in its place.
			</figcaption>
		</figure>

		In languages that have no word separators, such as Chinese,
		“unbreaking” a line requires joining the two lines with no intervening space.

		<figure>
			<pre lang="zh-Hant">
				這個段落是那麼長，
				在一行寫不行。最好
				用三行寫。
			</pre>

			<p lang="zh-Hant">這個段落是那麼長，在一行寫不行。最好用三行寫。

			<figcaption>
				Eliminating a line break in Chinese
				requires eliminating any intervening [=white space=].
			</figcaption>
		</figure>

		The segment break transformation rules can use adjacent context
		to either transform the segment break into a space
		or eliminate it entirely.
	</div>

	Note: Historically, HTML and CSS have unconditionally converted [=segment breaks=] to spaces,
	which has prevented content authored in languages such as Chinese
	from being able to break lines within the source.
	Thus UA heuristics need to be conservative about where they discard [=segment breaks=]
	even as they strive to improve support for such languages.

<h3 id="tab-size-property" caniuse="css3-tabsize" oldids="tab-size">
Tab Character Size: the 'tab-size' property</h3>

	<wpt title="This section has good test coverage."></wpt>

	<pre class="propdef">
	Name: tab-size
	Value: <<number>> | <<length>>
	Initial: 8
	Applies to: text
	Inherited: yes
	Computed value: the specified number or absolute length
	Animation type: by computed value type
	Canonical order: n/a
	</pre>

	<wpt>
	tab-size/tab-size-integer-001.html
	tab-size/tab-size.html
	tab-size/tab-size-inheritance-001.html
	inheritance.html
	parsing/tab-size-valid.html
	parsing/tab-size-invalid.html
	parsing/tab-size-computed.html
	tab-size/tab-size-computed-value-001.html
	tab-size/tab-size-inline-001.html
	animations/tab-size-interpolation.html
	</wpt>

	This property determines the <dfn id=tab-size-dfn>tab size</dfn>
	used to render [=preserved=] tab characters (U+0009).
	A <<number>> represents the measure
	as a multiple of the advance width of the space character (U+0020)
	of the nearest [=block container=] ancestor of the [=preserved=] [=tab=],
	including its associated 'letter-spacing' and 'word-spacing'.
	Negative values are not allowed.

	<wpt>
	tab-size/tab-size-integer-001.html
	tab-size/tab-size-integer-002.html
	tab-size/tab-size-integer-003.html
	tab-size/tab-size-integer-004.html
	tab-size/tab-size-length-001.html
	tab-size/tab-size-length-002.html
	tab-size/tab-size-percent-001.html
	tab-size/tab-min-rendered-width-1.html
	tab-size/tab-size-spacing-001.html
	white-space/tab-stop-threshold-001.html
	white-space/tab-stop-threshold-002.html
	white-space/tab-stop-threshold-003.html
	white-space/tab-stop-threshold-004.html
	white-space/tab-stop-threshold-005.html
	white-space/tab-stop-threshold-006.html
	text-indent/text-indent-tab-positions-001.html
	</wpt>

	<wpt pathprefix="/css/CSS2/text/">
	white-space-processing-042.xht
	</wpt>

<h2 id="line-breaking">
Line Breaking and Word Boundaries</h2>

	<wpt title="
		Tests mostly not needed for this section:
		these are definitions,
		they get tested through their application,
		not by themselves.

		Can be a good section
		to host tests for i18n requirements
		not covered in detail by the spec.

		Possible additions:
		* Basic line breaking tests for any language mentioned (Thai, Lao, Khmer, Javanese, Balinese, Yi…)"></wpt>

	When inline-level content is laid out into lines, it is broken across line boxes.
	Such a break is called a <dfn export>line break</dfn>.
	When a line is broken due to explicit line-breaking controls
	(such as a <a>preserved</a> newline character),
	or due to the start or end of a block,
	it is a <dfn export>forced line break</dfn>.
	When a line is broken due to content <dfn lt="wrapping|wrap">wrapping</dfn>
	(i.e. when the UA creates unforced line breaks
	in order to fit the content within the measure),
	it is a <dfn>soft wrap break</dfn>.
	The process of breaking inline-level content into lines is called <dfn export lt="line breaking process | line breaking">line breaking</dfn>.

	Wrapping is only performed at an allowed break point,
	called a <dfn export>soft wrap opportunity</dfn>.
	When wrapping is enabled (see 'white-space'),
	the UA must minimize the amount of content overflowing a line
	by wrapping the line at a [=soft wrap opportunity=],
	if one exists.

	<wpt>
	line-breaking/line-breaking-020.html
	</wpt>

	In most writing systems,
	in the absence of hyphenation a [=soft wrap opportunity=] occurs only at word boundaries.
	Many such systems use [=spaces=] or punctuation to explicitly separate words,
	and [=soft wrap opportunities=] can be identified by these characters.
	Scripts such as Thai, Lao, and Khmer, however,
	do not use spaces or punctuation to separate words.
	Although the zero width space (U+200B) can be used as an explicit word delimiter
	in these scripts,
	this practice is not common.
	As a result, a lexical resource is needed
	to correctly identify [=soft wrap opportunities=] in such texts.

	In some other writing systems,
	[=soft wrap opportunities=] are based on orthographic syllable boundaries,
	not word boundaries.
	Some of these systems, such as Javanese and Balinese,
	are similar to Thai and Lao in that they
	require analysis of the text to find breaking opportunities.
	In others such as Chinese (as well as Japanese, Yi, and sometimes also Korean),
	each syllable tends to correspond to a single [=typographic letter unit=],
	and thus line breaking conventions allow the line to break
	anywhere <em>except</em> between certain character combinations.
	Additionally the level of strictness in these restrictions
	varies with the typesetting style.

	<wpt>
	i18n/css3-text-line-break-baspglwj-003.html
	i18n/css3-text-line-break-baspglwj-004.html
	i18n/css3-text-line-break-baspglwj-005.html
	i18n/css3-text-line-break-baspglwj-006.html
	i18n/css3-text-line-break-baspglwj-007.html
	i18n/css3-text-line-break-baspglwj-008.html
	i18n/css3-text-line-break-baspglwj-009.html
	i18n/css3-text-line-break-baspglwj-010.html
	i18n/css3-text-line-break-baspglwj-011.html
	i18n/css3-text-line-break-baspglwj-012.html
	i18n/css3-text-line-break-baspglwj-014.html
	i18n/css3-text-line-break-baspglwj-015.html
	i18n/css3-text-line-break-baspglwj-016.html
	i18n/css3-text-line-break-baspglwj-017.html
	i18n/css3-text-line-break-baspglwj-018.html
	i18n/css3-text-line-break-baspglwj-019.html
	i18n/css3-text-line-break-baspglwj-020.html
	i18n/css3-text-line-break-baspglwj-021.html
	i18n/css3-text-line-break-baspglwj-022.html
	i18n/css3-text-line-break-baspglwj-023.html
	i18n/css3-text-line-break-baspglwj-024.html
	i18n/css3-text-line-break-baspglwj-025.html
	i18n/css3-text-line-break-baspglwj-026.html
	i18n/css3-text-line-break-baspglwj-030.html
	i18n/css3-text-line-break-baspglwj-031.html
	i18n/css3-text-line-break-baspglwj-032.html
	i18n/css3-text-line-break-baspglwj-033.html
	i18n/css3-text-line-break-baspglwj-034.html
	i18n/css3-text-line-break-baspglwj-035.html
	i18n/css3-text-line-break-baspglwj-036.html
	i18n/css3-text-line-break-baspglwj-037.html
	i18n/css3-text-line-break-baspglwj-038.html
	i18n/css3-text-line-break-baspglwj-039.html
	i18n/css3-text-line-break-baspglwj-040.html
	i18n/css3-text-line-break-baspglwj-041.html
	i18n/css3-text-line-break-baspglwj-042.html
	i18n/css3-text-line-break-baspglwj-043.html
	i18n/css3-text-line-break-baspglwj-044.html
	i18n/css3-text-line-break-baspglwj-045.html
	i18n/css3-text-line-break-baspglwj-046.html
	i18n/css3-text-line-break-baspglwj-047.html
	i18n/css3-text-line-break-baspglwj-048.html
	i18n/css3-text-line-break-baspglwj-049.html
	i18n/css3-text-line-break-baspglwj-050.html
	i18n/css3-text-line-break-baspglwj-051.html
	i18n/css3-text-line-break-baspglwj-052.html
	i18n/css3-text-line-break-baspglwj-060.html
	i18n/css3-text-line-break-baspglwj-061.html
	i18n/css3-text-line-break-baspglwj-062.html
	i18n/css3-text-line-break-baspglwj-063.html
	i18n/css3-text-line-break-baspglwj-064.html
	i18n/css3-text-line-break-baspglwj-065.html
	i18n/css3-text-line-break-baspglwj-066.html
	i18n/css3-text-line-break-baspglwj-067.html
	i18n/css3-text-line-break-baspglwj-068.html
	i18n/css3-text-line-break-baspglwj-069.html
	i18n/css3-text-line-break-baspglwj-070.html
	i18n/css3-text-line-break-baspglwj-071.html
	i18n/css3-text-line-break-baspglwj-072.html
	i18n/css3-text-line-break-baspglwj-073.html
	i18n/css3-text-line-break-baspglwj-074.html
	i18n/css3-text-line-break-baspglwj-075.html
	i18n/css3-text-line-break-baspglwj-076.html
	i18n/css3-text-line-break-baspglwj-077.html
	i18n/css3-text-line-break-baspglwj-078.html
	i18n/css3-text-line-break-baspglwj-080.html
	i18n/css3-text-line-break-baspglwj-081.html
	i18n/css3-text-line-break-baspglwj-082.html
	i18n/css3-text-line-break-baspglwj-083.html
	i18n/css3-text-line-break-baspglwj-084.html
	i18n/css3-text-line-break-baspglwj-085.html
	i18n/css3-text-line-break-baspglwj-086.html
	i18n/css3-text-line-break-baspglwj-090.html
	i18n/css3-text-line-break-baspglwj-091.html
	i18n/css3-text-line-break-baspglwj-092.html
	i18n/css3-text-line-break-baspglwj-093.html
	i18n/css3-text-line-break-baspglwj-095.html
	i18n/css3-text-line-break-baspglwj-096.html
	i18n/css3-text-line-break-baspglwj-097.html
	i18n/css3-text-line-break-baspglwj-098.html
	i18n/css3-text-line-break-baspglwj-099.html
	i18n/css3-text-line-break-baspglwj-100.html
	i18n/css3-text-line-break-baspglwj-101.html
	i18n/css3-text-line-break-baspglwj-102.html
	i18n/css3-text-line-break-baspglwj-103.html
	i18n/css3-text-line-break-baspglwj-104.html
	i18n/css3-text-line-break-baspglwj-105.html
	i18n/css3-text-line-break-baspglwj-106.html
	i18n/css3-text-line-break-baspglwj-107.html
	i18n/css3-text-line-break-baspglwj-108.html
	i18n/css3-text-line-break-baspglwj-109.html
	i18n/css3-text-line-break-baspglwj-110.html
	i18n/css3-text-line-break-baspglwj-111.html
	i18n/css3-text-line-break-baspglwj-112.html
	i18n/css3-text-line-break-baspglwj-113.html
	i18n/css3-text-line-break-baspglwj-114.html
	i18n/css3-text-line-break-baspglwj-115.html
	i18n/css3-text-line-break-baspglwj-116.html
	i18n/css3-text-line-break-baspglwj-117.html
	i18n/css3-text-line-break-baspglwj-118.html
	i18n/css3-text-line-break-opclns-001.html
	i18n/css3-text-line-break-opclns-002.html
	i18n/css3-text-line-break-opclns-003.html
	i18n/css3-text-line-break-opclns-004.html
	i18n/css3-text-line-break-opclns-005.html
	i18n/css3-text-line-break-opclns-006.html
	i18n/css3-text-line-break-opclns-007.html
	i18n/css3-text-line-break-opclns-008.html
	i18n/css3-text-line-break-opclns-009.html
	i18n/css3-text-line-break-opclns-010.html
	i18n/css3-text-line-break-opclns-011.html
	i18n/css3-text-line-break-opclns-012.html
	i18n/css3-text-line-break-opclns-014.html
	i18n/css3-text-line-break-opclns-015.html
	i18n/css3-text-line-break-opclns-016.html
	i18n/css3-text-line-break-opclns-017.html
	i18n/css3-text-line-break-opclns-018.html
	i18n/css3-text-line-break-opclns-019.html
	i18n/css3-text-line-break-opclns-020.html
	i18n/css3-text-line-break-opclns-021.html
	i18n/css3-text-line-break-opclns-022.html
	i18n/css3-text-line-break-opclns-023.html
	i18n/css3-text-line-break-opclns-024.html
	i18n/css3-text-line-break-opclns-025.html
	i18n/css3-text-line-break-opclns-026.html
	i18n/css3-text-line-break-opclns-027.html
	i18n/css3-text-line-break-opclns-028.html
	i18n/css3-text-line-break-opclns-029.html
	i18n/css3-text-line-break-opclns-030.html
	i18n/css3-text-line-break-opclns-031.html
	i18n/css3-text-line-break-opclns-032.html
	i18n/css3-text-line-break-opclns-033.html
	i18n/css3-text-line-break-opclns-034.html
	i18n/css3-text-line-break-opclns-035.html
	i18n/css3-text-line-break-opclns-036.html
	i18n/css3-text-line-break-opclns-037.html
	i18n/css3-text-line-break-opclns-038.html
	i18n/css3-text-line-break-opclns-039.html
	i18n/css3-text-line-break-opclns-040.html
	i18n/css3-text-line-break-opclns-041.html
	i18n/css3-text-line-break-opclns-042.html
	i18n/css3-text-line-break-opclns-043.html
	i18n/css3-text-line-break-opclns-044.html
	i18n/css3-text-line-break-opclns-045.html
	i18n/css3-text-line-break-opclns-046.html
	i18n/css3-text-line-break-opclns-047.html
	i18n/css3-text-line-break-opclns-049.html
	i18n/css3-text-line-break-opclns-050.html
	i18n/css3-text-line-break-opclns-051.html
	i18n/css3-text-line-break-opclns-052.html
	i18n/css3-text-line-break-opclns-053.html
	i18n/css3-text-line-break-opclns-054.html
	i18n/css3-text-line-break-opclns-055.html
	i18n/css3-text-line-break-opclns-056.html
	i18n/css3-text-line-break-opclns-057.html
	i18n/css3-text-line-break-opclns-058.html
	i18n/css3-text-line-break-opclns-059.html
	i18n/css3-text-line-break-opclns-060.html
	i18n/css3-text-line-break-opclns-061.html
	i18n/css3-text-line-break-opclns-062.html
	i18n/css3-text-line-break-opclns-063.html
	i18n/css3-text-line-break-opclns-064.html
	i18n/css3-text-line-break-opclns-065.html
	i18n/css3-text-line-break-opclns-100.html
	i18n/css3-text-line-break-opclns-101.html
	i18n/css3-text-line-break-opclns-102.html
	i18n/css3-text-line-break-opclns-103.html
	i18n/css3-text-line-break-opclns-104.html
	i18n/css3-text-line-break-opclns-105.html
	i18n/css3-text-line-break-opclns-106.html
	i18n/css3-text-line-break-opclns-107.html
	i18n/css3-text-line-break-opclns-108.html
	i18n/css3-text-line-break-opclns-109.html
	i18n/css3-text-line-break-opclns-110.html
	i18n/css3-text-line-break-opclns-111.html
	i18n/css3-text-line-break-opclns-112.html
	i18n/css3-text-line-break-opclns-113.html
	i18n/css3-text-line-break-opclns-114.html
	i18n/css3-text-line-break-opclns-115.html
	i18n/css3-text-line-break-opclns-116.html
	i18n/css3-text-line-break-opclns-117.html
	i18n/css3-text-line-break-opclns-119.html
	i18n/css3-text-line-break-opclns-120.html
	i18n/css3-text-line-break-opclns-121.html
	i18n/css3-text-line-break-opclns-122.html
	i18n/css3-text-line-break-opclns-123.html
	i18n/css3-text-line-break-opclns-124.html
	i18n/css3-text-line-break-opclns-125.html
	i18n/css3-text-line-break-opclns-126.html
	i18n/css3-text-line-break-opclns-127.html
	i18n/css3-text-line-break-opclns-128.html
	i18n/css3-text-line-break-opclns-129.html
	i18n/css3-text-line-break-opclns-130.html
	i18n/css3-text-line-break-opclns-131.html
	i18n/css3-text-line-break-opclns-132.html
	i18n/css3-text-line-break-opclns-133.html
	i18n/css3-text-line-break-opclns-134.html
	i18n/css3-text-line-break-opclns-135.html
	i18n/css3-text-line-break-opclns-136.html
	i18n/css3-text-line-break-opclns-137.html
	i18n/css3-text-line-break-opclns-138.html
	i18n/css3-text-line-break-opclns-139.html
	i18n/css3-text-line-break-opclns-140.html
	i18n/css3-text-line-break-opclns-141.html
	i18n/css3-text-line-break-opclns-142.html
	i18n/css3-text-line-break-opclns-143.html
	i18n/css3-text-line-break-opclns-144.html
	i18n/css3-text-line-break-opclns-145.html
	i18n/css3-text-line-break-opclns-146.html
	i18n/css3-text-line-break-opclns-147.html
	i18n/css3-text-line-break-opclns-148.html
	i18n/css3-text-line-break-opclns-149.html
	i18n/css3-text-line-break-opclns-150.html
	i18n/css3-text-line-break-opclns-151.html
	i18n/css3-text-line-break-opclns-152.html
	i18n/css3-text-line-break-opclns-153.html
	i18n/css3-text-line-break-opclns-155.html
	i18n/css3-text-line-break-opclns-156.html
	i18n/css3-text-line-break-opclns-157.html
	i18n/css3-text-line-break-opclns-158.html
	i18n/css3-text-line-break-opclns-159.html
	i18n/css3-text-line-break-opclns-160.html
	i18n/css3-text-line-break-opclns-161.html
	i18n/css3-text-line-break-opclns-162.html
	i18n/css3-text-line-break-opclns-163.html
	i18n/css3-text-line-break-opclns-164.html
	i18n/css3-text-line-break-opclns-165.html
	i18n/css3-text-line-break-opclns-166.html
	i18n/css3-text-line-break-opclns-167.html
	i18n/css3-text-line-break-opclns-168.html
	i18n/css3-text-line-break-opclns-169.html
	i18n/css3-text-line-break-opclns-170.html
	i18n/css3-text-line-break-opclns-171.html
	i18n/css3-text-line-break-opclns-200.html
	i18n/css3-text-line-break-opclns-201.html
	i18n/css3-text-line-break-opclns-202.html
	i18n/css3-text-line-break-opclns-203.html
	i18n/css3-text-line-break-opclns-204.html
	i18n/css3-text-line-break-opclns-205.html
	i18n/css3-text-line-break-opclns-206.html
	i18n/css3-text-line-break-opclns-207.html
	i18n/css3-text-line-break-opclns-208.html
	i18n/css3-text-line-break-opclns-209.html
	i18n/css3-text-line-break-opclns-210.html
	i18n/css3-text-line-break-opclns-211.html
	i18n/css3-text-line-break-opclns-212.html
	i18n/css3-text-line-break-opclns-213.html
	i18n/css3-text-line-break-opclns-214.html
	i18n/css3-text-line-break-opclns-215.html
	i18n/css3-text-line-break-opclns-217.html
	i18n/css3-text-line-break-opclns-218.html
	i18n/css3-text-line-break-opclns-219.html
	i18n/css3-text-line-break-opclns-220.html
	i18n/css3-text-line-break-opclns-221.html
	i18n/css3-text-line-break-opclns-222.html
	i18n/css3-text-line-break-opclns-223.html
	i18n/css3-text-line-break-opclns-225.html
	i18n/css3-text-line-break-opclns-226.html
	</wpt>

	While CSS does not fully define where [=soft wrap opportunities=] occur,
    some controls are provided to distinguish common variations:

	<ul>
		<li>
			The 'line-break' property allows choosing various levels of “strictness”
			for line breaking restrictions.
		<li>
			The 'word-break' property controls what types of letters
			are glommed together to form unbreakable “words”,
			causing CJK characters to behave like non-CJK text or vice versa.
		<li>
			The 'hyphens' property controls whether automatic hyphenation
			is allowed to break words in scripts that hyphenate.
		<li>
			The 'overflow-wrap' property allows the UA to take a break anywhere
			in otherwise-unbreakable strings that would otherwise overflow.
	</ul>

	Note: <a href="https://www.unicode.org/reports/tr14/"><cite>Unicode Standard Annex #14: Unicode Line Breaking Algorithm</cite></a>
	defines a baseline behavior
	for line breaking for all scripts in Unicode,
	which is expected to be further tailored.
	[[UAX14]]
	More information on line breaking conventions
	can be found in <a href="https://www.w3.org/TR/jlreq/"><cite>Requirements for Japanese Text Layout</cite></a> [[JLREQ]]
	and <cite>Formatting Rules for Japanese Documents</cite> [[JIS4051]] for Japanese,
	<a href="https://www.w3.org/TR/clreq/"><cite>Requirements for Chinese Text Layout</cite></a> [[CLREQ]]
	and <cite>General Rules for Punctuation</cite> [[ZHMARK]] for Chinese.
	See also the
	<a href="https://www.w3.org/International/">Internationalization Working Group</a>’s
	<a href="https://www.w3.org/TR/typography/#blocks_paragraphs">Language Enablement Index</a>
	which includes more information on additional languages.
	[[TYPOGRAPHY]]
	Any guidance on additional appropriate references
	would be much appreciated.

<h3 id="line-break-details">
Line Breaking Details</h3>

	<wpt title="
		This section has partial test coverage.

		Missing tests:

		* “Regardless of the white-space value […] the BK, NL […] classes […] must be honored”
		* For soft wrap opportunities before the first or after the last character of a box, the break occurs immediately before/after the box (at its margin edge) rather than breaking the box between its content edge and the content.
		* Test for <a href=https://github.com/w3c/csswg-drafts/issues/4284>https://github.com/w3c/csswg-drafts/issues/4284</a>

		Untestable(?):

		* UAs that allow wrapping at punctuation other than spaces should prioritize breakpoints. […]"></wpt>

	When determining [=line breaks=]:

	<ul>
		<li>
			The interaction of [=line breaking=] and bidirectional text is defined by
			[[css-writing-modes-4#bidi-algo]]
			and the <cite>Unicode Bidirectional Algorithm</cite>
			(<a href="http://unicode.org/reports/tr9/#Reordering_Resolved_Levels">UAX9&sect;3.4 Reordering Resolved Levels</a> in particular).
			[[!CSS-WRITING-MODES-4]]
			[[!UAX9]]

			<wpt pathprefix="/css/CSS2/bidi-text/">
			bidi-breaking-001.xht
			bidi-breaking-002.xht
			bidi-breaking-003.xht
			</wpt>

		<li>
			Regardless of the 'white-space' value,
			lines always break at each [=preserved=] forced break character:
			thus for all values,
			line-breaking behavior defined for
			the <code>BK</code> and <code>NL</code> Unicode line breaking classes
			must be honored.
			[[!UAX14]]

			Note: The bidi implications of such [=forced line breaks=]
			are defined by the <a href="https://www.unicode.org/reports/tr9/"><cite>Unicode Bidirectional Algorithm</cite></a>.
			[[!UAX9]]

		<li>
			Except where explicitly defined otherwise
			(e.g. for ''line-break: anywhere'' or ''overflow-wrap: anywhere'')
			line breaking behavior defined for
			the <code>WJ</code>,
			<code>ZW</code>,
			<code>GL</code>,
			and <code>ZWJ</code>
			Unicode line breaking classes
			must be honored.
			[[!UAX14]]

			<wpt>
			word-break/word-break-normal-001.html
			line-breaking/line-breaking-001.html
			line-breaking/line-breaking-002.html
			line-breaking/line-breaking-003.html
			line-breaking/line-breaking-004.html
			line-breaking/line-breaking-005.html
			line-breaking/line-breaking-006.html
			line-breaking/line-breaking-007.html
			line-breaking/line-breaking-008.html
			line-breaking/line-breaking-021.html
			i18n/css3-text-line-break-baspglwj-001.html
			i18n/css3-text-line-break-baspglwj-002.html
			i18n/css3-text-line-break-baspglwj-120.html
			i18n/css3-text-line-break-baspglwj-121.html
			i18n/css3-text-line-break-baspglwj-122.html
			i18n/css3-text-line-break-baspglwj-123.html
			i18n/css3-text-line-break-baspglwj-124.html
			i18n/css3-text-line-break-baspglwj-125.html
			i18n/css3-text-line-break-baspglwj-126.html
			i18n/css3-text-line-break-baspglwj-127.html
			i18n/css3-text-line-break-baspglwj-128.html
			i18n/css3-text-line-break-baspglwj-130.html
			i18n/css3-text-line-break-baspglwj-131.html
			word-break/word-break-break-all-018.html
			word-break/word-break-break-all-021.html
			word-break/word-break-break-all-022.html
			</wpt>

		<li>
			UAs that allow wrapping at punctuation
			other than [=word separators=]
			in writing systems that use them
			<em>should</em> prioritize breakpoints.
			(For example, if breaks after slashes are given a lower priority than spaces,
			the sequence “check /etc” will never break between the "/" and the "e".)
			As long as care is taken to avoid such awkward breaks,
			allowing breaks at appropriate punctuation other than [=word separators=]
			is recommended,
			as it results in more even-looking margins, particularly in narrow measures.
			The UA may use the width of the containing block, the text's language,
			the 'line-break' value,
			and other factors in assigning priorities:
			CSS does not define prioritization of line breaking opportunities.
			Prioritization of [=word separators=] is not expected,
			however,
			if ''word-break: break-all'' is specified
			(since this value explicitly requests line breaking behavior
			not based on breaking at [=word separators=])--
			and is forbidden under ''line-break: anywhere''.

		<li>
			Out-of-flow elements
			and inline element boundaries
			do not introduce a [=forced line break=]
			or [=soft wrap opportunity=] in the flow.

			<wpt>
			line-breaking/line-breaking-012.html
			line-breaking/line-breaking-015.html
			line-breaking/line-breaking-016.html
			line-breaking/line-breaking-017.html
			line-breaking/line-breaking-018.html
			line-breaking/line-breaking-019.html
			</wpt>

		<li>
			For Web-compatibility
			there is a [=soft wrap opportunity=]
			before and after each replaced element or other [=atomic inline=],
			even when adjacent to a character that would normally suppress them,
			such as U+00A0 NO-BREAK SPACE.

			<wpt>
			line-breaking/line-breaking-atomic-001.html
			line-breaking/line-breaking-atomic-002.html
			line-breaking/line-breaking-atomic-003.html
			line-breaking/line-breaking-atomic-004.html
			line-breaking/line-breaking-atomic-005.html
			line-breaking/line-breaking-atomic-006.html
			line-breaking/line-breaking-atomic-007.html
			line-breaking/line-breaking-atomic-008.html
			line-breaking/line-breaking-atomic-009.html
			line-breaking/line-breaking-replaced-001.html
			line-breaking/line-breaking-replaced-002.html
			line-breaking/line-breaking-replaced-003.html
			line-breaking/line-breaking-replaced-004.html
			line-breaking/line-breaking-replaced-005.html
			line-breaking/line-breaking-replaced-006.html
			line-breaking/line-breaking-atomic-nowrap-001.html
			</wpt>

		<li>
			For [=soft wrap opportunities=] created by characters
			that disappear at the line break (e.g. U+0020 SPACE),
			properties on the box directly containing that character
			control the line breaking at that opportunity.
			For [=soft wrap opportunities=] defined by the boundary between two characters,
			the 'white-space' property
			on the nearest common ancestor of the two characters
			controls breaking;
			<!-- http://lists.w3.org/Archives/Public/www-style/2008Dec/0043.html -->
			which elements’ 'line-break', 'word-break', and 'overflow-wrap' properties
			control the determination of [=soft wrap opportunities=]
			at such boundaries
			is undefined in Level 3.

			<wpt>
			line-breaking/line-breaking-009.html
			line-breaking/line-breaking-010.html
			line-breaking/line-breaking-011.html
			line-breaking/line-breaking-ic-001.html
			line-breaking/line-breaking-ic-002.html
			line-breaking/line-breaking-ic-003.html
			white-space/white-space-wrap-after-nowrap-001.html
			word-break/word-break-break-all-inline-010.html
			overflow-wrap/overflow-wrap-anywhere-inline-003.html
			word-break/break-boundary-2-chars-001.html
			</wpt>

		<li>
			For [=soft wrap opportunities=] before the first
			or after the last character of a box,
			the break occurs immediately before/after the box
			(at its margin edge)
			rather than breaking the box
			between its content edge and the content.

		<li>
			Line breaking in/around Ruby is defined
			in [[css-ruby-1#line-breaks]].
			[[!CSS-RUBY-1]]

		<li>
			In order to avoid unexpected overflow,
			if the user agent is unable to perform the requisite lexical
			or orthographic analysis
			for line breaking any [=content language=] that requires it--
			for example due to lacking a dictionary for certain languages--
			it must assume a [=soft wrap opportunity=]
			between pairs of [=typographic letter units=] in that writing system.

			Note: This provision is not triggered merely when
			the UA fails to find a word boundary in a particular text run;
			the text run may well be a single unbreakable word.
			It applies for example
			when a text run is composed of Khmer characters (U+1780 to U+17FF)
			if the user agent does not know how to determine
			word boundaries in Khmer.
	</ul>

<h3 id="word-break-property" caniuse="word-break" oldids="word-break">
Breaking Rules for Letters: the 'word-break' property</h3>

	<wpt title="
		This section has partial test coverage.

		Missing tests:
		* No test of Animation type.
		* affects intrinsic sizing (tested for word-break:break-word)
		* treating non-letter typographic character units belonging to the NU, AL, AI, or ID Unicode line breaking classes
		* any typographic character units resolving to the any typographic letter units (and any typographic character units resolving to the <code>NU</code> (“numeric”), <code>AL</code> (“alphabetic”), or <code>SA</code> (“Southeast Asian”) line breaking classes
		* effect of word-break:keep-all on NU and AI classes
		* Symbols that line-break the same way as letters of a particular category are affected the same way as those letters.
		* does not suppress wbr
		* Tests for <a href=https://github.com/w3c/csswg-drafts/issues/4765>https://github.com/w3c/csswg-drafts/issues/4765</a>
		* More tests for “does not affect rules governing the soft wrap opportunities created around punctuation"></wpt>

	<pre class="propdef">
	Name: word-break
	Value: normal | keep-all | break-all | break-word
	Initial: normal
	Applies to: text
	Inherited: yes
	Canonical order: n/a
	Computed value: specified keyword
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/word-break-invalid.html
	parsing/word-break-valid.html
	parsing/word-break-computed.html
	word-break/word-break-break-all-inline-001.html
	word-break/word-break-break-all-inline-002.html
	word-break/word-break-break-all-inline-003.html
	word-break/word-break-break-all-inline-004.html
	word-break/word-break-break-all-inline-005.html
	word-break/word-break-break-all-inline-006.html
	word-break/word-break-break-all-inline-007.html
	word-break/word-break-break-all-inline-009.html
	word-break/word-break-break-all-062.html
	word-break/word-break-keep-all-063.html
	</wpt>

	This property specifies [=soft wrap opportunities=] between letters,
	i.e. where it is “normal” and permissible to break lines of text.
	Specifically it controls whether a [=soft wrap opportunity=]
	generally exists
	between adjacent [=typographic letter units=],
	treating non-[=letter=] [=typographic character units=]
	belonging to the
	<code>NU</code>,
	<code>AL</code>,
	<code>AI</code>,
	or <code>ID</code>
	Unicode line breaking classes
	as [=typographic letter units=] for this purpose (only).
	[[!UAX14]]
	It does not affect rules governing the [=soft wrap opportunities=]
	created by [=white space=]
	(as well as by [=other space separators=])
	and around punctuation.
	(See 'line-break' for controls affecting punctuation and small kana.)

	<wpt>
	word-break/word-break-break-all-010.html
	word-break/word-break-break-all-020.html
	word-break/word-break-keep-all-005.html
	word-break/word-break-keep-all-006.html
	word-break/word-break-keep-all-007.html
	word-break/word-break-keep-all-008.html
	word-break/word-break-break-all-012.html
	word-break/word-break-break-all-013.html
	word-break/word-break-break-all-015.html
	word-break/word-break-break-all-016.html
	word-break/word-break-break-all-019.html
	word-break/word-break-break-all-020.html
	word-break/word-break-break-all-023.html
	word-break/word-break-break-all-024.html
	word-break/word-break-break-all-025.html
	word-break/word-break-break-all-026.html
	word-break/word-break-break-all-027.html
	word-break/word-break-break-all-028.html
	word-break/word-break-break-all-inline-008.html
	white-space/break-spaces-008.html
	word-break/word-break-min-content-003.html
	</wpt>

	<div class="example">
		For example,
		in some styles of CJK typesetting,
		English words are allowed to break between any two letters,
		rather than only at spaces or hyphenation points;
		this can be enabled with ''word-break:break-all''.

		<figure>
			<img src="images/break-all.png"
			     alt="A snippet of Japanese text with English in it.
			          The word 'caption' is broken into 'capt' and 'ion' across two lines.">

			<figcaption>
				An example of English text embedded in Japanese
				being broken at an arbitrary point in the word.
			</figcaption>
		</figure>

		As another example, Korean has two styles of line-breaking:
		between any two Korean syllables (''word-break: normal'')
		or, like English, mainly at spaces (''word-break: keep-all'').

		<pre>
			각 줄의 마지막에 한글이 올 때 줄 나눔 <strong>기
			준을</strong> “글자” 또는 “어절” 단위로 한다.
		</pre>

		<pre>
			각 줄의 마지막에 한글이 올 때 줄 나눔
			<strong>기준을</strong> “글자” 또는 “어절” 단위로 한다.
		</pre>

		Ethiopic similarly has two styles of line-breaking,
		either only breaking at [=word separators=] (''word-break: normal''),
		or also allowing breaks between letters within a word (''word-break: break-all'').

		<pre>
			ተወልዱ፡ኵሉ፡ሰብእ፡ግዑዛን፡ወዕሩያን፡
			<strong>በማዕረግ</strong>፡ወብሕግ።ቦሙ፡ኅሊና፡ወዐቅል፡
			ወይትጌበሩ፡አሐዱ፡ምስለ፡አሀዱ፡
			በመንፈሰ፡እኍና።
		</pre>

		<pre>
			ተወልዱ፡ኵሉ፡ሰብእ፡ግዑዛን፡ወዕሩያን፡<strong>በማ
			ዕረግ</strong>፡ወብሕግ።ቦሙ፡ኅሊና፡ወዐቅል፡ወይትጌ
			በሩ፡አሐዱ፡ምስለ፡አሀዱ፡በመንፈሰ፡እኍና።
		</pre>
	</div>

	Note: To enable additional break opportunities only in the case of overflow,
	see 'overflow-wrap'.

	Values have the following meanings:

	<dl dfn-for=word-break dfn-type=value>
		<dt><dfn>normal</dfn>
		<dd>
			Words break according to their customary rules,
			as described [[#line-breaking|above]].
			Korean, which commonly exhibits two different behaviors,
			allows breaks between any two consecutive Hangul/Hanja.
			For Ethiopic, which also exhibits two different behaviors,
			such breaks within words are not allowed.

			<wpt>
			word-break/word-break-normal-ar-000.html
			word-break/word-break-normal-bo-000.html
			word-break/word-break-normal-en-000.html
			word-break/word-break-normal-hi-000.html
			word-break/word-break-normal-ja-000.html
			word-break/word-break-normal-ja-001.html
			word-break/word-break-normal-ja-002.html
			word-break/word-break-normal-ja-004.html
			word-break/word-break-normal-km-000.html
			word-break/word-break-normal-ko-000.html
			word-break/word-break-normal-lo-000.html
			word-break/word-break-normal-my-000.html
			word-break/word-break-normal-tdd-000.html
			word-break/word-break-normal-th-000.html
			word-break/word-break-normal-zh-000.html
			</wpt>

		<dt><dfn>break-all</dfn>
		<dd>
			Breaking is allowed within “words”:
			specifically,
			in addition to [=soft wrap opportunities=] allowed for ''word-break/normal'',
			any [=typographic letter units=]
			(and any [=typographic character units=] resolving to the
			<code>NU</code> (“numeric”),
			<code>AL</code> (“alphabetic”),
			or <code>SA</code> (“Southeast Asian”)
			line breaking classes [[!UAX14]])
			are instead treated as <code>ID</code>
			(“ideographic characters”)
			for the purpose of line-breaking.
			Hyphenation is not applied.

			<wpt>
			word-break/word-break-break-all-000.html
			word-break/word-break-break-all-001.html
			word-break/word-break-break-all-002.html
			word-break/word-break-break-all-003.html
			word-break/word-break-break-all-005.html
			word-break/word-break-break-all-006.html
			word-break/word-break-break-all-012.html
			word-break/word-break-break-all-013.html
			word-break/word-break-break-all-014.html
			word-break/word-break-break-all-015.html
			word-break/word-break-break-all-016.html
			word-break/word-break-break-all-017.html
			word-break/word-break-break-all-018.html
			word-break/word-break-break-all-019.html
			word-break/word-break-break-all-020.html
			word-break/word-break-break-all-021.html
			word-break/word-break-break-all-022.html
			word-break/word-break-break-all-023.html
			word-break/word-break-break-all-024.html
			word-break/word-break-break-all-025.html
			word-break/word-break-break-all-026.html
			word-break/word-break-break-all-027.html
			word-break/word-break-break-all-028.html
			word-break/word-break-break-all-029.html
			word-break/word-break-break-all-030.html
			word-break/word-break-break-all-031.html
			word-break/word-break-break-all-032.html
			word-break/word-break-break-all-inline-001.html
			word-break/word-break-break-all-inline-002.html
			word-break/word-break-break-all-inline-003.html
			word-break/word-break-break-all-inline-004.html
			word-break/word-break-break-all-inline-005.html
			word-break/word-break-break-all-inline-006.html
			word-break/word-break-break-all-inline-007.html
			word-break/word-break-break-all-inline-008.html
			word-break/word-break-break-all-inline-009.html
			word-break/word-break-break-all-inline-010.html
			white-space/break-spaces-006.html
			white-space/break-spaces-008.html
			white-space/break-spaces-before-first-char-004.html
			white-space/break-spaces-before-first-char-005.html
			white-space/break-spaces-before-first-char-006.html
			white-space/break-spaces-before-first-ideographic-char-004.html
			white-space/break-spaces-before-first-ideographic-char-005.html
			white-space/break-spaces-before-first-ideographic-char-006.html
			overflow-wrap/overflow-wrap-anywhere-006.html
			line-break/line-break-loose-hyphens-002.html
			line-break/line-break-normal-hyphens-002.html
			line-break/line-break-strict-hyphens-002.html
			word-break/break-boundary-2-chars-002.html
			</wpt>

			Note: This value does not affect
			whether there are [=soft wrap opportunities=]
			around punctuation characters.
			To allow breaks anywhere, see ''line-break: anywhere''.

			<wpt>
			white-space/break-spaces-before-first-char-011.html
			white-space/break-spaces-before-first-ideographic-char-011.html
			</wpt>

			Note: This option enables the other common behavior for Ethiopic.
			It is also often used in a context where
			the text consists predominantly of CJK characters
			with only short non-CJK excerpts,
			and it is desired that the text be better distributed on each line.

		<dt><dfn>keep-all</dfn>
		<dd>
			Breaking is forbidden within “words”:
			implicit [=soft wrap opportunities=] between [=typographic letter units=]
			(or other [=typographic character units=]
			belonging to the
			<code>NU</code>,
			<code>AL</code>,
			<code>AI</code>,
			or <code>ID</code>
			Unicode line breaking classes [[!UAX14]])
			are suppressed,
			i.e. breaks are prohibited between pairs of such characters
			(regardless of 'line-break' settings other than ''line-break/anywhere'')
			except where opportunities exist due to dictionary-based breaking.
			Otherwise this option is equivalent to ''word-break/normal''.
			In this style, sequences of CJK characters do not break.

			<wpt>
			word-break/word-break-keep-all-000.html
			word-break/word-break-keep-all-001.html
			word-break/word-break-keep-all-002.html
			word-break/word-break-keep-all-003.html
			word-break/word-break-keep-all-009.html
			word-break/word-break-keep-all-010.html
			</wpt>

			Note: This is the other common behavior for Korean
			(which uses [=spaces=] between words),
			and is also useful for mixed-script text where CJK snippets are mixed
			into another language that uses [=spaces=] for separation.
	</dl>

	Symbols that line-break the same way as letters of a particular category
	are affected the same way as those letters.

	<div class="example">
		Here’s a mixed-script sample text:

		<pre style="white-space: pre-wrap">
			这是一些汉字 and some Latin <bdi dir=rtl>و کمی خط عربی</bdi> และตัวอย่างการเขียนภาษาไทย በጽሑፍ፡ማራዘሙን፡አንዳንድ፡
		</pre>

		The break-points are determined as follows (indicated by &lsquo;&middot;&rsquo;):

		<dl>
			<dt>''word-break: normal''
			<dd>
				<pre style="white-space: pre-wrap">
					这·是·一·些·汉·字·and·some·Latin·<bdi dir=rtl>و·کمی·خط·عربی</bdi>·และ·ตัวอย่าง·การเขียน·ภาษาไทย·በጽሑፍ፡·ማራዘሙን፡·አንዳንድ፡
				</pre>

			<dt>''word-break: break-all''
			<dd>
				<pre style="white-space: pre-wrap">
					这·是·一·些·汉·字·a·n·d·s·o·m·e·L·a·t·i·n·<bdi dir=rtl>و·ﮐ·ﻤ·ﻰ·ﺧ·ﻁ·ﻋ·ﺮ·ﺑ·ﻰ</bdi>·แ·ล·ะ·ตั·ว·อ·ย่·า·ง·ก·า·ร·เ·ขี·ย·น·ภ·า·ษ·า·ไ·ท·ย·በ·ጽ·ሑ·ፍ፡·ማ·ራ·ዘ·ሙ·ን፡·አ·ን·ዳ·ን·ድ፡
				</pre>

			<dt>''word-break: keep-all''
			<dd>
				<pre style="white-space: pre-wrap">
					这是一些汉字·and·some·Latin·<bdi dir=rtl>و·کمی·خط·عربی</bdi>·และ·ตัวอย่าง·การเขียน·ภาษาไทย·በጽሑፍ፡·ማራዘሙን፡·አንዳንድ፡
				</pre>
		</dl>
	</div>

	<div class="example" id=jp-title-break>
		<style>
			#jp-title-break td samp,
			#jp-title-break td pre {
				font-size: 1.5em;
				width: 9em;
				line-height: 2;
				padding: 0.5em 1em;
				display: block;
				margin: auto;
				border: solid gray 1px;
				background: white;
			}
		</style>

		Japanese is usually typeset allowing line breaks within words.
		However, it is sometimes preferred to suppress these wrapping opportunities
		and to only allow wrapping at the end of certain sentence fragments.
		This is most commonly done in very short pieces of text,
		such as headings and table or figure captions.

		This can be achieved by marking the allowed wrapping points
		with <{wbr}> or U+200B ZERO WIDTH SPACE,
		and suppressing the other ones using ''word-break: keep-all''.

		For instance, the following markup can produce either of the renderings below,
		depending on the value of the 'word-break' property:

		<xmp highlight=markup>
			<h1>窓ぎわの<wbr>トットちゃん</h1>
		</xmp>

		<table class=data>
			<colgroup span=1></colgroup>
			<colgroup span=2></colgroup>
			<thead>
				<tr>
					<td>
					<th><code highlight=css>h1 { word-break: normal }</code>
					<th><code highlight=css>h1 { word-break: keep-all }</code>
			<tbody>
				<tr>
					<th scope=row>Expected rendering
					<td>
						<pre lang=ja>
							窓ぎわのトットちゃ
							ん
						</pre>

					<td>
						<pre lang=ja>
							窓ぎわの
							トットちゃん
						</pre>
				<tr>
					<th scope=row>Result in your browser
					<td>
						<samp lang=ja>
							窓ぎわの<wbr>トットちゃん
						</samp>
					<td>
						<samp style="word-break:keep-all" lang=ja>
							窓ぎわの<wbr>トットちゃん
						</samp>
		</table>
	</div>

	When shaping scripts such as Arabic
	are allowed to break within words due to ''word-break/break-all''
	the characters must still be shaped
	as if the word were [[#word-break-shaping|not broken]]
	(see [[#word-break-shaping]]).

	<wpt>
	word-break/word-break-break-all-004.html
	</wpt>

	For compatibility with legacy content,
	the 'word-break' property also supports
	a deprecated <dfn value for=word-break>break-word</dfn> keyword.
	When specified, this has the same effect as
	''word-break: normal'' and ''overflow-wrap: anywhere'',
	regardless of the actual value of the 'overflow-wrap' property.
	<!-- This is officially sad -->

	<wpt>
	white-space/pre-wrap-008.html
	white-space/pre-wrap-016.html
	word-break/word-break-break-word-overflow-wrap-interactions.html
	word-break/word-break-break-word-crash-001.html
	white-space/break-spaces-003.html
	white-space/break-spaces-004.html
	white-space/break-spaces-008.html
	white-space/break-spaces-before-first-char-010.html
	white-space/break-spaces-before-first-ideographic-char-010.html
	word-break/word-break-min-content-001.html
	word-break/word-break-min-content-002.html
	word-break/word-break-min-content-003.html
	word-break/word-break-min-content-004.html
	word-break/word-break-min-content-005.html
	word-break/word-break-min-content-006.html
	white-space/break-spaces-with-ideographic-space-002.html
	white-space/break-spaces-with-ideographic-space-004.html
	white-space/break-spaces-with-ideographic-space-006.html
	white-space/break-spaces-with-ideographic-space-008.html
	white-space/break-spaces-with-ideographic-space-009.html
	</wpt>

<h3 id="line-break-property">
Line Breaking Strictness: the 'line-break' property</h3>

	<wpt title="
		This section has extensive test coverage for CJK.

		Missing tests:
		* applies to text
		* No test of Animation type.
		* affects intrinsic sizing

		Untestable(?):
		* behavior of “auto”"></wpt>

	<pre class="propdef">
	Name: line-break
	Value: auto | loose | normal | strict | anywhere
	Initial: auto
	Applies to: text
	Inherited: yes
	Canonical order: n/a
	Computed value: specified keyword
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/line-break-valid.html
	parsing/line-break-invalid.html
	parsing/line-break-computed.html
	</wpt>

	This property specifies the strictness of line-breaking rules applied
	within an element:
	especially how [=wrapping=] interacts with punctuation and symbols.
	Values have the following meanings:

	<dl dfn-for=line-break dfn-type=value>
		<dt><dfn>auto</dfn>
		<dd>
			The UA determines the set of line-breaking restrictions to use,
			and it may vary the restrictions based on the length of the line;
			e.g., use a less restrictive set of line-break rules for short lines.

		<dt><dfn>loose</dfn>
		<dd>
			Breaks text using the least restrictive set of line-breaking
			rules. Typically used for short lines, such as in newspapers.

		<dt><dfn>normal</dfn>
		<dd>
			Breaks text using the most common set of line-breaking rules.

		<dt><dfn>strict</dfn>
		<dd>
			Breaks text using the most stringent set of line-breaking rules.

		<dt><dfn>anywhere</dfn>
		<dd>
			There is a [=soft wrap opportunity=] around every [=typographic character unit=],
			including around any punctuation character
			or [=preserved white spaces=],
			or in the middle of words,
			disregarding any prohibition against line breaks,
			even those introduced by characters with the <code>GL</code>, <code>WJ</code>, or <code>ZWJ</code> line breaking classes
			or mandated by the 'word-break' property.
			[[UAX14]]
			The different wrapping opportunities must not be prioritized.
			Hyphenation is not applied.

			<wpt>
			line-break/line-break-anywhere-001.html
			line-break/line-break-anywhere-002.html
			line-break/line-break-anywhere-003.html
			line-break/line-break-anywhere-004.html
			line-break/line-break-anywhere-005.html
			line-break/line-break-anywhere-006.html
			line-break/line-break-anywhere-007.html
			line-break/line-break-anywhere-008.html
			line-break/line-break-anywhere-009.html
			line-break/line-break-anywhere-010.html
			line-break/line-break-anywhere-011.html
			line-break/line-break-anywhere-012.html
			line-break/line-break-anywhere-013.html
			line-break/line-break-anywhere-014.html
			line-break/line-break-anywhere-015.html
			line-break/line-break-anywhere-016.html
			line-break/line-break-anywhere-017.html
			line-break/line-break-anywhere-and-white-space-001.html
			line-break/line-break-anywhere-and-white-space-002.html
			line-break/line-break-anywhere-and-white-space-003.html
			line-break/line-break-anywhere-and-white-space-004.html
			line-break/line-break-anywhere-and-white-space-005.html
			line-break/line-break-anywhere-and-white-space-006.html
			line-break/line-break-anywhere-and-white-space-007.html
			line-break/line-break-anywhere-and-white-space-008.html
			line-break/line-break-anywhere-and-white-space-009.html
			line-break/line-break-anywhere-and-white-space-009.html
			line-break/line-break-anywhere-overrides-uax-behavior-001.html
			line-break/line-break-anywhere-overrides-uax-behavior-002.html
			line-break/line-break-anywhere-overrides-uax-behavior-003.html
			line-break/line-break-anywhere-overrides-uax-behavior-004.html
			line-break/line-break-anywhere-overrides-uax-behavior-005.html
			line-break/line-break-anywhere-overrides-uax-behavior-006.html
			line-break/line-break-anywhere-overrides-uax-behavior-007.html
			line-break/line-break-anywhere-overrides-uax-behavior-008.html
			line-break/line-break-anywhere-overrides-uax-behavior-009.html
			line-break/line-break-anywhere-overrides-uax-behavior-010.html
			line-break/line-break-anywhere-overrides-uax-behavior-011.html
			line-break/line-break-anywhere-overrides-uax-behavior-012.html
			line-break/line-break-anywhere-overrides-uax-behavior-013.html
			line-break/line-break-anywhere-overrides-uax-behavior-014.html
			line-break/line-break-anywhere-overrides-uax-behavior-015.html
			line-break/line-break-anywhere-overrides-uax-behavior-016.html
			line-break/line-break-shaping-001.html
			white-space/break-spaces-before-first-char-007.html
			white-space/break-spaces-before-first-char-011.html
			white-space/break-spaces-before-first-ideographic-char-007.html
			white-space/break-spaces-before-first-ideographic-char-011.html
			</wpt>

			Note: This value triggers the line breaking rules typically seen in terminals.

			<div class=note>
				Note: ''line-break/anywhere'' only allows [=preserved white spaces=]
				at the end of the line
				to be wrapped to the next line
				when 'white-space' is set to ''white-space/break-spaces'',
				because in other cases:

				<ul>
					<li>
						[=preserved white space=] at the end/start of the line is discarded
						(''white-space/normal'', ''white-space/pre-line'')

					<li>
						wrapping is forbidden altogether (''nowrap'', ''pre'')

					<li>
						the [=preserved white space=] [=hang=] (''pre-wrap'').
				</ul>

				When it does have an effect on [=preserved white space=],
				with ''white-space: break-spaces'',
				it allows breaking before the first space of a sequence,
				which ''break-spaces'' on its own does not.
			</div>

			<wpt>
			line-break/line-break-anywhere-005.html
			white-space/break-spaces-before-first-char-007.html
			white-space/break-spaces-before-first-char-008.html
			white-space/break-spaces-before-first-char-009.html
			white-space/break-spaces-before-first-char-010.html
			white-space/break-spaces-before-first-ideographic-char-007.html
			white-space/break-spaces-before-first-ideographic-char-008.html
			white-space/break-spaces-before-first-ideographic-char-009.html
			white-space/break-spaces-before-first-ideographic-char-010.html
			</wpt>
	</dl>

	CSS distinguishes between four levels of strictness
	in the rules for text wrapping.
	The precise set of rules in effect for each of
	''line-break/loose'',
	''line-break/normal'',
	and ''line-break/strict''
	is up to the UA
	and should follow language conventions.
	However, this specification does require that:

	<ul>
		<li>
			The following breaks are forbidden in ''strict'' line breaking
			and allowed in ''line-break/normal'' and ''loose'':

			<ul>
				<li>
					breaks before Japanese small kana
					or the Katakana-Hiragana prolonged sound mark,
					i.e. characters
					from the Unicode line breaking class <code>CJ</code>.
					[[!UAX14]]

					<wpt>
					line-break/line-break-loose-011.xht
					line-break/line-break-loose-012.xht
					line-break/line-break-normal-011.xht
					line-break/line-break-normal-012.xht
					line-break/line-break-strict-011.xht
					line-break/line-break-strict-012.xht
					i18n/ja/css-text-line-break-ja-cj-loose.html
					i18n/ja/css-text-line-break-ja-cj-normal.html
					i18n/ja/css-text-line-break-ja-cj-strict.html
					i18n/zh/css-text-line-break-zh-cj-loose.html
					i18n/zh/css-text-line-break-zh-cj-normal.html
					i18n/zh/css-text-line-break-zh-cj-strict.html
					i18n/other-lang/css-text-line-break-de-cj-loose.html
					i18n/other-lang/css-text-line-break-de-cj-normal.html
					i18n/other-lang/css-text-line-break-de-cj-strict.html
					i18n/unknown-lang/css-text-line-break-cj-loose.html
					i18n/unknown-lang/css-text-line-break-cj-normal.html
					i18n/unknown-lang/css-text-line-break-cj-strict.html
					</wpt>
			</ul>

		<li>
			The following breaks are allowed for ''line-break/normal''
			and ''loose'' line breaking
			if the [=writing system=] is <a for=writing-system>Chinese</a>
			or <a for=writing-system>Japanese</a>,
			and are otherwise forbidden:

			<ul>
				<li>
					breaks before certain CJK hyphen-like characters:<br>
					&#x301C;&nbsp;U+301C,
					&#x30A0;&nbsp;U+30A0

					<wpt>
					line-break/line-break-loose-013.xht
					line-break/line-break-normal-013.xht
					line-break/line-break-strict-013.xht
					i18n/ja/css-text-line-break-ja-hyphens-loose.html
					i18n/ja/css-text-line-break-ja-hyphens-normal.html
					i18n/ja/css-text-line-break-ja-hyphens-strict.html
					i18n/zh/css-text-line-break-zh-hyphens-loose.html
					i18n/zh/css-text-line-break-zh-hyphens-normal.html
					i18n/zh/css-text-line-break-zh-hyphens-strict.html
					i18n/other-lang/css-text-line-break-de-hyphens-loose.html
					i18n/other-lang/css-text-line-break-de-hyphens-normal.html
					i18n/other-lang/css-text-line-break-de-hyphens-strict.html
					i18n/unknown-lang/css-text-line-break-hyphens-loose.html
					i18n/unknown-lang/css-text-line-break-hyphens-normal.html
					i18n/unknown-lang/css-text-line-break-hyphens-strict.html
					writing-system/writing-system-line-break-001.html
					</wpt>
			</ul>
		<li>
			The following breaks are allowed for ''loose'' line breaking
			if the preceding character
			belongs to the Unicode line breaking class <code>ID</code>
			[[!UAX14]]
			(including when the preceding character
			is treated as <code>ID</code>
			due to ''word-break: break-all''),
			and are otherwise forbidden:

			<ul>
				<li>
					breaks before hyphens:<br>
					&#x2010;&nbsp;U+2010,  &#x2013;&nbsp;U+2013

					<wpt>
					line-break/line-break-loose-hyphens-001.html
					line-break/line-break-normal-hyphens-001.html
					line-break/line-break-strict-hyphens-001.html
					line-break/line-break-loose-hyphens-002.html
					line-break/line-break-normal-hyphens-002.html
					line-break/line-break-strict-hyphens-002.html
					line-break/line-break-loose-hyphens-003.html
					line-break/line-break-normal-hyphens-003.html
					line-break/line-break-strict-hyphens-003.html
					</wpt>
			</ul>
		<li>
			The following breaks are forbidden for ''line-break/normal''
			and ''strict'' line breaking
			and allowed in ''loose'':

			<ul>
				<li>
					breaks before iteration marks:<br>
					&#x3005;&nbsp;U+3005,  &#x303B;&nbsp;U+303B,  &#x309D;&nbsp;U+309D,
					&#x309E;&nbsp;U+309E,  &#x30FD;&nbsp;U+30FD,  &#x30FE;&nbsp;U+30FE

					<wpt>
					line-break/line-break-loose-014.xht
					line-break/line-break-normal-014.xht
					line-break/line-break-strict-014.xht
					i18n/ja/css-text-line-break-ja-iteration-loose.html
					i18n/ja/css-text-line-break-ja-iteration-normal.html
					i18n/ja/css-text-line-break-ja-iteration-strict.html
					i18n/zh/css-text-line-break-zh-iteration-loose.html
					i18n/zh/css-text-line-break-zh-iteration-normal.html
					i18n/zh/css-text-line-break-zh-iteration-strict.html
					i18n/other-lang/css-text-line-break-de-iteration-loose.html
					i18n/other-lang/css-text-line-break-de-iteration-normal.html
					i18n/other-lang/css-text-line-break-de-iteration-strict.html
					i18n/unknown-lang/css-text-line-break-iteration-loose.html
					i18n/unknown-lang/css-text-line-break-iteration-normal.html
					i18n/unknown-lang/css-text-line-break-iteration-strict.html
					</wpt>

				<li>
					breaks between inseparable characters
					(such as &#x2025;&nbsp;U+2025, &#x2026;&nbsp;U+2026)
					i.e. characters from the Unicode line breaking class <code>IN</code>.
					[[!UAX14]]

					<wpt>
					line-break/line-break-loose-015.xht
					line-break/line-break-normal-015a.xht
					line-break/line-break-normal-015b.xht
					line-break/line-break-strict-015a.xht
					line-break/line-break-strict-015b.xht
					i18n/ja/css-text-line-break-ja-in-loose.html
					i18n/ja/css-text-line-break-ja-in-normal.html
					i18n/ja/css-text-line-break-ja-in-strict.html
					i18n/zh/css-text-line-break-zh-in-loose.html
					i18n/zh/css-text-line-break-zh-in-normal.html
					i18n/zh/css-text-line-break-zh-in-strict.html
					i18n/other-lang/css-text-line-break-de-in-loose.html
					i18n/other-lang/css-text-line-break-de-in-normal.html
					i18n/other-lang/css-text-line-break-de-in-strict.html
					i18n/unknown-lang/css-text-line-break-in-loose.html
					i18n/unknown-lang/css-text-line-break-in-normal.html
					i18n/unknown-lang/css-text-line-break-in-strict.html
					</wpt>
			</ul>
		<li>
			The following breaks are allowed for ''loose''
			if the [=writing system=] is <a for=writing-system>Chinese</a>
			or <a for=writing-system>Japanese</a>
			and are otherwise forbidden:

			<ul>
				<li>
					breaks before certain centered punctuation marks:<br>
					&#x30FB;&nbsp;U+30FB,
					&#xFF1A;&nbsp;U+FF1A,  &#xFF1B;&nbsp;U+FF1B,  &#xFF65;&nbsp;U+FF65,
					&#x203C;&nbsp;U+203C,
					&#x2047;&nbsp;U+2047,  &#x2048;&nbsp;U+2048,  &#x2049;&nbsp;U+2049,
					&#xFF01;&nbsp;U+FF01,  &#xFF1F;&nbsp;U+FF1F

					<wpt>
					line-break/line-break-loose-016a.xht
					line-break/line-break-loose-016b.xht
					line-break/line-break-normal-016a.xht
					line-break/line-break-normal-016b.xht
					line-break/line-break-strict-016a.xht
					line-break/line-break-strict-016b.xht
					i18n/ja/css-text-line-break-ja-cpm-loose.html
					i18n/ja/css-text-line-break-ja-cpm-normal.html
					i18n/ja/css-text-line-break-ja-cpm-strict.html
					i18n/zh/css-text-line-break-zh-cpm-loose.html
					i18n/zh/css-text-line-break-zh-cpm-normal.html
					i18n/zh/css-text-line-break-zh-cpm-strict.html
					i18n/other-lang/css-text-line-break-de-cpm-loose.html
					i18n/other-lang/css-text-line-break-de-cpm-normal.html
					i18n/other-lang/css-text-line-break-de-cpm-strict.html
					i18n/unknown-lang/css-text-line-break-cpm-loose.html
					i18n/unknown-lang/css-text-line-break-cpm-normal.html
					i18n/unknown-lang/css-text-line-break-cpm-strict.html
					writing-system/writing-system-line-break-002.html
					</wpt>

				<li>
					breaks before suffixes:<br>
					Characters with the Unicode line breaking class <code>PO</code>
					[[!UAX14]]
					and the [=East Asian Width property=]
					[[!UAX11]]
					<code>Ambiguous</code>,
					<code>Fullwidth</code>,
					or <code>Wide</code>.

					<wpt>
					line-break/line-break-loose-017a.xht
					line-break/line-break-loose-017b.xht
					line-break/line-break-normal-017a.xht
					line-break/line-break-normal-017b.xht
					line-break/line-break-strict-017a.xht
					line-break/line-break-strict-017b.xht
					i18n/ja/css-text-line-break-ja-po-loose.html
					i18n/ja/css-text-line-break-ja-po-normal.html
					i18n/ja/css-text-line-break-ja-po-strict.html
					i18n/zh/css-text-line-break-zh-po-loose.html
					i18n/zh/css-text-line-break-zh-po-normal.html
					i18n/zh/css-text-line-break-zh-po-strict.html
					i18n/other-lang/css-text-line-break-de-po-loose.html
					i18n/other-lang/css-text-line-break-de-po-normal.html
					i18n/other-lang/css-text-line-break-de-po-strict.html
					i18n/unknown-lang/css-text-line-break-po-loose.html
					i18n/unknown-lang/css-text-line-break-po-normal.html
					i18n/unknown-lang/css-text-line-break-po-strict.html
					</wpt>

				<li>
					breaks after prefixes:<br>
					Characters with the Unicode line breaking class <code>PR</code>
					[[!UAX14]]
					and the [=East Asian Width property=]
					[[!UAX11]]
					<code>Ambiguous</code>,
					<code>Fullwidth</code>,
					or <code>Wide</code>.

					<wpt>
					line-break/line-break-loose-018.xht
					line-break/line-break-normal-018.xht
					line-break/line-break-strict-018.xht
					i18n/ja/css-text-line-break-ja-pr-loose.html
					i18n/ja/css-text-line-break-ja-pr-normal.html
					i18n/ja/css-text-line-break-ja-pr-strict.html
					i18n/zh/css-text-line-break-zh-pr-loose.html
					i18n/zh/css-text-line-break-zh-pr-normal.html
					i18n/zh/css-text-line-break-zh-pr-strict.html
					i18n/other-lang/css-text-line-break-de-pr-loose.html
					i18n/other-lang/css-text-line-break-de-pr-normal.html
					i18n/other-lang/css-text-line-break-de-pr-strict.html
					i18n/unknown-lang/css-text-line-break-pr-loose.html
					i18n/unknown-lang/css-text-line-break-pr-normal.html
					i18n/unknown-lang/css-text-line-break-pr-strict.html
					</wpt>
			</ul>
	</ul>

	Note: The requirements listed above
	only create distinctions in CJK text.
	In an implementation that matches only the rules above,
	and no additional rules,
	'line-break' would only affect CJK code points
	unless the writing system is tagged as
	<a for=writing-system>Chinese</a> or <a for=writing-system>Japanese</a>.
	Future levels may add additional specific rules
	for other writing systems and languages
	as their requirements become known.

	<div class="example">
		As UAs can add additional distinctions
		between ''line-break/strict''/''line-break/normal''/''line-break/loose'' modes,
		these values can exhibit differences in other writing systems as well.
		For example, a UA with sufficiently-advanced Thai language processing ability
		could choose to map different levels of strictness in Thai line-breaking
		to these keywords,
		e.g. disallowing breaks within compound words in ''line-break/strict'' mode
		(e.g. breaking ตัวอย่างการเขียนภาษาไทย as ตัวอย่าง·การเขียน·ภาษาไทย)
		while allowing more breaks in ''line-break/loose''
		(ตัวอย่าง·การ·เขียน·ภาษา·ไทย).
	</div>

	Note: The CSSWG recognizes that in a future edition of the specification
	finer control over line breaking may be necessary
	to satisfy high-end publishing requirements.

<h3 id="hyphenation" oldids="hyphens-property" caniuse="css-hyphens">
Hyphenation: the 'hyphens' property</h3>

	<wpt title="This section has partial test coverage.

		Missing tests:
		* No test of Animation type.
		* Affects intrinsic sizing
		* “Automatic hyphenation opportunities within a word must be ignored if the word contains a conditional hyphen (shy or U+00AD), in favor of the conditional hyphen(s)”
		* “However, if, even after breaking at such opportunities, a portion of that word is still too long to fit on one line, an automatic hyphenation opportunity may be used.”"></wpt>

	<dfn id=hyphenate lt="hyphenation|hyphenate">Hyphenation</dfn>
	is the controlled splitting of words
	where they usually would not be allowed to break
	to improve the layout of paragraphs,
	typically splitting words at syllabic or morphemic boundaries
	and visually indicating the split
	(usually by inserting a hyphen, U+2010).
	In some cases, hyphenation may also alter the spelling of a word.
	Regardless, hyphenation is a rendering effect only:
	it must have no effect on the underlying document content
	or on text selection or searching.

	Hyphenation occurs
	when the line breaks at a valid <dfn>hyphenation opportunity</dfn>,
	which is a type of [=soft wrap opportunity=]
	that exists within a word where [=hyphenation=] is allowed.
	In CSS [=hyphenation opportunities=] are controlled
	with the 'hyphens' property.
	CSS Text Level 3 does not define the exact rules for [=hyphenation=];
	however UAs are strongly encouraged
	to optimize their choice of break points
	and to chose language-appropriate hyphenation points.

	<wpt>
	hyphens/hyphens-overflow-001.html
	</wpt>

	Note: The [=soft wrap opportunity=] introduced by
	the U+002D - HYPHEN-MINUS character
	or the U+2010 ‐ HYPHEN character
	is not a [=hyphenation opportunity=],
	as no visual indication of the split is <em>created</em> when wrapping:
	these characters are visible whether the line is wrapped at that point or not.

	Hyphenation opportunities <em>are</em> considered when calculating
	[=min-content size|min-content intrinsic sizes=].

	Note: This allows tables to hyphenate their contents
	instead of overflowing their containing block,
	which is particularly important in long-word languages like German.

	<!--
		See https://bugzilla.mozilla.org/show_bug.cgi?id=418975
	-->

	<pre class="propdef">
	Name: hyphens
	Value: none | manual | auto
	Initial: manual
	Applies to: text
	Inherited: yes
	Canonical order: n/a
	Computed value: specified keyword
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/hyphens-valid.html
	parsing/hyphens-invalid.html
	parsing/hyphens-computed.html
	hyphens/hyphens-auto-inline-010.html
	hyphens/hyphens-manual-inline-010.html
	hyphens/hyphens-manual-inline-011.html
	hyphens/hyphens-manual-inline-012.html
	</wpt>

	This property controls whether [=hyphenation=] is allowed to create more
	[=soft wrap opportunities=] within a line of text.
	Values have the following meanings:

	<dl dfn-for=hyphens dfn-type=value>
		<dt><dfn>none</dfn>
		<dd>
			Words are not hyphenated,
			even if characters inside the word
			explicitly define [=hyphenation opportunities=].

			Note: This does not suppress the existing [=soft wrap opportunities=]
			introduced by always visible characters such as
			U+002D - HYPHEN-MINUS
			or U+2010 ‐ HYPHEN.

			<wpt>
			hyphens/hyphens-none-011.html
			hyphens/hyphens-none-012.html
			hyphens/hyphens-none-013.html
			hyphens/hyphens-none-014.html
			hyphens/hyphens-none-015.html
			</wpt>

		<dt><dfn>manual</dfn>
		<dd>
			Words are only hyphenated where there are characters inside the word
			that explicitly suggest [=hyphenation opportunities=].

			<wpt>
			hyphens/hyphens-overflow-001.html
			hyphens/hyphens-manual-010.html
			hyphens/hyphens-manual-011.html
			hyphens/hyphens-manual-012.html
			hyphens/hyphens-manual-013.html
			hyphens/hyphens-out-of-flow-001.html
			hyphens/hyphens-shaping-001.html
			hyphens/hyphens-shaping-002.html
			hyphens/hyphens-span-001.html
			hyphens/shy-styling-001.html
			</wpt>

			<div class="example">
				In Unicode, U+00AD is a conditional "soft hyphen"
				and U+2010 is an unconditional hyphen.
				<cite>Unicode Standard Annex #14</cite>
				describes the <a href="http://unicode.org/reports/tr14/#SoftHyphen">role of soft hyphens in</a>
				Unicode line breaking.
				[[!UAX14]]
				In HTML,
				&amp;shy; represents the soft hyphen character,
				which suggests a hyphenation opportunity.

				<xmp highlight=html>ex&shy;ample</xmp>
			</div>

		<dt><dfn>auto</dfn>
		<dd>
			Words may be broken at [=hyphenation opportunities=]
			determined automatically by a language-appropriate hyphenation resource
			in addition to those indicated explicitly by a conditional hyphen.
			Automatic [=hyphenation opportunities=] within a word must be ignored
			if the word contains a conditional hyphen
			(&amp;shy; or U+00AD SOFT HYPHEN),
			in favor of the conditional hyphen(s).
			However, if, even after breaking at such opportunities,
			a portion of that word is still too long to fit on one line,
			an automatic hyphenation opportunity may be used.

			<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
			hyphenation-control-1.html
			</wpt>

			<wpt>
			hyphens/hyphens-auto-001.html
			hyphens/hyphens-auto-002.html
			hyphens/hyphens-auto-003.html
			hyphens/hyphens-auto-004.html
			hyphens/hyphens-auto-005.html
			hyphens/hyphens-auto-010.html
			hyphens/hyphens-out-of-flow-002.html
			hyphens/hyphens-span-002.html
			hyphens/hyphens-auto-and-contenteditable-crash.html
			hyphens/hyphens-auto-last-word-001.html
			hyphens/hyphens-punctuation-001.html
			</wpt>
	</dl>

	Correct automatic hyphenation requires a hyphenation resource
	appropriate to the language of the text being broken.
	The UA must therefore only automatically hyphenate text
	for which the <a>content language</a> is known
	and for which it has an appropriate hyphenation resource.

	<wpt>
	hyphens/hyphens-auto-001.html
	</wpt>

	<div class="advisement">
		Authors should correctly tag their content’s [=content language|language=]
		(e.g. using the HTML <code>lang</code> attribute
		or XML <code>xml:lang</code> attribute)
		in order to obtain correct automatic hyphenation.
	</div>

	The UA may use language-tailored heuristics
	to exclude certain words
	from automatic hyphenation.
	For example, a UA might try to avoid hyphenation in proper nouns
	by excluding words matching certain capitalization and punctuation patterns.
	Such heuristics are not defined by this specification.
	(Note that such heuristics will need to vary by language:
	English and German, for example, have very different capitalization conventions.)

	For the purpose of the 'hyphens' property,
	what constitutes a “word” is UA-dependent.
	However, inline element boundaries
	and out-of-flow elements
	must be ignored when determining word boundaries.

	<wpt>
	hyphens/hyphens-span-001.html
	hyphens/hyphens-span-002.html
	hyphens/hyphens-out-of-flow-001.html
	hyphens/hyphens-out-of-flow-002.html
	</wpt>

	Any glyphs shown due to hyphenation
	at a [=hyphenation opportunity=]
	created by a conditional hyphen character
	(such as U+00AD SOFT HYPHEN)
	are represented by that character
	and are styled according to the properties applied to it.

	<wpt>
	hyphens/shy-styling-001.html
	</wpt>

	When shaping scripts such as Arabic are allowed to break within words
	due to hyphenation,
	the characters must still be shaped
	as if the word were [[#word-break-shaping|not broken]]
	(see [[#word-break-shaping]]).

	<wpt>
	hyphens/hyphens-shaping-001.html
	hyphens/hyphens-shaping-002.html
	</wpt>

	<div class="example">
		For example, if the Uyghur word &ldquo;داميدى&rdquo;
		were hyphenated, it would appear as
		<img src="images/uyghur-hyphenate-joined.png"
		     alt="[isolated DAL + isolated ALEF + initial MEEM +
		          medial YEH + hyphen + line-break + final DAL +
		          isolated ALEF MAKSURA]">
		not as
		<img src="images/uyghur-hyphenate-unjoined.png"
		     alt="[isolated DAL + isolated ALEF + initial MEEM +
		          final YEH + hyphen + line-break + isolated DAL +
		          isolated ALEF MAKSURA]">
		.
	</div>

<h3 id="overflow-wrap-property" caniuse="wordwrap" oldids="overflow-wrap">
Overflow Wrapping: the 'overflow-wrap'/'word-wrap' property</h3>

	<wpt title="
		This section has fairly good test coverage.

		Missing tests:
		* No test of Animation type"></wpt>

	<pre class="propdef">
	Name: overflow-wrap, word-wrap
	Value: normal | break-word | anywhere
	Initial: normal
	Applies to: text
	Inherited: yes
	Canonical order: n/a
	Computed value: specified keyword
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/overflow-wrap-invalid.html
	parsing/overflow-wrap-valid.html
	parsing/overflow-wrap-computed.html
	parsing/word-wrap-invalid.html
	parsing/word-wrap-valid.html
	parsing/word-wrap-computed.html
	overflow-wrap/overflow-wrap-anywhere-span-001.html
	overflow-wrap/overflow-wrap-anywhere-span-002.html
	overflow-wrap/overflow-wrap-break-word-span-001.html
	overflow-wrap/overflow-wrap-break-word-span-002.html
	overflow-wrap/overflow-wrap-break-word-long-crash.html
	overflow-wrap/overflow-wrap-break-word-white-space-crash.html
	overflow-wrap/overflow-wrap-break-word-white-space-crash-002.html
	overflow-wrap/overflow-wrap-anywhere-inline-002.html
	</wpt>

	This property specifies whether the UA may break
	at otherwise disallowed points within a line
	to prevent overflow,
	when an otherwise-unbreakable string is too long to fit within the line box.
	It only has an effect when
	'white-space' allows [=wrapping=]. Possible values:

	<wpt>
	overflow-wrap/overflow-wrap-002.html
	</wpt>

	<dl dfn-for=overflow-wrap dfn-type=value>
		<dt><dfn>normal</dfn>
		<dd>
			Lines may break only at allowed break points.
			However,
			the restrictions introduced by ''word-break: keep-all'' may be relaxed
			to match ''word-break: normal''
			if there are no otherwise-acceptable break points in the line.

			<wpt>
			overflow-wrap/overflow-wrap-004.html
			overflow-wrap/overflow-wrap-normal-keep-all-001.html
			</wpt>

		<dt><dfn>anywhere</dfn>
		<dd>
			An otherwise unbreakable sequence of [=characters=]
			may be broken at an arbitrary point
			if there are no otherwise-acceptable break points in the line.
			Shaping characters are still shaped
			as if the word were not broken,
			and grapheme clusters must stay together as one unit.
			No hyphenation character is inserted at the break point.
			[=Soft wrap opportunities=] introduced by ''overflow-wrap/anywhere''
			<em>are considered</em>
			when calculating [=min-content size|min-content intrinsic sizes=].

			<wpt>
			overflow-wrap/overflow-wrap-min-content-size-001.html
			overflow-wrap/overflow-wrap-min-content-size-002.html
			overflow-wrap/overflow-wrap-min-content-size-003.html
			overflow-wrap/overflow-wrap-anywhere-001.html
			overflow-wrap/overflow-wrap-anywhere-003.html
			overflow-wrap/overflow-wrap-anywhere-006.html
			overflow-wrap/overflow-wrap-anywhere-007.html
			overflow-wrap/overflow-wrap-anywhere-008.html
			overflow-wrap/overflow-wrap-anywhere-009.html
			overflow-wrap/overflow-wrap-anywhere-010.html
			overflow-wrap/overflow-wrap-anywhere-011.html
			overflow-wrap/overflow-wrap-anywhere-inline-001.html
			overflow-wrap/overflow-wrap-anywhere-inline-002.html
			overflow-wrap/overflow-wrap-anywhere-inline-003.html
			overflow-wrap/overflow-wrap-anywhere-inline-004.html
			overflow-wrap/overflow-wrap-anywhere-fit-content-001.html
			overflow-wrap/overflow-wrap-min-content-size-005.html
			overflow-wrap/overflow-wrap-min-content-size-007.html
			overflow-wrap/overflow-wrap-cluster-002.html
			overflow-wrap/overflow-wrap-shaping-002.html
			white-space/break-spaces-before-first-char-009.html
			white-space/break-spaces-before-first-char-013.html
			white-space/break-spaces-before-first-ideographic-char-009.html
			white-space/break-spaces-before-first-ideographic-char-013.html
			word-break/word-break-min-content-001.html
			word-break/word-break-min-content-002.html
			word-break/word-break-min-content-003.html
			word-break/word-break-min-content-004.html
			word-break/word-break-min-content-005.html
			word-break/word-break-min-content-006.html
			white-space/pre-wrap-009.html
			white-space/pre-wrap-010.html
			white-space/break-spaces-with-overflow-wrap-002.html
			white-space/break-spaces-with-overflow-wrap-004.html
			white-space/break-spaces-with-overflow-wrap-006.html
			white-space/break-spaces-with-overflow-wrap-008.html
			white-space/break-spaces-with-overflow-wrap-010.html
			</wpt>

		<dt><dfn>break-word</dfn>
		<dd>
			As for ''overflow-wrap/anywhere''
			except that
			<a>soft wrap opportunities</a> introduced by ''overflow-wrap/break-word''
			are <em>not</em> considered
			when calculating [=min-content size|min-content intrinsic sizes=].

			<wpt>
			overflow-wrap/overflow-wrap-001.html
			overflow-wrap/overflow-wrap-break-word-001.html
			overflow-wrap/overflow-wrap-break-word-003.html
			overflow-wrap/overflow-wrap-break-word-008.html
			overflow-wrap/overflow-wrap-break-word-009.html
			overflow-wrap/overflow-wrap-break-word-010.html
			overflow-wrap/overflow-wrap-min-content-size-004.html
			overflow-wrap/overflow-wrap-min-content-size-006.html
			overflow-wrap/overflow-wrap-min-content-size-008.html
			overflow-wrap/overflow-wrap-break-word-fit-content-001.html
			overflow-wrap/overflow-wrap-cluster-001.html
			overflow-wrap/overflow-wrap-shaping-001.html
			white-space/break-spaces-before-first-char-008.html
			white-space/break-spaces-before-first-char-012.html
			white-space/break-spaces-before-first-ideographic-char-008.html
			white-space/break-spaces-before-first-ideographic-char-012.html
			overflow-wrap/overflow-wrap-break-word-keep-all-001.html
			white-space/break-spaces-with-overflow-wrap-001.html
			white-space/break-spaces-with-overflow-wrap-003.html
			white-space/break-spaces-with-overflow-wrap-005.html
			white-space/break-spaces-with-overflow-wrap-007.html
			white-space/break-spaces-with-overflow-wrap-009.html
			white-space/trailing-ideographic-space-013.html
			white-space/trailing-ideographic-space-014.html
			white-space/trailing-ideographic-space-015.html
			white-space/trailing-ideographic-space-016.html
			</wpt>
	</dl>

	For legacy reasons, UAs must treat 'word-wrap'
	as a [=legacy name alias=] of the 'overflow-wrap' property.

	<wpt>
	overflow-wrap/word-wrap-alias.html
	overflow-wrap/word-wrap-001.html
	overflow-wrap/word-wrap-002.html
	overflow-wrap/word-wrap-004.html
	</wpt>

<h3 id="word-break-shaping">
Shaping Across Intra-word Breaks</h3>

	<wpt title="This section has good test coverage."></wpt>

	When shaping scripts such as Arabic
	[=wrap=] at unforced [=soft wrap opportunities=] within words
	(such as when breaking due to
	''word-break: break-all'',
	''line-break: anywhere'',
	''overflow-wrap: break-word'',
	''overflow-wrap: anywhere'',
	or when [=hyphenating=])
	the characters must still be shaped
	(their joining forms chosen)
	as if the word were still whole.

	<wpt>
	hyphens/hyphens-shaping-001.html
	hyphens/hyphens-shaping-002.html
	line-break/line-break-shaping-001.html
	overflow-wrap/overflow-wrap-shaping-001.html
	overflow-wrap/overflow-wrap-shaping-002.html
	word-break/word-break-break-all-004.html
	</wpt>

	<div class="example">
		For example,
		if the word “نوشتن” is broken between the “ش” and “ت”,
		the “ش” still takes its initial form (“ﺷ”),
		and the “ت” its medial form (“ﺘ”)--
		forming as in “ﻧﻮﺷ | ﺘﻦ”, not as in “نوش | تن”.
	</div>

<h2 id="justification">
Alignment and Justification</h2>

	<wpt title="Tests only needed in subsections."></wpt>

	Alignment and justification controls
	how inline content is distributed within a line box.

<h3 id="text-align-property" oldids="text-align">
Text Alignment: the 'text-align' shorthand</h3>

	<wpt title="
		This section has partial test coverage.

		Missing tests:
		* If (after justification, if any) the inline contents of a line box are too long to fit within it, then the contents are start-aligned: any content that doesn’t fit overflows the line box’s end edge.
		* If the UA chooses to adjust the text, then it must ensure that tab stops continue to line up
		* “Values other than justify-all or match-parent are assigned to text-align-all and reset text-align-last to auto.”, and being a shorthand in general"></wpt>

	<pre class="propdef shorthand">
	Name: text-align
	Value: start | end | left | right | center | justify | match-parent | justify-all
	Initial: start
	Applies to: block containers
	Inherited: yes
	Canonical order: n/a
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/text-align-valid.html
	parsing/text-align-invalid.html
	parsing/text-align-computed.html
	</wpt>

	<wpt pathprefix="/css/CSS2/css1">
	c546-txt-align-000.xht
	</wpt>

	<wpt pathprefix="/css/CSS2/text">
	text-align-005.xht
	text-align-applies-to-001.xht
	text-align-applies-to-002.xht
	text-align-applies-to-003.xht
	text-align-applies-to-005.xht
	text-align-applies-to-006.xht
	text-align-applies-to-007.xht
	text-align-applies-to-008.xht
	text-align-applies-to-009.xht
	text-align-applies-to-010.xht
	text-align-applies-to-011.xht
	text-align-applies-to-012.xht
	text-align-applies-to-013.xht
	text-align-applies-to-014.xht
	text-align-applies-to-015.xht
	text-align-inherit-001.xht
	text-align-bidi-011.xht
	</wpt>

	This [=shorthand property=]
	sets the 'text-align-all' and 'text-align-last' properties
	and describes how the inline-level content of a block
	is aligned along the inline axis
	if the content does not completely fill the line box.
	Values other than ''justify-all'' or ''match-parent'' are assigned to 'text-align-all'
	and reset 'text-align-last' to ''text-align-last/auto''.

	Values have the following meanings:

	<dl dfn-for=text-align dfn-type=value>
		<dt><dfn>start</dfn>
		<dd>
			Inline-level content is aligned
			to the <a spec=css-writing-modes-4>start</a> edge of the line box.

			<wpt>
			text-align/text-align-006.html
			text-align/text-align-start-001.html
			text-align/text-align-start-002.html
			text-align/text-align-start-003.html
			text-align/text-align-start-004.html
			text-align/text-align-start-005.html
			text-align/text-align-start-006.html
			text-align/text-align-start-007.html
			text-align/text-align-start-008.html
			text-align/text-align-start-009.html
			text-align/text-align-start-010.html
			text-align/text-align-start-014.html
			text-align/text-align-start-015.html
			text-align/text-align-start-016.html
			text-align/text-align-start-017.html
			text-align/text-align-start-018.html
			text-align/text-align-start-019.html
			text-align/text-align-start-020.html
			text-align/text-align-start-021.html
			</wpt>

		<dt><dfn>end</dfn>
		<dd>
			Inline-level content is aligned
			to the <a spec=css-writing-modes-4>end</a> edge of the line box.

			<wpt>
			text-align/text-align-007.html
			text-align/text-align-end-001.html
			text-align/text-align-end-002.html
			text-align/text-align-end-003.html
			text-align/text-align-end-004.html
			text-align/text-align-end-005.html
			text-align/text-align-end-006.html
			text-align/text-align-end-007.html
			text-align/text-align-end-008.html
			text-align/text-align-end-009.html
			text-align/text-align-end-010.html
			text-align/text-align-end-014.html
			text-align/text-align-end-015.html
			text-align/text-align-end-016.html
			text-align/text-align-end-017.html
			text-align/text-align-end-018.html
			text-align/text-align-end-019.html
			text-align/text-align-end-020.html
			text-align/text-align-end-021.html
			</wpt>

		<dt><dfn>left</dfn>
		<dd>
			Inline-level content is aligned
			to the [=line-left=] edge of the line box.
			(In vertical writing modes,
			this can be either the physical top or bottom,
			depending on 'writing-mode'.)
			[[CSS-WRITING-MODES-4]]

			<wpt pathprefix="/css/CSS2/text">
			text-align-001.xht
			text-align-bidi-001.xht
			text-align-bidi-006.xht
			text-align-bidi-007.xht
			</wpt>

		<dt><dfn>right</dfn>
		<dd>
			Inline-level content is aligned
			to the [=line-right=]
			edge of the line box.
			(In vertical writing modes,
			this can be either the physical top or bottom,
			depending on 'writing-mode'.)
			[[CSS-WRITING-MODES-4]]

			<wpt pathprefix="/css/CSS2/text">
			text-align-002.xht
			text-align-bidi-005.xht
			</wpt>

		<dt><dfn>center</dfn>
		<dd>
			Inline-level content is centered within the line box.

			<wpt pathprefix="/css/CSS2/text">
			text-align-003.xht
			text-align-bidi-002.xht
			text-align-bidi-003.xht
			text-align-bidi-004.xht
			text-align-inherit-001.xht
			</wpt>

		<dt><dfn>justify</dfn>
		<dd>
			Text is justified
			according to the method specified by the 'text-justify' property,
			in order to exactly fill the line box.
			Unless otherwise specified by 'text-align-last',
			the last line before a forced break
			or the end of the block
			is ''start''-aligned.

			<wpt>
			text-align/text-align-justify-001.html
			text-align/text-align-justify-002.html
			text-align/text-align-justify-003.html
			text-align/text-align-justify-004.html
			text-align/text-align-justify-005.html
			text-align/text-align-justify-006.html
			text-align/text-align-justify-shy-001.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text">
			letter-spacing-justify-001.xht
			text-align-004.xht
			text-align-bidi-008.xht
			text-align-bidi-009.xht
			text-align-bidi-010.xht
			text-align-bidi-012.xht
			text-align-bidi-013.xht
			text-align-white-space-002.xht
			text-align-white-space-004.xht
			text-align-white-space-006.xht
			text-align-white-space-008.xht
			word-spacing-justify-001.xht
			</wpt>

		<dt><dfn>justify-all</dfn>
		<dd>
			Sets both 'text-align-all'
			and 'text-align-last'
			to ''text-align/justify'',
			forcing the last line to justify as well.

			<wpt>
			text-align/text-align-justifyall-001.html
			text-align/text-align-justifyall-002.html
			text-align/text-align-justifyall-003.html
			text-align/text-align-justifyall-004.html
			text-align/text-align-justifyall-005.html
			text-align/text-align-justifyall-006.html
			letter-spacing/letter-spacing-bidi-003.xht
			</wpt>

		<dt><dfn>match-parent</dfn>
		<dd>
			This value behaves the same as ''inherit''
			(computes to its parent’s computed value)
			except that an [=inherited value=] of ''start'' or ''end''
			is interpreted against the parent’s
			(or the [=initial containing block=]’s,
			if there is no parent)
			'direction' value
			and results in a computed value of either 'left' or 'right'.
			When specified on the 'text-align' shorthand,
			sets both 'text-align-all' and 'text-align-last' to ''text-align/match-parent''.

			<wpt>
			text-align/text-align-008.html
			</wpt>

			<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
			text-align-match-parent-01.html
			text-align-match-parent-02.html
			text-align-match-parent-03.html
			text-align-match-parent-04.html
			text-align-match-parent-root-ltr.html
			text-align-match-parent-root-rtl.html
			</wpt>
	</dl>

	A block of text
	is a stack of [=line boxes=].
	This property specifies how the inline-level boxes within each line box
	align with respect to the start and end sides of the line box.
	Alignment is not with respect to the
	[[CSS2/visuren#viewport|viewport]]
	or containing block.

	In the case of ''justify'',
	the UA may stretch or shrink any inline boxes
	by [[#text-justify-property|adjusting]] their text.
	(See 'text-justify'.)
	If an element’s [=white space=] is not [=collapsible=],
	then the UA is not required to adjust its text
	for the purpose of justification
	and may instead treat the text
	as having no [=justification opportunities=].
	If the UA chooses to adjust the text,
	then it must ensure
	that <a>tab stops</a> continue to line up as required by the
	[[#white-space-rules|white space processing rules]].

	<wpt pathprefix="/css/CSS2/text">
	text-align-white-space-001.xht
	text-align-white-space-003.xht
	text-align-white-space-005.xht
	text-align-white-space-007.xht
	</wpt>

	If (after justification, if any)
	the inline contents of a line box are too long to fit within it,
	then the contents are <a spec=css-writing-modes-4>start</a>-aligned:
	any content that doesn’t fit
	overflows the line box’s <a spec=css-writing-modes-4>end</a> edge.

	See [[#bidi-linebox]] for details on how to determine
	the <a spec=css-writing-modes-4>start</a> and <a spec=css-writing-modes-4>end</a> edges
	of a line box.

<h3 id="text-align-all-property" oldids="text-align-all">
Default Text Alignment: the 'text-align-all' property</h3>

	<wpt title="This section lacks tests."></wpt>

	<pre class="propdef">
	Name: text-align-all
	Value: start | end | left | right | center | justify | match-parent
	Initial: start
	Applies to: block containers
	Inherited: yes
	Computed value: keyword as specified, except for ''match-parent'' which computes as defined above
	Canonical order: n/a
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/text-align-all-valid.html
	parsing/text-align-all-invalid.html
	</wpt>

	This longhand of the 'text-align' [=shorthand property=]
	specifies the inline alignment of all lines of inline content in the block container,
	except for last lines
	overridden by a non-''text-align-last/auto'' value of 'text-align-last'.
	See 'text-align' for a full description of values.

	<p class="advisement">
	Authors should use the 'text-align' shorthand instead of this property.

<h3 id="text-align-last-property" caniuse="css-text-align-last" oldids="text-align-last">
Last Line Alignment: the 'text-align-last' property</h3>

	<wpt title="This section lacks tests."></wpt>

	<pre class="propdef">
	Name: text-align-last
	Value: auto | start | end | left | right | center | justify | match-parent
	Initial: auto
	Applies to: block containers
	Inherited: yes
	Canonical order: n/a
	Computed value: specified keyword
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/text-align-last-valid.html
	parsing/text-align-last-invalid.html
	parsing/text-align-last-computed.html
	text-align/text-align-last-013.html
	text-align/text-align-last-014.html
	</wpt>

	This property describes how the last line of a block or a line
	right before a [=forced line break=]
	is aligned.

	<wpt>
	text-align/text-align-last-001.html
	text-align/text-align-last-002.html
	text-align/text-align-last-003.html
	text-align/text-align-last-004.html
	text-align/text-align-last-005.html
	text-align/text-align-last-006.html
	text-align/text-align-last-010.html
	text-align/text-align-last-011.html
	text-align/text-align-last-012.html
	text-align/text-align-last-wins-001.html
	</wpt>

	If <dfn dfn-for=text-align-last dfn-type=value>auto</dfn> is specified,
	content on the affected line is aligned per 'text-align-all'
	unless 'text-align-all' is set to ''justify'',
	in which case it is ''text-align/start''-aligned.
	All other values are interpreted as described for 'text-align'.

	<wpt>
	text-align/text-align-last-007.html
	text-align/text-align-last-008.html
	text-align/text-align-last-009.html
	</wpt>

<h3 id="text-justify-property" caniuse="css-text-justify" oldids="text-justify">
Justification Method: the 'text-justify' property</h3>

	<wpt title="
		This section has light test coverage.
		All values (other than auto) are tested,
		but the tests are minimal.
		Not sure we can do better though.

		Missing tests:
		* No test of Animation Type
		* distribute <i>computes to</i> inter-character

		Untestable(?):
		* behavior of auto"></wpt>

	<pre class="propdef">
	Name: text-justify
	Value: auto | none | inter-word | inter-character
	Initial: auto
	Applies to: text
	Inherited: yes
	Canonical order: n/a
	Computed value: specified keyword (except for the ''distribute'' legacy value)
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/text-justify-valid.html
	parsing/text-justify-invalid.html
	parsing/text-justify-computed.html
	text-justify/text-justify-006.html
	</wpt>

	This property selects the justification method
	used when a line’s alignment is set to ''justify''
	(see 'text-align').
	The property applies to text,
	but is inherited from block containers
	to the root inline box containing their inline-level contents.
	It takes the following values:

	<wpt>
	text-justify/text-justify-006.html
	</wpt>

	<dl dfn-for=text-justify dfn-type=value>
		<dt><dfn>auto</dfn>
		<dd>
			The UA determines the justification algorithm to follow,
			based on a balance between performance and adequate presentation quality.
			Since justification rules vary by [=writing system=]
			and [=content language|language=],
			UAs should, where possible,
			use a justification algorithm appropriate to the text.

			<wpt pathprefix="/css/CSS2">
			text/letter-spacing-justify-001.xht
			text/word-spacing-justify-001.xht
			</wpt>

			<div class="example">
				For example,
				the UA could use by default a justification method
				that is a simple universal compromise for all writing systems--
				such as primarily expanding [=word separators=]
				and between CJK [=typographic letter units=]
				along with secondarily expanding
				between Southeast Asian [=typographic letter units=].
				Then, in cases where the [=content language=] of the paragraph is known,
				it could choose a more language-tailored justification behavior
				e.g. following the <a href="https://www.w3.org/TR/jlreq/"><cite>Requirements for Japanese Text Layout</cite></a> for Japanese [[JLREQ]],
				using cursive elongation for Arabic,
				using ''inter-word'' for German,
				etc.
			</div>

			<figure id="fig-text-justify-cursive">

				<img alt="Two lines of calligraphic Arabic end together
				          due to a mix of compressed and swash forms."
				     title="Swash forms elongate the first line
				            while a compressed contextual ligature shortens the second,
				            allowing both to end precisely together."
				            src="images/text-justify-cursive.png">

				<figcaption>
					An example of cursively-justified Arabic text,
					rendered by <a href="https://www.decotype.com/">Tasmeem</a>.
					Like English,
					Arabic can be justified by adjusting the spacing between words,
					but in most styles
					it can also be justified by calligraphically elongating
					or compressing the letterforms themselves.
					In this example,
					the upper text is extended to fill the line
					by the use of elongated (kashida) forms and swash forms,
					while the bottom line is compressed slightly
					by using a stacked combination for the characters between ت and م.
					By employing traditional calligraphic techniques,
					a typesetter can justify the line while preserving flow and color,
					providing a very high quality justification effect.
					However, this is by its nature a very script-specific effect.
				</figcaption>
			</figure>

			<figure id="fig-text-justify-compromise">
				<img alt="Extra space is partly to spaces and partly among CJK and Thai letters."
				     src="images/text-justify-compromise.png">

				<figcaption>
					Mixed-script text with ''text-justify: auto'':
					this interpretation uses a universal-compromise justification method,
					expanding at spaces as well as between CJK and Southeast Asian letters.
					This effectively uses inter-word + inter-ideograph spacing
					for lines that have word-separators and/or CJK characters
					and falls back to inter-cluster behavior for lines that don’t
					or for which the space stretches too far.
				</figcaption>
			</figure>

		<dt><dfn>none</dfn>
		<dd>
			Justification is disabled:
			there are no [=justification opportunities=] within the text.

			<wpt>
			text-justify/text-justify-001.html
			text-justify/text-justify-006.html
			</wpt>

			<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
			text-justify-none-001.html
			</wpt>

			<figure id="fig-text-justify-none">
				<img alt="No extra space is inserted."
				     src="images/text-justify-none.png">

				<figcaption>
					Mixed-script text with ''text-justify: none''
				</figcaption>
			</figure>

			Note: This value is intended for use in user stylesheets
			to improve readability or for accessibility purposes.

		<dt><dfn>inter-word</dfn>
		<dd>
			Justification adjusts spacing at [=word separators=] only
			(effectively varying the used 'word-spacing' on the line).
			This behavior is typical for languages that separate words using spaces,
			like English or Korean.

			<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
			text-justify-inter-word-001.html
			</wpt>

			<figure id="fig-text-justify-interword">
				<img alt="Extra space is equally distributed mainly to spaces."
				     src="images/text-justify-interword.png">

				<figcaption>
					Mixed-script text with ''text-justify: inter-word''
				</figcaption>
			</figure>

		<dt><dfn>inter-character</dfn>
		<dd>
			Justification adjusts spacing
			between each pair of adjacent [=typographic character units=]
			(effectively varying the used 'letter-spacing' on the line).
			This value is sometimes used in East Asian systems such as Japanese.

			<wpt>
			text-justify/text-justify-002.html
			</wpt>

			<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
			text-justify-inter-character-001.html
			</wpt>

			<figure id="fig-text-justify-distribute">
				<img alt="Extra space is equally distributed
				          at points between spaces and letters of all writing systems."
				     src="images/text-justify-distribute.png">

				<figcaption>
					Mixed-script text with ''text-justify: inter-character''
				</figcaption>
			</figure>

			For legacy reasons,
			UAs must also support the alternate keyword <dfn>distribute</dfn>
			which must compute to ''inter-character'',
			thus having the exact same meaning and behavior.

			<wpt>
			text-justify/text-justify-003.html
			</wpt>

			<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
			text-justify-distribute-001.html
			</wpt>
	</dl>

	<p class="advisement">
	Since optimal justification is [=content language|language=]-sensitive,
	authors should correctly language-tag their content for the best results.

	Note: The guidelines in this level of CSS
	do not describe a complete justification algorithm.
	They are merely a minimum set of requirements
	that a complete algorithm should meet.
	Limiting the set of requirements gives UAs some latitude
	in choosing a justification algorithm
	that meets their needs and desired balance of quality, speed, and complexity.

<h4 id="expanding-text">
Expanding and Compressing Text</h4>

	<wpt title="
		This section lacks tests.

		Missing tests:
		* whether a typographic character unit provides a justification opportunity is controlled by the text-justify value of its parent;
		* whether a justification opportunity exists between two consecutive typographic character units is determined by the text-justify value of their nearest common ancestor.
		* UAs must not break required ligatures or otherwise disable features required to correctly shape complex scripts
		* … and maybe more"></wpt>

	When justifying text,
	the user agent takes the remaining space
	between the ends of a line’s contents and the edges of its line box,
	and distributes that space throughout its content
	so that the contents exactly fill the line box.
	The user agent may alternatively distribute negative space,
	putting more content on the line
	than would otherwise fit under normal spacing conditions.

	A <dfn export oldids="expansion-opportunity">justification opportunity</dfn> is a point
	where the justification algorithm may alter spacing within the text.
	A justification opportunity can be provided by a single [=typographic character unit=]
	(such as a [=word separator=]),
	or by the juxtaposition of two [=typographic character units=].
	As with controls for [[#line-break-details|soft wrap opportunities]],
	whether a [=typographic character unit=] provides a [=justification opportunity=]
	is controlled by the 'text-justify' value of its parent;
	similarly,
	whether a [=justification opportunity=] exists
	between two consecutive [=typographic character units=]
	is determined by the 'text-justify' value of their nearest common ancestor.

	Space distributed by justification is <em>in addition to</em>
	the spacing defined by the 'letter-spacing' or 'word-spacing' properties.
	When such additional space is distributed
	to a [=word separator=] [=justification opportunity=],
	it is applied under the same rules as for 'word-spacing'.
	Similarly, when space is distributed
	to a [=justification opportunity=] between two [=typographic character units=],
	should be applied under the same rules as for 'letter-spacing'.

	A justification algorithm may divide [=justification opportunities=]
	into different priority levels.
	All [=justification opportunities=] within a given level
	are expanded or compressed at the same priority,
	regardless of which [=typographic character units=] created that opportunity.
	For example,
	if [=justification opportunities=] between two Han characters
	and between two Latin letters
	are defined to be at the same level
	(as they are in the ''inter-character'' justification style),
	they are not treated differently
	because they originate from different [=typographic character units=].
	It is not defined in this level
	whether or how other factors
	(such as font size, letter-spacing, glyph shape, position within the line, etc.)
	may influence the distribution of space to [=justification opportunities=] within the line.

	The UA may enable or break optional ligatures
	or use other font features
	such as alternate glyphs or glyph compression
	to help justify the text under any method.
	This behavior is not controlled by this level of CSS.
	However,
	UAs <em>must not</em> break required ligatures
	or otherwise disable features required to correctly shape complex scripts.

	If a [=justification opportunity=] exists within a line,
	and [[#text-align-property|text alignment]] specifies full justification
	(''text-align/justify'')
	for that line,
	it must be justified.

<h4 id="justify-symbols">
Handling Symbols and Punctuation</h4>

	<wpt title="This section lacks tests. Not sure what is testable though."></wpt>

	When determining [=justification opportunities=],
	a [=typographic character unit=]
	from the Unicode Symbols (S*) and Punctuation (P*) classes
	is generally treated the same as a [=typographic letter unit=] of the same script
	(or, if the character’s script property is Common,
	then as a [=typographic letter unit=] of the dominant script).

	However, by typographic tradition
	there may be additional rules controlling the justification of symbols and punctuation.
	Therefore, the UA may reassign specific characters
	or introduce additional levels of prioritization
	to handle [=justification opportunities=] involving symbols and punctuation.

	<div class="example">
		For example, there are traditionally no [=justification opportunities=]
		between consecutive
		U+2014 — EM DASH,
		U+2015 ― HORIZONTAL BAR,
		U+2026 … HORIZONTAL ELLIPSIS,
		or U+2025 ‥ TWO DOT LEADER
		characters [[JLREQ]];
		thus a UA might assign these characters to a “never” prioritization level.
		As another example, certain full-width punctuation characters
		(such as U+301A [ LEFT WHITE SQUARE BRACKET)
		are considered to contain a [=justification opportunity=] in Japanese.
		The UA might therefore assign these characters to a higher prioritization
		level than the opportunities between ideographic characters.
	</div>

<h4 id="justify-limits">
Unexpandable Text</h4>

	<wpt title="
		This section has basic test coverage.

		Missing tests:
		* Values of text-align-last other than justify
		* A broader range of non-stretchable content that just an empty span with padding"></wpt>

	If the inline contents of a line cannot be stretched to the full width of the line box,
	then they must be aligned as specified by the 'text-align-last' property.
	(If 'text-align-last' is ''justify'',
	then they must be aligned as for ''center''.)

	<wpt>
	text-align/text-align-last-empty-inline.html
	</wpt>

<h4 id="justify-cursive">
Cursive Scripts</h4>

	<wpt title="This section lacks automated tests."></wpt>

	Justification <em>must not</em> introduce gaps
	between the joined [=typographic letter units=]
	of [=cursive scripts=] such as Arabic.
	If it is able,
	the UA <em>may</em> translate space distributed to [=justification opportunities=]
	within a run of such [=typographic letter units=]
	into some form of cursive elongation for that run.
	It otherwise <em>must</em> assume that no [=justification opportunity=] exists
	between any pair of [=typographic letter units=] in [=cursive script=]
	(regardless of whether they join).

	<wpt>
	text-justify/text-justify-004.html
	text-justify/text-justify-005.html
	</wpt>

	<div class="example">
		The following are examples of unacceptable justification:

		<figure>
			<img alt="" src="images/arabic-stretch-spaced.png">

			<figcaption>
				Adding gaps between every pair of Arabic letters
			</figcaption>
		</figure>

		<figure>
			<img alt="" src="images/arabic-stretch-unjoined.png">

			<figcaption>
				Adding gaps between every pair of unjoined Arabic letters
			</figcaption>
		</figure>
	</div>

	Some font designs allow for the use of the tatweel character for justification.
	A UA that performs tatweel-based justification
	must properly handle the rules for its use.
	Note that correct insertion of tatweel characters depends on context,
	including the letter-combinations involved,
	location within the word,
	and location of the word within the line.

<h4 id="justify-algos">
Minimum Requirements for ''text-justify/auto'' Justification</h4>

	<wpt title="This section lacks tests."></wpt>

	For ''text-justify/auto'' justification,
	this specification does not define
	what all of the [=justification opportunities=] are,
	how they are prioritized,
	or when and how multiple levels of [=justification opportunities=] interact.
	However, it does require that:

	<ul>
		<li>
			Unless contraindicated by the typographic traditions
			of the [=content language=]
			or adjacent symbols/punctuation,
			each of the following provides a [=justification opportunity=]:

			<ul>
				<li>
					[=Word separators=]

				<li>
					The boundary between a [=typographic character unit=]
					of any [=block scripts=]
					and any other [=typographic character unit=]

				<li>
					The boundary between a [=typographic character unit=]
					of any [=clustered scripts=]
					and any other [=typographic character unit=]
			</ul>
		<li>
			All [=letters=] belonging to all [=block scripts=] are treated the same,
			and all [=letters=] belonging to all [=clustered scripts=] are treated the same.
			For example, no distinction is made
			between the justification opportunity
			between a Han letter followed by another Han letter,
			vs. the justification opportunity
			between a Han letter followed by a Hangul letter.
	</ul>

	Further information on text justification can be found in (or submitted to)
	<a href="https://www.w3.org/International/articles/typography/justification">“Approaches to Full Justification”</a>,
	which indexes by writing system and language,
	and is maintained by the <a href="https://www.w3.org/International/">W3C Internationalization Working Group</a>.
	[[JUSTIFY]]

<h2 id="spacing">
Spacing</h2>

	<wpt title="Tests only needed in subsections."></wpt>

	CSS offers control over text spacing
	via the 'word-spacing' and 'letter-spacing' properties,
	which specify additional space
	around [=word separators=]
	or between [=typographic character units=],
	respectively.

<h3 id="word-spacing-property" oldids="word-spacing">
Word Spacing: the 'word-spacing' property</h3>

	<wpt title="
		This section has limited test coverage.

		Missing tests:
		* inherit lengths as absolute
		* values may be negative
		* computed / resolved value of normal
		* should be applied half on each side of the character unless otherwise dictated by typographic tradition.
		* doesn’t do anything between words defined by text analysis like in Thai, only on actual word separators
		* works on  the Ethiopic word space (U+1361), the Aegean word separators (U+10100,U+10101), the Ugaritic word divider (U+1039F), and the Phoenician Word Separator (U+1091F).
		* word-spacing and bidi "></wpt>

	<pre class="propdef">
	Name: word-spacing
	Value: normal | <<length>>
	Initial: normal
	Applies to: text
	Inherited: yes
	Percentages: N/A
	Computed value: an absolute length
	Animation type: by computed value type
	Canonical order: n/a
	</pre>

	<wpt>
	inheritance.html
	parsing/word-spacing-valid.html
	parsing/word-spacing-invalid.html
	parsing/word-spacing-computed.html
	animations/word-spacing-interpolation.html
	animations/word-spacing-composition.html
	</wpt>

	<wpt pathprefix="/css/CSS2/css1">
	c541-word-sp-000.xht
	c541-word-sp-001.xht
	</wpt>

	<wpt pathprefix="css/CSS2/text">
	word-spacing-101.xht
	word-spacing-applies-to-001.xht
	word-spacing-applies-to-002.xht
	word-spacing-applies-to-003.xht
	word-spacing-applies-to-005.xht
	word-spacing-applies-to-006.xht
	word-spacing-applies-to-007.xht
	word-spacing-applies-to-008.xht
	word-spacing-applies-to-009.xht
	word-spacing-applies-to-010.xht
	word-spacing-applies-to-011.xht
	word-spacing-applies-to-012.xht
	word-spacing-applies-to-013.xht
	word-spacing-applies-to-014.xht
	word-spacing-applies-to-015.xht
	word-spacing-justify-001.xht
	</wpt>

	This property specifies additional spacing
	between &ldquo;words&rdquo;.
	Values are interpreted as defined below:

	<dl dfn-for=word-spacing dfn-type=value>
		<dt><dfn>normal</dfn>
		<dd>
			No additional spacing is applied.
			Computes to zero.

			<wpt pathprefix="css/CSS2/text">
			word-spacing-100.xht
			</wpt>

		<dt><dfn>&lt;length&gt;</dfn>
		<dd>
			Specifies extra spacing
			<em>in addition to</em> the intrinsic inter-word spacing
			defined by the font.

			<wpt>
			tab-size/tab-size-spacing-001.html
			</wpt>

			<wpt pathprefix="css/CSS2/text">
			word-spacing-004.xht
			word-spacing-005.xht
			word-spacing-006.xht
			word-spacing-007.xht
			word-spacing-008.xht
			word-spacing-016.xht
			word-spacing-017.xht
			word-spacing-018.xht
			word-spacing-019.xht
			word-spacing-020.xht
			word-spacing-028.xht
			word-spacing-029.xht
			word-spacing-030.xht
			word-spacing-031.xht
			word-spacing-032.xht
			word-spacing-040.xht
			word-spacing-041.xht
			word-spacing-042.xht
			word-spacing-043.xht
			word-spacing-044.xht
			word-spacing-052.xht
			word-spacing-053.xht
			word-spacing-054.xht
			word-spacing-055.xht
			word-spacing-056.xht
			word-spacing-064.xht
			word-spacing-065.xht
			word-spacing-066.xht
			word-spacing-067.xht
			word-spacing-068.xht
			word-spacing-076.xht
			word-spacing-077.xht
			word-spacing-078.xht
			word-spacing-079.xht
			word-spacing-080.xht
			word-spacing-088.xht
			word-spacing-089.xht
			word-spacing-090.xht
			word-spacing-091.xht
			word-spacing-092.xht
			word-spacing-097.xht
			word-spacing-098.xht
			word-spacing-099.xht
			</wpt>
	</dl>

	Additional spacing is applied to each [=word separator=] left in the text
	after the [[#white-space-rules|white space processing rules]] have been applied,
	and should be applied half on each side of the character
	unless otherwise dictated by typographic tradition.
	Values may be negative, but there may be implementation-dependent limits.

	<wpt pathprefix="css/CSS2/text">
	word-spacing-remove-space-001.xht
	word-spacing-remove-space-002.xht
	word-spacing-remove-space-003.xht
	word-spacing-remove-space-004.xht
	word-spacing-remove-space-005.xht
	word-spacing-remove-space-006.xht
	</wpt>

	<dfn id="word-separator" lt="word-separator character | word separator">Word-separator characters</dfn>
	are [=typographic character units=]
	whose primary purpose and general usage is to separate words.
	In Unicode this includes
	(but is not exhaustively defined as)
	the space (U+0020),
	the no-break space (U+00A0),
	the Ethiopic word space (U+1361),
	the Aegean word separators (U+10100,U+10101),
	the Ugaritic word divider (U+1039F),
	and the Phoenician word separator (U+1091F).
	[[UNICODE]]

	<wpt pathprefix="css/CSS2/text">
	word-spacing-characters-001.xht
	</wpt>

	Note: Neither punctuation in general,
	nor fixed-width spaces (such as U+3000 and U+2000 through U+200A),
	are considered [=word-separator characters=],
	because even though they frequently happen to separate words,
	their primary purpose is not to separate words.

	<wpt pathprefix="css/CSS2/text">
	word-spacing-characters-002.xht
	</wpt>

	If there are no [=word-separator characters=],
	or if a word-separating character has a zero advance width
	(such as U+200B ZERO WIDTH SPACE)
	then the user agent must not create an additional spacing between words.

	<wpt pathprefix="css/CSS2/text">
	word-spacing-characters-003.xht
	</wpt>

<h3 id="letter-spacing-property" caniuse="css-letter-spacing" oldids="letter-spacing">
Tracking: the 'letter-spacing' property</h3>

	<wpt title="
		This section has partial test coverage.

		Missing tests:
		* Due to <a href=https://github.com/w3c/csswg-drafts/issues/1518>issue 1518</a>, some/many tests in this section should be converted from MUST to SHOULD.
		* inherit lengths as absolute
		* For legacy reasons, a computed letter-spacing of zero yields a resolved value (getComputedStyle() return value) of normal.
		* When the effective spacing between two characters is not zero (due to either justification or a non-zero value of letter-spacing), user agents should not apply optional ligatures
		* However, ligatures and other font features specified via the low-level font-feature-settings property take precedence over this rule"></wpt>

	<pre class="propdef">
	Name: letter-spacing
	Value: normal | <<length>>
	Initial: normal
	Applies to: <a>inline boxes</a> and text
	Inherited: yes
	Computed value: an absolute length
	Animation type: by computed value type
	Canonical order: n/a
	</pre>

	<wpt>
	inheritance.html
	parsing/letter-spacing-valid.html
	parsing/letter-spacing-invalid.html
	parsing/letter-spacing-computed.html
	animations/letter-spacing-interpolation.html
	animations/letter-spacing-composition.html
	letter-spacing/letter-spacing-nesting-003.xht
	letter-spacing/letter-spacing-bidi-003.xht
	letter-spacing/letter-spacing-bidi-004.xht
	letter-spacing/letter-spacing-bidi-005.xht
	letter-spacing/letter-spacing-200.html
	letter-spacing/letter-spacing-201.html
	letter-spacing/letter-spacing-203.html
	letter-spacing/letter-spacing-206.html
	</wpt>

	<wpt pathprefix="/css/CSS2/css1">
	c542-letter-sp-000.xht
	c542-letter-sp-001.xht
	</wpt>

	<wpt pathprefix="/css/CSS2/text">
	letter-spacing-applies-to-001.xht
	letter-spacing-applies-to-002.xht
	letter-spacing-applies-to-003.xht
	letter-spacing-applies-to-005.xht
	letter-spacing-applies-to-006.xht
	letter-spacing-applies-to-007.xht
	letter-spacing-applies-to-008.xht
	letter-spacing-applies-to-009.xht
	letter-spacing-applies-to-010.xht
	letter-spacing-applies-to-011.xht
	letter-spacing-applies-to-012.xht
	letter-spacing-applies-to-013.xht
	letter-spacing-applies-to-014.xht
	letter-spacing-applies-to-015.xht
	</wpt>

	This property specifies additional spacing
	(commonly called <dfn export>tracking</dfn>)
	between adjacent [=typographic character units=].
	Letter-spacing is applied after
	[[css-writing-modes-4#text-direction|bidi reordering]]
	and is in addition to [[css-fonts-3#font-kerning-prop|kerning]]
	and 'word-spacing'.
	[[CSS-WRITING-MODES-4]]
	[[CSS-FONTS-3]]
	Depending on the justification rules in effect,
	user agents may further increase or decrease the space
	between [=typographic character units=]
	in order to [[#text-justify-property|justify text]].

	<wpt>
	letter-spacing/letter-spacing-bidi-001.html
	letter-spacing/letter-spacing-bidi-004.xht
	letter-spacing/letter-spacing-nesting-003.xht
	letter-spacing/letter-spacing-bidi-003.xht
	letter-spacing/letter-spacing-bidi-004.xht
	letter-spacing/letter-spacing-bidi-005.xht
	letter-spacing/letter-spacing-206.html
	letter-spacing/letter-spacing-211.html
	letter-spacing/letter-spacing-212.html
	</wpt>

	<wpt pathprefix="/css/CSS2">
	bidi-005.xht
	bidi-006.xht
	bidi-007.xht
	bidi-008.xht
	bidi-009.xht
	bidi-010.xht
	bidi-text/bidi-005a.xht
	bidi-text/bidi-005b.xht
	bidi-text/bidi-006a.xht
	bidi-text/bidi-006b.xht
	bidi-text/bidi-007b.xht
	bidi-text/bidi-008b.xht
	bidi-text/bidi-009b.xht
	bidi-text/bidi-010b.xht
	text/letter-spacing-justify-001.xht
	</wpt>

	Values have the following meanings:

	<dl dfn-for=letter-spacing dfn-type=value>
		<dt><dfn>normal</dfn>
		<dd>
			No additional spacing is applied. Computes to zero.

			<wpt pathprefix="/css/CSS2/text">
			letter-spacing-100.xht
			</wpt>

		<dt><dfn>&lt;length&gt;</dfn>
		<dd>
			Specifies <em>additional</em> spacing
			between [=typographic character units=].
			Values may be negative,
			but there may be implementation-dependent limits.

			<wpt>
			tab-size/tab-size-spacing-001.html
			</wpt>

			<wpt pathprefix="/css/CSS2/text">
			letter-spacing-004.xht
			letter-spacing-005.xht
			letter-spacing-006.xht
			letter-spacing-007.xht
			letter-spacing-008.xht
			letter-spacing-016.xht
			letter-spacing-017.xht
			letter-spacing-018.xht
			letter-spacing-019.xht
			letter-spacing-020.xht
			letter-spacing-028.xht
			letter-spacing-029.xht
			letter-spacing-030.xht
			letter-spacing-031.xht
			letter-spacing-032.xht
			letter-spacing-040.xht
			letter-spacing-041.xht
			letter-spacing-042.xht
			letter-spacing-043.xht
			letter-spacing-044.xht
			letter-spacing-052.xht
			letter-spacing-053.xht
			letter-spacing-054.xht
			letter-spacing-055.xht
			letter-spacing-056.xht
			letter-spacing-064.xht
			letter-spacing-065.xht
			letter-spacing-066.xht
			letter-spacing-067.xht
			letter-spacing-068.xht
			letter-spacing-076.xht
			letter-spacing-077.xht
			letter-spacing-078.xht
			letter-spacing-079.xht
			letter-spacing-080.xht
			letter-spacing-088.xht
			letter-spacing-089.xht
			letter-spacing-090.xht
			letter-spacing-091.xht
			letter-spacing-092.xht
			letter-spacing-097.xht
			letter-spacing-098.xht
			letter-spacing-099.xht
			letter-spacing-101.xht
			letter-spacing-102.xht
			</wpt>
	</dl>

	For <a href="https://github.com/w3c/csswg-drafts/issues/1484">legacy reasons</a>,
	a computed 'letter-spacing' of zero
	yields a [=resolved value=]
	({{getComputedStyle()}} return value)
	of ''letter-spacing/normal''.

	For the purpose of 'letter-spacing',
	each consecutive run of [=atomic inlines=]
	(such as images and inline blocks)
	is treated as a single [=typographic character unit=].

	<wpt>
	letter-spacing/letter-spacing-204.html
	</wpt>

	Letter-spacing must not be applied at the beginning of a line.
	Whether letter-spacing is applied at the end of a line is undefined in this level.

	<wpt>
	letter-spacing/letter-spacing-end-of-line-001.html
	tab-size/tab-size-spacing-001.html
	letter-spacing/letter-spacing-200.html
	letter-spacing/letter-spacing-201.html
	white-space/white-space-letter-spacing-001.html
	</wpt>

	<div class="example">
		When letter-spacing is not applied at the beginning or end of a line,
		text always fits flush with the edge of the block.

		<pre highlight=css>
			p { letter-spacing: 1em; }
		</pre>

		<xmp highlight=html>
			<p>abc</p>
		</xmp>

		<p class="ls-ex good ls-fixed-width color-box" style="text-align: left">a&#x3000;b&#x3000;c</p>
		<p class="ls-ex good ls-fixed-width color-box" style="text-align: right">a&#x3000;b&#x3000;c</p>

		UAs therefore <em>really should not</em> [[RFC6919]]
		append letter spacing to the right or trailing edge of a line:

		<p class="ls-ex bad ls-fixed-width color-box" style="text-align: right">a&#x3000;b&#x3000;c&#x3000;</p>
	</div>

	Letter spacing between two [=typographic character units=]
	effectively “belongs” to the innermost element
	that contains the two [=typographic character units=]:
	the total letter spacing between two adjacent [=typographic character units=]
	(after bidi reordering)
	is specified by and rendered within the innermost element
	that <em>contains</em> the boundary
	between the two [=typographic character units=].
	However, the UA may instead attach letter-spacing at element boundaries
	to one or the other [=typographic character unit=]
	using the letter-spacing value pertaining to its containing element.

	Note: This secondary behavior is permitted in this level
	due to Web-compat concerns.

	<wpt>
	letter-spacing/letter-spacing-bidi-002.html
	letter-spacing/letter-spacing-bidi-004.xht
	letter-spacing/letter-spacing-bidi-005.xht
	letter-spacing/letter-spacing-nesting-001.html
	letter-spacing/letter-spacing-nesting-002.html
	letter-spacing/letter-spacing-nesting-003.xht
	letter-spacing/letter-spacing-203.html
	letter-spacing/letter-spacing-205.html
	</wpt>

	<div class="example">
		An inline box is expected to only include
		letter spacing between characters completely contained within that element,
		thus excluding letter spacing on the right or trailing edge of the element:

		<pre highlight=css>p { letter-spacing: 1em; }</pre>

		<xmp highlight=html><p>a<span>bb</span>c</p></xmp>

		<p class="ls-ex good">a&#x3000;<span class="color-box">b&#x3000;b</span>&#x3000;c</p>

		<p class="ls-ex bad">a&#x3000;<span class="color-box">b&#x3000;b&#x3000;</span>c</p>

		Consequently a given value of 'letter-spacing' is expected
		to only affect the spacing between characters
		completely contained within the element for which it is specified:

		<pre highlight=css>
			p    { letter-spacing: 1em; }
			span { letter-spacing: 2em; }
		</pre>

		<xmp highlight=html><p>a<span>bb</span>c</p></xmp>

		<p class="ls-ex">a&#x3000;<span class="color-box">b&#x3000;&#x3000;b</span>&#x3000;c</p>

		<p>This further implies that applying 'letter-spacing' to
		an element containing only a single character
		has no effect on the rendered result:

		<pre highlight=css>
			p    { letter-spacing: 1em; }
			span { letter-spacing: 2em; }
		</pre>

		<xmp highlight=html><p>a<span>b</span>c</p></xmp>

		<p class="ls-ex">a&#x3000;<span class="color-box">b</span>&#X3000;c</p>

		Since letter spacing is inserted <strong>after</strong> RTL reordering,
		the letter spacing applied to the inner span below likewise has no effect,
		since after reordering the "c" doesn’t end up next to "&#x5d0;":

		<pre highlight=css>
			p    { letter-spacing: 1em; }
			span { letter-spacing: 2em; }
		</pre>

		<pre highlight=html>

			&lt;!-- abc followed by Hebrew letters alef (&#x5d0;), bet (&#x5d1;) and gimel (&#x5d2;) -->
			&lt;!-- Reordering will display these in reverse order. --&gt;
			<bdo dir=ltr>&lt;p>ab&lt;span>c&#x5d0;&lt;/span>&#x5d1;&#x5d2;&lt;/p></bdo>
		</pre>

		<p class="ls-ex">a&#x3000;b</span>&#x3000;<span class="color-box">c</span>&#x3000;<span class="color-box">&#x5d0;</span>&#x3000;&#x5d1;&#x3000;&#x5d2;</p>
	</div>

	Letter spacing ignores invisible zero-width formatting characters
	(such as those from the Unicode Cf category).
	Spacing must be added as if those characters did not exist in the document.

	<wpt>
	letter-spacing/letter-spacing-control-chars-001.html
	letter-spacing/letter-spacing-202.html
	</wpt>

	<div class="example">
		For example, 'letter-spacing' applied to
		<code highlight=html>A&amp;#x200B;B</code> is identical to <code highlight=html>AB</code>,
		regardless of where any element boundaries might fall.
	</div>

	When the effective spacing between two characters is not zero
	(due to either [[#text-justify-property|justification]]
	or a non-zero value of 'letter-spacing'),
	user agents should not apply optional ligatures,
	i.e. those that are not defined as required
	for fundamentally correct glyph shaping.
	However, ligatures and other font features
	specified via the low-level 'font-feature-settings' property
	take precedence over this rule.
	See [[css-fonts-3#feature-precedence]].

	<div class="example">
		For example, if the word “filial” is letter-spaced,
		an “fi” ligature should not be used
		as it will prevent even spacing of the text.

		<figure>
			<strong style="letter-spacing: 0.5em">filial</strong> vs <strong style="letter-spacing: 0.5em">filial</strong>
		</figure>
	</div>

	Note: In OpenType, required ligatures are expected
	to be associated to the <code>rlig</code> feature.
	All other ligatures are therefore considered optional.
	In some cases, however, UA or platform heuristics
	apply additional ligatures in order to handle broken fonts;
	this specification does not define or override such exceptional handling.

<h4 id="cursive-tracking">
Cursive Scripts</h4>

	<wpt title="This section lacks tests. Not sure automated tests are possible."></wpt>

	If it is able,
	the UA <em>may</em> apply letter spacing to [=cursive scripts=]
	by translating the total extra space to be distributed to a run of such letters
	into some form of cursive elongation
	(or compression, for negative tracking values)
	for that run
	that results in an equivalent total expansion (or compression) of the run.
	Otherwise,
	if the UA cannot expand text from a [=cursive script=]
	without breaking its cursive connections,
	it <em>must not</em> apply spacing
	between any pair of that script’s [=typographic letter units=] at all
	(effectively treating each word as a single [=typographic letter unit=]
	for the purpose of letter-spacing).
	Both cases will result in an effective spacing of zero between such letters;
	however the former will preserve the sense of stretching out the text.

	<div class="example">
      Below are some appropriate and inappropriate examples of spacing out Arabic text.

	  <table class="data">
		<thead>
			<tr>
				<td><img src="images/arabic-stretch-original.png" alt="">
				<td>&mdash;
				<td>Original text
		<tbody>
			<tr>
				<td><img src="images/arabic-stretch-spaced.png" alt="">
				<td class="no">BAD
				<th>
					Even distribution of space between each letter.
					<em>Notice this breaks cursive joins!</em>
			<tr>
				<td><img src="images/arabic-stretch-kashida.png" alt="">
				<td class="ok">OK
				<th>
					Distributing &sum;<var>letter-spacing</var>
					by typographically-appropriate cursive elongation.
					<em>The resulting text is as long as the previous evenly-spaced example.</em>

			<tr>
				<td><img src="images/arabic-stretch-suppressed.png" alt="">
				<td class="ok">OK
				<th>
					Suppressing 'letter-spacing' between Arabic letters.
					<em>Notice 'letter-spacing' is nonetheless applied
					to non-Arabic characters (like [=spaces=]).</em>

			<tr>
				<td><img src="images/arabic-stretch-unjoined.png" alt="">
				<td class="no">BAD
				<th>
					Applying 'letter-spacing' only between non-joined letters.
					<em>This distorts typographic color and obfuscates word boundaries.</em>
	  </table>
	</div>

	Note: Proper cursive elongation or compression of a text
	can vary depending on the
	script,
	typeface,
	language,
	location within a word,
	location within a line,
	implementation complexity,
	font capabilities,
	and calligraphic preferences,
	and may not be possible in certain cases at all.
	It may involve the use of shortening ligatures,
	swash variants,
	contextual forms,
	elongation glyphs such as U+0640 ـ ARABIC TATWEEL,
	or other microtypography.
	It is outside the scope of CSS to define rules for these effects.
	Authors should avoid applying 'letter-spacing' to cursive scripts
	unless they are prepared to accept non-interoperable results.

<h3 id="boundary-shaping">
Shaping Across Element Boundaries</h3>

	<wpt title="This section has good test coverage."></wpt>

	Text shaping <em>must</em> be broken at inline box boundaries
	when any of the following are true
	for any box whose boundary separates the two [=typographic character units=]:

	<ul>
		<li>
			Any of 'margin'/'border'/'padding'
			separating the two [=typographic character units=] in the inline axis
			is non-zero.

			<wpt>
			shaping/shaping-009.html
			shaping/reference/shaping-009-ref.html
			shaping/shaping-010.html
			shaping/reference/shaping-010-ref.html
			shaping/shaping-011.html
			shaping/reference/shaping-011-ref.html
			boundary-shaping/boundary-shaping-003.html
			boundary-shaping/boundary-shaping-004.html
			boundary-shaping/boundary-shaping-005.html
			boundary-shaping/boundary-shaping-007.html
			boundary-shaping/boundary-shaping-009.html
			</wpt>

		<li>
			'vertical-align' is not ''vertical-align/baseline''.

			<wpt>
			boundary-shaping/boundary-shaping-002.html
			boundary-shaping/boundary-shaping-006.html
			</wpt>

		<li>
			The boundary is a [=bidi-isolates|bidi isolation boundary=].

			<wpt>
			shaping/shaping-012.html
			shaping/reference/shaping-012-ref.html
			shaping/shaping-013.html
			boundary-shaping/boundary-shaping-008.html
			</wpt>
	</ul>

	Text shaping <em>must not</em> be broken across inline box boundaries
	when there is no effective change in formatting,
	or if the only formatting changes do not affect the glyphs
	(as in applying <a href="https://www.w3.org/TR/css-text-decor-3/">text decoration</a>).

	<wpt>
	text-transform/text-transform-shaping-001.html
	text-transform/text-transform-shaping-002.html
	text-transform/text-transform-shaping-003.html
	shaping/shaping-000.html
	shaping/reference/shaping-000-ref.html
	shaping/shaping-004.html
	shaping/shaping-005.html
	shaping/shaping-006.html
	shaping/shaping-007.html
	shaping/shaping-014.html
	shaping/reference/shaping-014-ref.html
	shaping/shaping-016.html
	shaping/reference/shaping-016-ref.html
	shaping/shaping-022.html
	shaping/reference/shaping-022-ref.html
	shaping/shaping-025.html
	shaping/reference/shaping-025-ref.html
	shaping/shaping_lig-000.html
	boundary-shaping/boundary-shaping-001.html
	boundary-shaping/boundary-shaping-010.html
	</wpt>

	Text shaping <em>should not</em> be broken across inline box boundaries otherwise,
	if it is reasonable and possible for that case given the limitations of the font technology.

	<wpt>
	shaping/shaping-001.html
	shaping/reference/shaping-001-ref.html
	shaping/shaping-002.html
	shaping/reference/shaping-002-ref.html
	shaping/shaping-003.html
	shaping/reference/shaping-003-ref.html
	shaping/shaping-008.html
	shaping/reference/shaping-008-ref.html
	shaping/shaping-017.html
	shaping/shaping-018.html
	shaping/shaping-020.html
	shaping/reference/shaping-020-ref.html
	shaping/shaping-021.html
	shaping/reference/shaping-021-ref.html
	shaping/shaping-023.html
	shaping/reference/shaping-023-ref.html
	shaping/shaping-024.html
	shaping/reference/shaping-024-ref.html
	boundary-shaping/boundary-shaping-009.html
	</wpt>

	<div class="example">
		An example of reasonable and possible shaping across boundaries
		is Arabic shaping:
		in many systems this is performed by the font engine,
		allowing the font to provide variant glyphs
		with potentially very sophisticated contextual shaping.
		It’s not generally possible to rely on this system across a font change
		unless the font engine has an API to provide context,
		but it is straightforward and therefore quite reasonable
		for an engine to work around this limitation by, for example,
		using the zero-width-joiner (U+200D) or zero-width-non-joiner (U+200C)
		as appropriate to solicit the correct choice of
		initial/medial/final/isolated glyph.

		An example of possible but not reasonable shaping across boundaries
		is handling a font that is sensitive to 20 characters of context
		on either side to choose its glyphs:
		passing all the text before <em>and after</em> the string in question,
		even through multiple inline boundaries with formatting changes,
		is complicated.
		The UA <em>could</em> handle such cases,
		but is not required to,
		as they are not typical or fundamentally required
		by any modern writing system.

		An example of impossible shaping across boundaries
		is a change in font weight partway through the word “and”
		in a font where a ligature would replace
		all three letters of the word “and”
		with an ampersand glyph (“&amp;”).

		<!--
			It’s simply not possible for the UA
			to create the effect of a partway-bold single glyph.
		-->
	</div>

<h2 id="edge-effects">
Edge Effects</h2>

	<wpt title="Tests only needed in subsections."></wpt>

	Edge effects control
	the indentation of lines with respect to other lines in the block ('text-indent')
	and how content is measured at the start and end edges of a line ('hanging-punctuation').

<h3 id="text-indent-property" caniuse="css-text-indent" oldids="text-indent">
First Line Indentation: the 'text-indent' property</h3>

	<wpt title="
		This section has partial test coverage.

		Missing tests:
		* hanging keyword
		* each-line keyword"></wpt>

	<pre class="propdef">
	Name: text-indent
	Value: [ <<length-percentage>> ] && hanging? && each-line?
	Initial: 0
	Applies to: block containers
	Inherited: yes
	Percentages: refers to block container’s own <a>inline-axis</a> <a>inner size</a>
	Computed value: computed <<length-percentage>> value, plus any specified keywords
	Animation type: by computed value type
	Canonical order: <abbr title="follows order of property value definition">per grammar</abbr>
	</pre>

	<wpt>
	inheritance.html
	parsing/text-indent-valid.html
	parsing/text-indent-invalid.html
	parsing/text-indent-computed.html
	animations/text-indent-interpolation.html
	animations/text-indent-composition.html
	text-indent/text-indent-long-line-crash.html
	</wpt>

	<wpt pathprefix="/css/CSS2/css1">
	c547-indent-000.xht
	c547-indent-001.xht
	</wpt>

	<wpt pathprefix="/css/CSS2/text/">
	text-indent-012.xht
	text-indent-013.xht
	text-indent-014.xht
	text-indent-112.xht
	text-indent-applies-to-001.xht
	text-indent-applies-to-002.xht
	text-indent-applies-to-003.xht
	text-indent-applies-to-005.xht
	text-indent-applies-to-006.xht
	text-indent-applies-to-007.xht
	text-indent-applies-to-008.xht
	text-indent-applies-to-009.xht
	text-indent-applies-to-010.xht
	text-indent-applies-to-011.xht
	text-indent-applies-to-012.xht
	text-indent-applies-to-013.xht
	text-indent-applies-to-014.xht
	text-indent-applies-to-015.xht
	text-indent-inherited-001.xht
	</wpt>

	This property specifies the indentation
	applied to lines of inline content in a block.
	The indent is treated as a margin
	applied to the <a spec=css-writing-modes-4>start</a> edge of the line box.

	<wpt pathprefix="/css/CSS2/text/">
	text-indent-010.xht
	text-indent-012.xht
	text-indent-013.xht
	text-indent-115.xht
	text-indent-on-blank-line-rtl-left-align.html
	text-indent-overflow-001.xht
	text-indent-overflow-002.xht
	text-indent-overflow-003.xht
	text-indent-overflow-004.xht
	text-indent-rtl-001.xht
	text-indent-rtl-002.xht
	</wpt>

	Unless otherwise specified
	by the ''each-line'' and/or ''text-indent/hanging'' keywords,
	only lines that are the
	[=first formatted line=]
	of an element are affected.
	[[!CSS-PSEUDO-4]]
	For example, the first line of an anonymous block box is only affected
	if it is the first child of its parent element.

	<wpt pathprefix="/css/CSS2/text/">
	text-indent-014.xht
	text-indent-wrap-001.xht
	</wpt>

	Values have the following meanings:

	<dl dfn-for=text-indent dfn-type=value>
		<dt><dfn>&lt;length&gt;</dfn>
		<dd>
			Gives the amount of the indent as an absolute length.

			<wpt pathprefix="/css/CSS2/text/">
			text-indent-004.xht
			text-indent-005.xht
			text-indent-006.xht
			text-indent-007.xht
			text-indent-008.xht
			text-indent-010.xht
			text-indent-012.xht
			text-indent-013.xht
			text-indent-014.xht
			text-indent-016.xht
			text-indent-017.xht
			text-indent-018.xht
			text-indent-019.xht
			text-indent-020.xht
			text-indent-028.xht
			text-indent-029.xht
			text-indent-030.xht
			text-indent-031.xht
			text-indent-032.xht
			text-indent-040.xht
			text-indent-041.xht
			text-indent-042.xht
			text-indent-043.xht
			text-indent-044.xht
			text-indent-052.xht
			text-indent-053.xht
			text-indent-054.xht
			text-indent-055.xht
			text-indent-056.xht
			text-indent-064.xht
			text-indent-065.xht
			text-indent-066.xht
			text-indent-067.xht
			text-indent-068.xht
			text-indent-076.xht
			text-indent-077.xht
			text-indent-078.xht
			text-indent-079.xht
			text-indent-080.xht
			text-indent-088.xht
			text-indent-089.xht
			text-indent-090.xht
			text-indent-091.xht
			text-indent-092.xht
			text-indent-109.xht
			text-indent-110.xht
			text-indent-111.xht
			text-indent-113.xht
			text-indent-114.xht
			text-indent-115.xht
			text-indent-intrinsic-001.xht
			text-indent-intrinsic-002.xht
			text-indent-intrinsic-003.xht
			text-indent-intrinsic-004.xht
			text-indent-on-blank-line-rtl-left-align.html
			text-indent-overflow-001.xht
			text-indent-overflow-002.xht
			text-indent-overflow-003.xht
			text-indent-overflow-004.xht
			text-indent-rtl-001.xht
			text-indent-rtl-002.xht
			</wpt>

		<dt><dfn>&lt;percentage&gt;</dfn>
		<dd>
			Gives the amount of the indent
			as a percentage of the block container’s own <a>logical width</a>.

			<wpt pathprefix="/css/CSS2/text/">
			text-indent-011.xht
			text-indent-100.xht
			text-indent-101.xht
			text-indent-102.xht
			text-indent-103.xht
			text-indent-104.xht
			text-indent-percent-001.xht
			</wpt>

			Percentages must be treated as ''0''
			for the purpose of calculating [=intrinsic size contributions=],
			but are always resolved normally when performing layout.

			<wpt>
			text-indent/percentage-value-intrinsic-size.html
			text-indent/text-indent-percentage-001.xht
			text-indent/text-indent-percentage-002.html
			text-indent/text-indent-percentage-003.html
			text-indent/text-indent-percentage-004.html
			</wpt>

			Note: This can lead to the element overflowing.
			It is not recommended to use percentage indents and intrinsic sizing together.

		<dt><dfn>each-line</dfn>
		<dd>
			Indentation affects the first line of each block container
			and each line after a <a>forced line break</a>
			(but not lines after a <a>soft wrap break</a>).

			<!--
				We could probably say "first formated line" here and not be incorrect,
				but that would also be unnecessarily specific, so keep it simple.
			-->

		<dt><dfn>hanging</dfn>
		<dd>
			Inverts which lines are affected.
    </dl>

	<div class="example">
		<p>If 'text-align' is ''start'' and 'text-indent' is ''5em'' in
		left-to-right text with no floats present, then first line of text
		will start 5em into the block:</p>

		<pre class="output">
			     Since CSS1 it has been possible to
			indent the first line of a block element
			5em by setting the 'text-indent' property&nbsp;
			to '5em'.
		</pre>

		If we add the ''text-indent/hanging'' keyword,
		then the first line will start flush,
		but other lines will be indented 5em:

		<pre class="output">
			In CSS3 we can instead indent all other
			     lines of the block element by 5em
			     by setting the 'text-indent' property
			     to 'hanging 5em'.
		</pre>
	</div>

	<div class="example">
		Since the 'text-indent' property only affects the “first formatted line”,
		a line after a forced break will not be indented.

		<pre class="output">
			   For example, in the middle of
			this paragraph is an equation,
			which is centered:
			             x + y = z
			The first line after the equation
			is flush (else it would look like
			we started a new paragraph).
		</pre>

		However, sometimes (as in poetry or code),
		it is appropriate to indent each line
		that happens to be long enough to wrap.
		In the following example, 'text-indent'
		is given a value of ''3em hanging each-line'',
		giving the third line of the poem a hanging indent
		where it soft-wraps at the block’s right boundary:

		<pre class="output">
			In a short line of text
			There need be no wrapping,
			But when we go on and on and on&nbsp;&nbsp;
			   and on,
			Sometimes a soft break
			Can help us stay on the page.
		</pre>
	</div>

	Note: Since the 'text-indent' property inherits,
	when specified on a block element, it will affect descendant
	inline-block elements.
	For this reason, it is often wise to specify ''text-indent: 0'' on
	elements that are specified ''display: inline-block''.</p>

<h3 id="hanging">
Hanging Glyphs</h3>

	<wpt title="
		Test coverage TBD.
		Partly tested through [[#hanging-punctuation-property]]
		partly through [[#white-space-phase-2]]."></wpt>

	When a glyph at the start or end edge of a line <dfn lt="hang">hangs</dfn>,
	it is not considered
	when measuring the line’s contents for fit, alignment, or justification.
	Depending on the line’s alignment/justification, this can
	result in the mark being placed outside the line box.
	The [=hanging=] glyph is also not taken into account
	when computing [=intrinsic sizes=] ([=min-content size=] and [=max-content size=]),
	and any sizes derived thereof.
	(The interaction of this measurement and kerning is currently UA-defined;
	the CSSWG <a href="https://github.com/w3c/csswg-drafts/issues/2397">welcomes advice</a> on this point.)

	<wpt>
	white-space/full-width-leading-spaces-004.html
	</wpt>

	A <dfn><a lt=hang>hanging</a> glyph</dfn>
	is still enclosed inside its parent inline box
	and still participates in text justification:
	its character advance is just not measured when determining
	how much content fits on the line,
	how much the line’s contents need to be expanded or compressed for justification,
	or how to position the content within the line box for text alignment.
	Effectively, the [=hanging=] glyph character advance
	is re-interpreted as an additional negative margin
	on the affected edge of its parent [=inline box=];
	the line is otherwise laid out as usual.
	An overflowing [=hanging glyph=] should typically be considered
	[=ink overflow=]
	so as to avoid creating unnecessary scrollbars,
	but the UA may treat it as [=scrollable overflow=]
	when the content is editable
	or in other circumstances where treating it as [=scrollable overflow=]
	would be useful to the user.
	[[!CSS-OVERFLOW-3]]

	<wpt>
	hanging-punctuation/hanging-scrollable-001.html
	white-space/white-space-intrinsic-size-019.html
	white-space/white-space-intrinsic-size-020.html
	</wpt>

	In some cases, a glyph at the end of a line
	can <dfn>conditionally hang</dfn>:
	it [=hangs=] only if it does not otherwise fit in the line prior to justification.
	It is not considered when measuring the line’s contents for fit;
	however, any part of it that does not fit
	is considered to [=hang=].
	Glyphs that [=conditionally hang=] are not taken into account
	when computing [=min-content sizes=]
	and any sizes derived thereof,
	but they are taken into account for [=max-content sizes=]
	and any sizes derived thereof.

	<wpt>
	white-space/white-space-intrinsic-size-013.html
	white-space/white-space-intrinsic-size-014.html
	white-space/white-space-intrinsic-size-017.html
	</wpt>

	Non-zero inline-axis borders or padding between
	a [=hang=]able glyph and the edge of the line prevent the glyph from hanging.
	For example, a period at the end of an inline box with end padding
	does not [=hang=] at the end edge of a line.

	Multiple adjacent glyphs can hang together,
	however specific limits on how many are allowed to hang may be specified
	(e.g. at most one punctuation character may [=hang=] at each edge of the line).

<h4 id="hanging-punctuation-property" caniuse="css-hanging-punctuation" oldids="hanging-punctuation">
Hanging Punctuation: the 'hanging-punctuation' property</h4>

	<wpt title="
		This section has spotty test coverage.
		All values have tests.

		Missing tests:
		* No test of Animation type.
		* Affects intrinsic sizing
		* each value has a test, and checks with some characters, but there isn’t a test for every relevant unicode character
		* it is not considered when measuring the line’s contents for […] alignment
		* it is not considered when measuring the line’s contents for […] justification
		* Non-zero inline-axis borders or padding between a hangable mark and the edge of the line prevent the mark from hanging
		* At most one punctuation character may hang at each edge of the line.
		* should be treated as ink overflow"></wpt>

	<pre class="propdef">
	Name: hanging-punctuation
	Value: none | [ first || [ force-end | allow-end ] || last ]
	Initial: none
	Applies to: text
	Inherited: yes
	Canonical order: <abbr title="follows order of property value definition">per grammar</abbr>
	Computed value: specified keyword(s)
	Animation type: discrete
	</pre>

	<wpt>
	inheritance.html
	parsing/hanging-punctuation-valid.html
	parsing/hanging-punctuation-invalid.html
	hanging-punctuation/hanging-punctuation-inline-001.html
	</wpt>

	This property determines whether a punctuation mark,
	if one is present,
	[=hangs=] and may be placed outside the line box (or in the indent)
	at the start or at the end of a line of text.

	Note: If there is not sufficient padding on the
	block container, 'hanging-punctuation' can trigger overflow.</p>

    Values have the following meanings:

	<dl dfn-for=hanging-punctuation dfn-type=value>
		<dt><dfn>none</dfn>
		<dd>
			No punctuation character is made to [=hang=].

		<dt><dfn>first</dfn>
		<dd>
			An opening bracket or quote at the start
			of the [[CSS2/selector#first-line-pseudo|first formatted line]]
			of an element [=hangs=].
			This applies to all characters in the Unicode categories Ps, Pf, Pi
			plus the ASCII quote marks U+0027 ' APOSTROPHE and U+0022 " QUOTATION MARK.

			<wpt>
			hanging-punctuation/hanging-punctuation-first-001.xht
			</wpt>

		<dt><dfn>last</dfn>
		<dd>
			A closing bracket or quote at the end
			of the last formatted line of an element [=hangs=].
			This applies to all characters in the Unicode categories Pe, Pf, Pi
			plus the ASCII quote marks U+0027 ' APOSTROPHE and U+0022 " QUOTATION MARK.

			<wpt>
			hanging-punctuation/hanging-punctuation-last-001.xht
			</wpt>

		<dt><dfn>force-end</dfn>
		<dd>
			A [=stop or comma=] at the end of a line [=hangs=].

			<wpt>
			hanging-punctuation/hanging-punctuation-force-end-001.xht
			</wpt>

		<dt><dfn>allow-end</dfn>
		<dd>
			A [=stop or comma=] at the end of a line [=conditionally hangs=].

			<wpt>
			hanging-punctuation/hanging-punctuation-allow-end-001.xht
			</wpt>
	</dl>

	At most one punctuation character may [=hang=] at each edge of the line.

	<dfn lt="stop or comma">Stops and commas</dfn> allowed to [=hang=] include:
	<table class="data">
		<tr><td>U+002C <td>&#x002C; <td>COMMA
		<tr><td>U+002E <td>&#x002E; <td>FULL STOP
		<tr><td>U+060C <td>&#x060C; <td>ARABIC COMMA
		<tr><td>U+06D4 <td>&#x06D4; <td>ARABIC FULL STOP
		<tr><td>U+3001 <td>&#x3001; <td>IDEOGRAPHIC COMMA
		<tr><td>U+3002 <td>&#x3002; <td>IDEOGRAPHIC FULL STOP
		<tr><td>U+FF0C <td>&#xFF0C; <td>FULLWIDTH COMMA
		<tr><td>U+FF0E <td>&#xFF0E; <td>FULLWIDTH FULL STOP
		<tr><td>U+FE50 <td>&#xFE50; <td>SMALL COMMA
		<tr><td>U+FE51 <td>&#xFE51; <td>SMALL IDEOGRAPHIC COMMA
		<tr><td>U+FE52 <td>&#xFE52; <td>SMALL FULL STOP
		<tr><td>U+FF61 <td>&#xFF61; <td>HALFWIDTH IDEOGRAPHIC FULL STOP
		<tr><td>U+FF64 <td>&#xFF64; <td>HALFWIDTH IDEOGRAPHIC COMMA
	</table>

    The UA may include other characters as appropriate.

	Note: The CSS Working Group would appreciate if UAs including
	other characters would <a href="#status">inform the working group</a>
	of such additions.

	<div class="example">
		The ''allow-end'' and ''force-end'' are two variations
		of hanging punctuation used in East Asia.

		<div>
			<figure class="sidefigure">
				<img src="images/hanging-punctuation-allow-end.png"
				     width="202" height="51"
				     alt="hanging-punctuation: allow-end">
			</figure>

			<pre highlight="css">
				p {
				  text-align: justify;
				  hanging-punctuation: allow-end;
				}
			</pre>

			<figure class="sidefigure">
				<img src="images/hanging-punctuation-force-end.png"
				     width="202" height="51"
				    alt="hanging-punctuation: force-end">
			</figure>

			<pre highlight="css">
				p {
				  text-align: justify;
				  hanging-punctuation: force-end;
				}
			</pre>
		</div>

		The punctuation at the end of the first line for ''allow-end''
		does not hang, because it fits without hanging.
		However, if ''force-end'' is used, it is forced to hang.
		The justification measures the line without the hanging punctuation.
		Therefore when the line is expanded, the punctuation is pushed outside the line.
	</div>

<h3 id="bidi-linebox">
Bidirectionality and Line Boxes</h3>

	<wpt title="This section lacks tests."></wpt>

	The <a spec=css-writing-modes-4>start</a>
	and <a spec=css-writing-modes-4>end</a> sides of a line box
	are determined by the [=inline base direction=] of the line box.
	Although they usually match,
	the [=inline base direction=] of a [=line box=]
	is distinct from the [=inline base direction=]
	of the [=containing block=] or the [=bidi paragraph=].
	The [=line box=]’s [=inline base direction=] affects
	'text-align-all', 'text-align-last', 'text-indent', and 'hanging-punctuation'--
	i.e. the position and alignment of its contents with respect to its edges.
	It does not affect the formatting or ordering of inline content
	(which is controlled by the <a href="https://www.unicode.org/reports/tr9/"><cite>Unicode Bidirectional Algorithm</cite></a>
	as applied by <a href="https://www.w3.org/TR/css-writing-modes-3/"><cite>CSS Writing Modes</cite></a>
	[[!UAX9]]
	[[CSS-WRITING-MODES-4]]).


	In most cases, a [=line box=]’s [=inline base direction=]
	is given by its [=containing block=]’s computed 'direction'.
	However,
	if its [=containing block=] has ''unicode-bidi: plaintext''
	[[!CSS-WRITING-MODES-4]]:

	<ul>
		<li>
			If the [=bidi paragraph=] to which the [=line box=] belongs
			(that is, the [=bidi paragraph=] for which the line box holds content)
			has strong directionality,
			the line box’s [=inline base direction=] is that direction.

		<li>
			If the [=line box=] is empty
			(i.e. contains no [=atomic inlines=] or
			characters other than the newline character, if any)
			or otherwise has no strong directionality
			(contains only weak or neutral characters),
			its [=inline base direction=] is taken
			from the preceding line box (if any),
			or, if this is the first line box in the containing block,
			from the 'direction' property of the containing block.
			(This can result in an RTL line box whose contents have an LTR base direction.)
	</ul>

	<div class="example">
		In the following example,
		assuming the <code>&lt;block&gt;</code>
		is a start-aligned preformatted block
		(''display: block; white-space: pre; text-align: start''),
		every other line is right-aligned:

		<xmp dir=auto highlight=html>
			<block style="unicode-bidi: plaintext">
			français
			فارسی
			français
			فارسی
			français
			فارسی
			</block>
		</xmp>
	</div>


	<div class="example">
		Because neutral characters (such as punctuation)
		and isolated runs are skipped
		when <a href="http://unicode.org/reports/tr9/#P2">finding the inline base direction of a plaintext bidi paragraph</a>,
		the line box in the following example will be left-to-right
		(and thus left-aligned given ''text-align: start''),
		as dictated by the first strong character, ‘h’:

		<xmp highlight=html>
			<para style="display: block; direction: rtl; unicode-bidi:plaintext">
			“<quote style="unicode-bidi:plaintext">שלום!</quote>”, he said.
			</para>
		</xmp>
	</div>

	<div class="example">
		<xmp highlight=html>
			<textarea style="direction: rtl; unicode-bidi:plaintext">

			Hello!

			</textarea>
		</xmp>

		Because of ''unicode-bidi: plaintext'',
		the “Hello!” is typeset LTR
		(i.e. with the exclamation mark on the right side)
		and left-aligned,
		ignoring the containing block’s RTL 'direction'.
		This makes the empty line following it LTR as well,
		which means that a caret on that line should appear at its left edge.
		The empty first line, however, is right-aligned:
		having no preceding line,
		it assumes the RTL direction of its containing block.
	</div>

<h2 class="no-num" id="order">
Appendix A:
Text Processing Order of Operations</h2>

	<wpt title="Tests probably not needed for this section, as it is excercised through the rest of the specificaiton."></wpt>

	<em>This appendix is normative.</em>

	The following list defines the order of text operations.
	(Implementations are not bound to this order as long as the resulting layout is the same.)

	<ol>
		<li>
			[[#white-space-phase-1|white space processing]] part I (pre-wrapping)

		<li>
			[[#transforming|text transformation]]

		<li>
			[[css-writing-modes-4#text-combine-upright|text combination]] [[!CSS-WRITING-MODES-4]]

		<li>
			[[css-writing-modes-4#text-orientation|text orientation]] [[!CSS-WRITING-MODES-4]]

		<li>
			[=wrapping|text wrapping=] while applying per line:

			* [[#text-indent-property|indentation]]
			* [[css-writing-modes-4#text-direction|bidirectional reordering]] [[!CSS2]] / [[!CSS-WRITING-MODES-4]]
			* [[#white-space-phase-2|white space processing]] part II
			* <a href="https://www.w3.org/TR/css-fonts-3/">font/glyph selection and positioning</a> [[!CSS-FONTS-3]]
			* 'letter-spacing' and 'word-spacing'
			* [[#hanging-punctuation-property|hanging punctuation]]

		<li>
			[[#justification|justification]]
			(which may affect glyph selection and/or text wrapping, looping back into that step)

		<li>[[#text-align-property|text alignment]]
	</ol>

	<wpt>
	letter-spacing/letter-spacing-bidi-003.xht
	</wpt>

<h2 class="no-num" id="plaintext">
Appendix B:
Conversion to Plaintext</h2>

	<wpt title="This section lacks tests."></wpt>

	<em>This appendix is normative</em> for the purpose of plaintext copy-paste operations.

	<!--
		https://lists.w3.org/Archives/Public/www-style/2016Oct/0115.html
		https://lists.w3.org/Archives/Public/public-editing-tf/2016Apr/0005.html
	-->

	When a CSS-rendered document is converted to a plaintext format,
	it is expected that:

	<ul>
		<li>
			The 'text-transform' property has no effect.

		<li>
			[[#white-space-phase-1]] is applied
			and any sequence of [=collapsible=] [=white space=]
			at the beginning of a [=block=]
			or immediately following a [=forced line break=]
			is removed.
	</ul>

<h2 class="no-num" id="default-stylesheet">
Appendix C:
Default UA Stylesheet</h2>

	<wpt title="Tests not needed for this section."></wpt>

	<em>This appendix is informative,</em>
	and is to help UA developers to implement a default stylesheet for HTML,
	but UA developers are free to ignore or modify as appropriate.

	<div class="example">
		<pre highlight=css>
			/* make option elements align together */
			option { text-align: match-parent; }
		</pre>
	</div>
	<!--
		Remove once https://github.com/whatwg/html/issues/6538 has been closed
	-->

<h2 class="no-num" id="script-groups">
Appendix D:
Scripts and Spacing</h2>

	<wpt title="
		Tests not needed for this section:
		these are definitions,
		they get tested through their application,
		not by themselves."></wpt>

	<em>This appendix is normative.</em>

	Typographic behavior varies somewhat by language,
	but varies drastically by writing system.
	This appendix categorizes some common [=Unicode script|scripts=] in Unicode 6.0
	according to their justification and spacing behavior.
	Category descriptions are descriptive, not prescriptive;
	the determining factor is the prioritization of [=justification opportunities=].

	<dl>
		<dt><dfn>block scripts</dfn>
		<dd>
			CJK and by extension all Wide characters
			(see <a href="https://www.unicode.org/reports/tr11/"><cite>East Asian Width</cite></a> [[!UAX11]]).
			The following [=Unicode scripts=] are included:
			Bopomofo, Han, Hangul, Hiragana, Katakana, and Yi.
			Characters of the [=East Asian Width property=]
			<code>Wide</code> and <code>Fullwidth</code> are also included,
			but <code>Ambiguous</code> characters are included
			only if the [=writing system=] is
			<a for=writing-system>Chinese</a>,
			<a for=writing-system>Korean</a>,
			or <a for=writing-system>Japanese</a>.

		<dt><dfn>clustered scripts</dfn>
		<dd>
			Clustered scripts have discrete units
			and break only at word boundaries,
			but do not use visible word separators.
			They prioritize stretching spaces,
			but comfortably admit inter-character spacing for justification.
			The clustered scripts include,
			but are not limited to,
			the following [=Unicode scripts=]:
			Khmer,
			Lao,
			Myanmar,
			New Tai Lue,
			Tai Le,
			Tai Tham,
			Tai Viet,
			Thai

		<dt><dfn lt="cursive script">cursive scripts</dfn>
		<dd>
			Cursive scripts do not admit gaps
			between their letters for either justification or 'letter-spacing'.
			The following [=Unicode scripts=] are included:
			Arabic,
			Mandaic,
			Mongolian,
			N’Ko,
			Phags Pa,
			Syriac

			Note: Indic scripts with baseline connectors
			(such as Devanagari and Gujarati)
			<em>are not</em> considered [=cursive scripts=],
			and <em>do</em> admit such gaps
			between [=typographic character units=].
			See <a href="https://www.w3.org/TR/ilreq/"><cite>Indic Layout Requirements</cite></a>.
			[[ILREQ]]
	</dl>

	User agents should update this list
	as they update their Unicode support
    to handle as-yet-unencoded cursive scripts in future versions of Unicode,
    and are encouraged to ask the CSSWG to update this spec accordingly.

<h2 id="character-properties" class="no-num">
Appendix E:
Characters and Properties</h2>

	<wpt title="This section lacks tests."></wpt>

	<em>This appendix is normative.</em>

	Unicode defines four code point-level properties
	that are referenced in CSS typesetting:

	<dl export>
		<dt><dfn lt="Unicode East Asian Width|East Asian Width property"><a href="http://www.unicode.org/reports/tr11/#Definitions">East Asian width property</a></dfn>
		<dd>
			Defined in <cite>Unicode Standard Annex #11</cite> [[!UAX11]] and given as the <code>East_Asian_Width</code> property
			in the <a href="https://www.unicode.org/reports/tr44/"><cite>Unicode Character Database</cite></a>
			[[!UAX44]].

		<dt><dfn lt="Unicode General Category|Unicode category|General Category"><a href="http://www.unicode.org/reports/tr44/#General_Category_Values">general category</a></dfn>
		<dd>
			Defined in <cite>Unicode Standard Annex #44</cite> [[!UAX44]] and given as the <code>General_Category</code> property
			in the <a href="https://www.unicode.org/reports/tr44/"><cite>Unicode Character Database</cite></a>
			[[!UAX44]].

		<dt><dfn lt="Unicode Script|Script property"><a href="http://www.unicode.org/reports/tr24/#Values">script property</a></dfn>
		<dd>
			Defined in <cite>Unicode Standard Annex #24</cite> [[!UAX24]] and given as the <code>Script</code> property
			in the <a href="https://www.unicode.org/reports/tr44/"><cite>Unicode Character Database</cite></a>
			[[!UAX44]].
			(UAs must include any ScriptExtensions.txt assignments in this mapping.)

		<dt><dfn lt="Unicode Vertical Orientation|Vertical Orientation"><a href="http://www.unicode.org/reports/tr50/">Vertical Orientation</a></dfn>
		<dd>
			Defined in <cite>Unicode Standard Annex #50</cite> [[!UAX50]] as the Vertical_Orientation property
			in the <a href="https://www.unicode.org/reports/tr44/"><cite>Unicode Character Database</cite></a>
			[[!UAX44]].
	</dl>

	Unicode defines properties for individual code points,
	but sometimes it is necessary to determine the properties
	of a [=typographic character unit=].
	For the purposes of CSS Text,
	the properties of a [=typographic character unit=] are given
	by the base character of its first [=grapheme cluster=]--
	except in two cases:

	<ul>
		<li>
			[=Grapheme clusters=] formed with an Enclosing Mark
			(<code>Me</code>)
			of the Common script
			are considered to be Other Symbols
			(<code>So</code>)
			in the Common script.
			They are assumed to have the same Unicode properties
			as the replacement character (U+FFFD).

		<li>
			[=Grapheme clusters=] formed with a Space Separator
			(<code>Zs</code>)
			as the base
			are considered to be Modifier Symbols
			(<code>Sk</code>).
			They are assumed to have the same East Asian Width property as the base,
			but take their other properties
			from the first combining character in the sequence.
	</ul>

<!-- CUT SEGMENT BREAK TRANSFORM
<h2 id="space-discard-set" class="no-num">
Appendix F:
Space-Discarding Unicode Characters</h2>

	<em>This appendix is normative.</em></p>

	Characters belonging to the <dfn>space-discarding character set</dfn>
	bias adjacent [=segment breaks=] towards
	being discarded rather than being transformed into U+0020 SPACE
	when collapsing white space, see [[#line-break-transform]].
	Characters from the following blocks in Unicode 13.0 [[UNICODE]]
	are considered part of the [=space-discarding character set=]:

	<table class=data>
	<caption>Space-discarding Unicode Bocks</caption>
	<thead>
		<tr>
		<th>Codepoint Range
		<th>Block Name
	<tbody>
		<tr>
			<td>U+2E80..U+2EFF
			<td>CJK Radicals Supplement
		<tr>
			<td>U+2F00..U+2FDF
			<td>Kangxi Radicals
		<tr>
			<td>U+2FF0..U+2FFF
			<td>Ideographic Description Characters
		<tr>
			<td>U+3000..U+303F
			<td>CJK Symbols and Punctuation
		<tr>
			<td>U+3040..U+309F
			<td>Hiragana
		<tr>
			<td>U+30A0..U+30FF
			<td>Katakana
		<tr>
			<td>U+3130..U+318F
			<td>Kanbun
		<tr>
			<td>U+3190..U+319F
			<td>Kanbun
		<tr>
			<td>U+31C0..U+31EF
			<td>CJK Strokes
		<tr>
			<td>U+31F0..U+31FF
			<td>Katakana Phonetic Extensions
		<tr>
			<td>U+3300..U+33FF
			<td>CJK Compatibility
		<tr>
			<td>U+3400..U+4DBF
			<td>CJK Unified Ideographs Extension A
		<tr>
			<td>U+4E00..U+9FFF
			<td>CJK Unified Ideographs
		<tr>
			<td>U+A000..U+A48F
			<td>Yi Syllables
		<tr>
			<td>U+A490..U+A4CF
			<td>Yi Radicals
		<tr>
			<td>U+F900..U+FAFF
			<td>CJK Compatibility Ideographs
		<tr>
			<td>U+FE10..U+FE1F
			<td>Vertical Forms
		<tr>
			<td>U+FE30..U+FE4F
			<td>CJK Compatibility Forms
		<tr>
			<td>U+FE50..U+FE6F
			<td>Small Form Variants
		<tr>
			<td>U+FF00..U+FFEF
			<td>Halfwidth and Fullwidth Forms
		<tr>
			<td>U+1B000..U+1B0FF
			<td>Kana Supplement
		<tr>
			<td>U+1B100..U+1B12F
			<td>Kana Extended-A
		<tr>
			<td>U+1B130..U+1B16F
			<td>Small Kana Extension
		<tr>
			<td>U+20000..U+2A6DF
			<td>CJK Unified Ideographs Extension B
		<tr>
			<td>U+2A700..U+2B73F
			<td>CJK Unified Ideographs Extension C
		<tr>
			<td>U+2B740..U+2B81F
			<td>CJK Unified Ideographs Extension D
		<tr>
			<td>U+2B820..U+2CEAF
			<td>CJK Unified Ideographs Extension E
		<tr>
			<td>U+2CEB0..U+2EBEF
			<td>CJK Unified Ideographs Extension F
		<tr>
			<td>U+2F800..U+2FA1F
			<td>CJK Compatibility Ideographs Supplement
		<tr>
			<td>U+30000..U+3134F
			<td>CJK Unified Ideographs Extension G
	</table>

	For future revisions of Unicode,
	any new block whose initially-allocated contents comprise
	at least 50% codepoints belonging to the
	Han, Hiragana, Katakana, or Yi script
	shall also be considered part of the [=space-discarding character set=].
	[[UNICODE]]

	<details class="note">
		<summary>Wherefore this table of “space-discarding characters”?</summary>

		The purpose of the [[#line-break-transform|segment break transformation rules]]
		is to “unbreak” text that has been formatted
		with extra white space for source code readability,
		see [[#line-break-transform]].

		In most cases, “unbreaking” a line of text requires joining them with a space,
		but some writing systems don’t use spaces
		so such texts need to be joined without any space.
		CSS uses the characters before and after to determine
		whether to join lines with or without a space.

		For simplicity and for ease of implementation,
		the classification of characters as space-discarding or space-preserving
		is done by Unicode code block.
		Ideally, such a list would be maintained in The Unicode Standard,
		but the Unicode Technical Committee has yet
		to express any intention of taking on this task.
		[[UNICODE]]
		In the meantime, in the interest of bringing
		more of the text-processing facilities of CSS and HTML
		that are available to Western writing systems
		to Eastern writing systems as well,
		the CSSWG is maintaining this appendix
		and refining the rules in [[#line-break-transform]],
		and hopes that in the future,
		once CSS has demonstrated its viability,
		the Unicode Consortium will recognize the need for an “unbreaking” algorithm
		and take over maintenance of such.

		things that could use an unbreaking algorithm:

		* HTML/CSS
		* Markdown
		* TeX
		* text editors’ “unbreak lines” commands
	</details>
CUT SEGMENT BREAK TRANSFORM -->

<h2 id="script-tagging" class="no-num">
Appendix F:
Identifying the Content Writing System</h2>

	<wpt title="
		This section has partial test coverage.
		Each of the various properties
		that take the content language into account is tested,
		except tested on text-justification:auto,
		but probably not testable anyway.

		Missing tests:
		* if the writing system to specified to be one of the Hant, Hans, Hani, Hanb, or Bopo ISO15924 codes, then the writing system is Chinese.
		* if the writing system to specified to be one of the Jpan, Hira ISO15924 codes, then the writing system is Japanese.
		* if the writing system to specified to be one of the Kore, Hang, or Jamo ISO15924 codes, then the writing system is Korean."></wpt>

	<em>This appendix is normative.</em>

	While most languages have a preferred writing system,
	some have multiple, and
	most can also be transcribed into one or more foreign writing systems.
	As a common example, most languages have at least one Latin transcription,
	and can thus be written in the Latin writing system.
	Transcribed texts typically adopt the typographic conventions of the writing system:
	for example Japanese “romaji” and Chinese Pinyin use Latin letters and word spaces,
	and follow Latin line-breaking and justification practices accordingly.
	As another example, historical ideographic Korean
	(<code>ko-Hani</code>)
	does not use word spaces,
	and should therefore be typeset similar to Chinese
	rather than modern Korean.

<!-- Tagging the Writing System -->

	In HTML or any other [=document language=]
	using <cite>BCP47</cite> tags for identifying languages to declare the [=content language=],
	authors can disambiguate or indicate the use of an atypical writing system
	with script subtags.
	[[BCP47]]
	For example, to indicate use of the Latin writing system
	for languages which don’t natively use it,
	the <code>-Latn</code> script subtag can be added,
	e.g. <code>ja-Latn</code> for Japanese romaji.
	Other subtags exist for other writing systems,
	see ISO’s <cite>Code for the Representation of Names of Scripts</cite> and the <a href="http://unicode.org/iso15924/iso15924-codes.html">ISO15924 script tag registry</a>.
	[[ISO15924]]

	<div class="example">
		Some common/historical examples of using <cite>BCP47</cite> tags with script subtags:
		<dl>
			<dt><code>zh-Latn</code>
			<dd>Chinese, written in Latin transcription.
			<dt><code>ko-Hani</code>
			<dd>Korean, written in Hanja (Chinese ideographic characters).
			<dt><code>tr-Arab</code>
			<dd>Turkish, written in Arabic script.
			<dt><code>mn-Cyrl</code>
			<dd>Mongolian, written in Cyrillic.
			<dt><code>mn-Mong</code>
			<dd>Mongolian, written in traditional Mongolian script.
		</dl>
	</div>

	However, <cite>BCP47</cite> script subtags are not typically used
	(and are in fact discouraged)
	for languages strongly associated with a single writing system:
	instead that writing system is expected to be implied
	when no other is specified.
	[[BCP47]]
	IANA maintains a database of various languages’ most common writing system
	via the <code>Suppress-Script</code> field in its
	<a href="https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry">language subtag registry</a>
	for this purpose.

	Note: More advice on language tagging can be found in
	the <a href="https://www.w3.org/International/core/">Internationalization Working Group</a>’s
	<a href="https://www.w3.org/International/articles/language-tags/">“Language tags in HTML and XML”</a>
	and <a href="https://www.w3.org/International/questions/qa-choosing-language-tags">“Choosing a Language Tag”</a>.

<!-- Assuming the Writing System -->

	When no writing system is explicitly indicated,
	UAs should assume the most common writing system
	of the declared [=content language=]
	for language-sensitive typographic behaviors
	such as line-breaking or justification.
	However, UAs must not assume that writing system
	if the author has explicitly declared a different one.
	If the UA has no language-specific knowledge
	of a particular language and writing system combination,
	it must use the typographic conventions of the declared writing system
	(assuming the conventions of a different language if necessary),
	not the conventions of the declared language in an assumed writing system,
	which would be inappropriate to the declared writing system.

	<wpt>
	writing-system/writing-system-font-001.html
	writing-system/writing-system-text-transform-001.html
	writing-system/writing-system-segment-break-001.html
	writing-system/writing-system-line-break-001.html
	writing-system/writing-system-line-break-002.html
	</wpt>

	The full correspondence between languages and their most common writing systems
	is out of scope for this document.
	However, user agents must assume at least the following:

	<ul>
		<li>
			If the [=content language=] is Chinese and the [=writing system=] is unspecified,
			or for any [=content language=]
			if the [=writing system=] to specified to be one of the
			''Hant'',
			''Hans'',
			''Hani'',
			''Hanb'',
			or ''Bopo''
			ISO script codes,
			then the [=writing system=] is <dfn noexport for=writing-system>Chinese</dfn>.

		<li>
			If the [=content language=] is Japanese and the [=writing system=] is unspecified,
			or for any [=content language=]
			if the [=writing system=] to specified to be one of the
			''Jpan'',
			''Hrkt'',
			''Hira'',
			or ''Kana'' ISO script codes,
			then the [=writing system=] is <dfn noexport for=writing-system>Japanese</dfn>.

			<wpt>
			writing-system/writing-system-line-break-002.html
			writing-system/writing-system-segment-break-001.html
			</wpt>

		<li>
			If the [=content language=] is Korean and the [=writing system=] is unspecified,
			or for any [=content language=]
			if the [=writing system=] to specified to be one of the
			''Kore'',
			''Hang'',
			or ''Jamo''
			ISO script codes,
			then the [=writing system=] is <dfn noexport for=writing-system>Korean</dfn>.

		<li>
			The [=writing system=] is only considered
			to be <dfn noexport for=writing-system lt='known | unknown'>unknown</dfn>
			if the [=content language=] itself is unknown,
			or if it explicitly indicates an unknown writing system.

			Note: Mere omission of the [=writing system=] information
			when the [=content language=] is declared
			means the that the [=writing system=] is implied, not unknown.
	</ul>

<h2 id="small-kana" class=no-num>
Appendix G:
Small Kana Mappings</h2>

	<wpt title="
		This section has good test coverage,
		through the text-transform property."></wpt>

	<style>
		.pairs-table th {
			text-align: center;
		}
	</style>

	<em>This appendix is normative.</em>

	<div class="pairs-table">
		<table class=data>
			<caption>Small Kana Map to Full-size Kana</caption>

			<thead>
				<tr>
					<th scope=col><dfn noexport for=kana lt="small | small kana">Small</dfn>
					<th scope=col><dfn noexport for=kana lt="full-size |full-size kana">Full-size</dfn>

			<tbody title="Hiragana">
				<!-- Vowels (Hiragana) -->
				<tr>
					<td>&#x3041; U+3041
					<td>&#x3042; U+3042
				<tr>
					<td>&#x3043; U+3043
					<td>&#x3044; U+3044
				<tr>
					<td>&#x3045; U+3045
					<td>&#x3046; U+3046
				<tr>
					<td>&#x3047; U+3047
					<td>&#x3048; U+3048
				<tr>
					<td>&#x3049; U+3049
					<td>&#x304A; U+304A

				<!-- Consonant K (Hiragana) -->
				<tr>
					<td>&#x3095; U+3095
					<td>&#x304B; U+304B
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x3096; U+3096
					<td>&#x3051; U+3051
				<!--
				<tr>
					<td>
					<td>
				-->

				<!-- Consonant T (Hiragana) -->
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x3063; U+3063
					<td>&#x3064; U+3064
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->

				<!-- Consonant Y (Hiragana) -->
				<tr>
					<td>&#x3083; U+3083
					<td>&#x3084; U+3084
				<!--
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x3085; U+3085
					<td>&#x3086; U+3086
				<!--
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x3087; U+3087
					<td>&#x3088; U+3088

				<!-- Consonant W (Hiragana) -->
				<tr>
					<td>&#x308E; U+308E
					<td>&#x308F; U+308F
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->

			<tbody title="Katakana">
				<!-- Vowels (Katakana) -->
				<tr>
					<td>&#x30A1; U+30A1
					<td>&#x30A2; U+30A2
				<tr>
					<td>&#x30A3; U+30A3
					<td>&#x30A4; U+30A4
				<tr>
					<td>&#x30A5; U+30A5
					<td>&#x30A6; U+30A6
				<tr>
					<td>&#x30A7; U+30A7
					<td>&#x30A8; U+30A8
				<tr>
					<td>&#x30A9; U+30A9
					<td>&#x30AA; U+30AA

				<!-- Consonant K (Katakana) -->
				<tr>
					<td>&#x30F5; U+30F5
					<td>&#x30AB; U+30AB
				<!--
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x31F0; U+31F0
					<td>&#x30AF; U+30AF
				<tr>
					<td>&#x30F6; U+30F6
					<td>&#x30B1; U+30B1
				<!--
				<tr>
					<td>
					<td>
				-->

				<!-- Consonant S (Katakana) -->
				<!--
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x31F1; U+31F1
					<td>&#x30B7; U+30B7
				<tr>
					<td>&#x31F2; U+31F2
					<td>&#x30B9; U+30B9
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->

				<!-- Consonant T (Katakana) -->
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x30C3; U+30C3
					<td>&#x30C4; U+30C4
				<!--
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x31F3; U+31F3
					<td>&#x30C8; U+30C8

				<!-- Consonant N (Katakana) -->
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x31F4; U+31F4
					<td>&#x30CC; U+30CC
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->

				<!-- Consonant H (Katakana) -->
				<tr>
					<td>&#x31F5; U+31F5
					<td>&#x30CF; U+30CF
				<tr>
					<td>&#x31F6; U+31F6
					<td>&#x30D2; U+30D2
				<tr>
					<td>&#x31F7; U+31F7
					<td>&#x30D5; U+30D5
				<tr>
					<td>&#x31F8; U+31F8
					<td>&#x30D8; U+30D8
				<tr>
					<td>&#x31F9; U+31F9
					<td>&#x30DB; U+30DB

				<!-- Consonant M (Katakana) -->
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x31FA; U+31FA
					<td>&#x30E0; U+30E0
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->

				<!-- Consonant Y (Katakana) -->
				<tr>
					<td>&#x30E3; U+30E3
					<td>&#x30E4; U+30E4
				<!--
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x30E5; U+30E5
					<td>&#x30E6; U+30E6
				<!--
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#x30E7; U+30E7
					<td>&#x30E8; U+30E8

				<!-- Consonant R (Katakana) -->
				<tr>
					<td>&#x31FB; U+31FB
					<td>&#x30E9; U+30E9
				<tr>
					<td>&#x31FC; U+31FC
					<td>&#x30EA; U+30EA
				<tr>
					<td>&#x31FD; U+31FD
					<td>&#x30EB; U+30EB
				<tr>
					<td>&#x31FE; U+31FE
					<td>&#x30EC; U+30EC
				<tr>
					<td>&#x31FF; U+31FF
					<td>&#x30ED; U+30ED

				<!-- Consonant W (Katakana) -->
				<tr>
					<td>&#x30EE; U+30EE
					<td>&#x30EF; U+30EF
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->

			<tbody title="Half-width Katakana">
				<!-- Vowels (hwid) -->
				<tr>
					<td>&#xFF67; U+FF67
					<td>&#xFF71; U+FF71
				<tr>
					<td>&#xFF68; U+FF68
					<td>&#xFF72; U+FF72
				<tr>
					<td>&#xFF69; U+FF69
					<td>&#xFF73; U+FF73
				<tr>
					<td>&#xFF6A; U+FF6A
					<td>&#xFF74; U+FF74
				<tr>
					<td>&#xFF6B; U+FF6B
					<td>&#xFF75; U+FF75

				<!-- Consonant T (hwid Katakana) -->
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#xFF6F; U+FF6F
					<td>&#xFF82; U+FF82
				<!--
				<tr>
					<td>
					<td>
				<tr>
					<td>
					<td>
				-->

				<!-- Consonant Y (hwid Katakana) -->
				<tr>
					<td>&#xFF6C; U+FF6C
					<td>&#xFF94; U+FF94
				<!--
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#xFF6D; U+FF6D
					<td>&#xFF95; U+FF95
				<!--
				<tr>
					<td>
					<td>
				-->
				<tr>
					<td>&#xFF6E; U+FF6E
					<td>&#xFF96; U+FF96
		</table>
	</div>

	<wpt>
	text-transform/text-transform-full-size-kana-001.html
	text-transform/text-transform-full-size-kana-002.html
	text-transform/text-transform-full-size-kana-003.html
	text-transform/text-transform-full-size-kana-004.html
	text-transform/text-transform-full-size-kana-005.html
	text-transform/text-transform-full-size-kana-006.html
	text-transform/text-transform-full-size-kana-007.html
	</wpt>

<h2 id="priv-sec" class="no-num">
Privacy and Security Considerations</h2>

	<wpt title="Tests not needed for this section."></wpt>

	This specification introduces no new security considerations.

	This specification leaks the user’s installed hyphenation and line-breaking dictionaries.

<h2 class="no-num" id="acknowledgements">
Acknowledgements</h2>

	<wpt title="Tests not needed for this section."></wpt>

	This specification would not have been possible without the help from:
	Addison Phillips,
	Aharon Lanin,
	Alan Stearns,
	Ambrose Li,
	Arnold Schrijver,
	Arye Gittelman,
	Ayman Aldahleh,
	Ben Errez,
	Bert Bos,
	Chris Lilley,
	Chris Pratley,
	Chris Thrasher,
	Chris Wilson,
	Dave Hyatt,
	David Baron,
	Emilio Cobos Álvarez,
	Eric LeVine,
	Etan Wexler,
	Frank Tang,
	Håkon Wium Lie,
	IM Mincheol,
	Ian Hickson,
	James Clark,
	Javier Fernandez,
	John Daggett,
	Jonathan Kew,
	Ken Lunde,
	Laurie Anna Edlund,
	Marcin Sawicki,
	Martin Dürst,
	Martin Heijdra,
	Masafumi Yabe,
	Masayasu Ishikawa,
	Michael Jochimsen,
	Michel Suignard,
	Mike Bemford,
	Myles Maxfield,
	Nat McCully,
	Paul Nelson,
	Rahul Sonnad,
	Richard Ishida,
	Shinyu Murakami,
	Stephen Deach,
	Steve Zilles,
	Takao Suzuki,
	Tantek Çelik,
	Xidorn Quan,
	Yaniv Feinberg.

<h2 class="no-num" id="changes" oldids="recent-changes">
Changes</h2>

	<wpt title="Tests not needed for this section."></wpt>

	There have been some minor editorial changes since
	the <a href="https://www.w3.org/TR/2020/CR-css-text-3-20201222/">December 2020 Candidate Recommendation</a>.

	In addition, the following normative changes have been made:

	* Define that ''distribute'' computes to ''inter-character'', rather than merely behave the same.

	See also <a href="https://www.w3.org/TR/2020/CR-css-text-3-20201222/#changes">earlier list of changes</a>
	covering the 2020 and 2019 Working Drafts prior to that Candidate Recommendation
	and the <a href="https://drafts.csswg.org/css-text-3/issues-lc-2013">Disposition of Comments</a>
	covering all comments between 2013 and 2020.

	<wpt hidden title="Tests for the next level(s) of this specification">
	white-space/text-space-collapse-discard-001.xht
	white-space/text-space-collapse-preserve-breaks-001.xht
	white-space/text-space-trim-trim-inner-001.xht

	word-boundary/word-boundary-001.html
	word-boundary/word-boundary-002.html
	word-boundary/word-boundary-003.html
	word-boundary/word-boundary-004.html
	word-boundary/word-boundary-005.html
	word-boundary/word-boundary-006.html
	word-boundary/word-boundary-007.html
	word-boundary/word-boundary-008.html
	word-boundary/word-boundary-009.html
	word-boundary/word-boundary-010.html
	word-boundary/word-boundary-011.html
	word-boundary/word-boundary-012.html
	word-boundary/word-boundary-013.html
	word-boundary/word-boundary-014.html
	word-boundary/word-boundary-015-manual.html
	word-boundary/word-boundary-101.html
	word-boundary/word-boundary-102.html
	word-boundary/word-boundary-103.html
	word-boundary/word-boundary-104.html
	word-boundary/word-boundary-105.html
	word-boundary/word-boundary-106.html
	word-boundary/word-boundary-107.html
	word-boundary/word-boundary-108.html
	word-boundary/word-boundary-109.html
	word-boundary/word-boundary-110.html
	word-boundary/word-boundary-111.html
	word-boundary/word-boundary-112.html
	word-boundary/word-boundary-113.html
	word-boundary/word-boundary-114.html
	word-boundary/word-boundary-115.html
	word-boundary/word-boundary-116.html
	word-boundary/word-boundary-117.html
	word-boundary/word-boundary-118.html
	word-boundary/word-boundary-119.html
	word-boundary/word-boundary-120.html
	word-boundary/word-boundary-121.html
	word-boundary/word-boundary-122.html
	word-boundary/word-boundary-123.html
	word-boundary/word-boundary-124.html
	word-boundary/word-boundary-125.html
	word-boundary/word-boundary-126.html
	word-boundary/word-boundary-127.html
	word-boundary/word-boundary-128.html
	word-boundary/word-boundary-129.html
	parsing/word-boundary-detection-computed.html
	parsing/word-boundary-detection-invalid.html
	parsing/word-boundary-detection-valid.html
	parsing/word-boundary-expansion-computed.html
	parsing/word-boundary-expansion-invalid.html
	parsing/word-boundary-expansion-valid.html
	</wpt>