Overview.bs

<style media="print" type="text/css">
    img#edge { width: 80%; height: 70%;}
    dt.label { display: run-in; }
</style>

<pre class='metadata'>
Title: CSS Inline Layout Module Level 3
Shortname: css-inline
Level: 3
Status: ED
Work Status: Revising
Group: csswg
TR: https://www.w3.org/TR/css-inline/
ED: https://drafts.csswg.org/css-inline/
Previous version: https://www.w3.org/TR/2016/WD-css-inline-3-20160524/
Previous version: https://www.w3.org/TR/2015/WD-css-inline-3-20150917/
Previous version: https://www.w3.org/TR/2014/WD-css-inline-3-20141218/
Previous version: https://www.w3.org/TR/2002/WD-css3-linebox-20020515/
!Issues list: <a href="https://github.com/w3c/csswg-drafts/issues?q=is%3Aissue+is%3Aopen+label%3Acss-inline-3">CSS3 Line Layout issues in GitHub</a>
Editor: Dave Cramer, Hachette Livre, dauwhe@gmail.com, w3cid 65283
Editor: Elika J. Etemad / fantasai, Invited Expert, http://fantasai.inkedblade.net/contact, w3cid 35400
Editor: Steve Zilles, Adobe, szilles@adobe.com, w3cid 3129
Abstract: The CSS formatting model provides for a flow of elements and text inside of a container to be wrapped into lines.  The formatting of elements and text within a line, its positioning in the inline progression direction, and the breaking of lines are described in [[CSS3TEXT]].  This module describes the positioning in the block progression direction both of elements and text within lines and of the lines themselves.  This positioning is often relative to a baseline.  It also describes special features for formatting of first lines and drop caps.  It extends on the model in [[CSS2]].
Ignored Terms: line-height-shift-adjustment, text-script, after, before, alignment subtree
Link Defaults: css-fonts-3 (property) font-family, css-color-3 (property) color
At Risk: the 'initial-letters-wrap' property
</pre>

<pre class="link-defaults">
spec:css-align-3; type:dfn; text:alignment baseline
spec:css-break-3; type:dfn; text:fragment
</pre>

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

	This module defines the CSS Inline Layout model,
	replacing and extending the model as defined in CSS2.1.
	It is very much a work-in-progress, and implementers should reference CSS2.1 for now.

	The <dfn export>root inline box</dfn> is an anonymous inline box
	which is automatically generated to hold
	all of the <a>inline-level</a> contents of a <a>block container</a>
	(if it has any).
	It inherits from its parent <a>block container</a>,
	but is otherwise unstyleable.

<h2 id="line-height">
Line Heights and Baseline Alignment</h2>

	<p class="issue">This section is being rewritten. Refer to <a href="https://www.w3.org/TR/CSS2/visudet.html#line-height">section 10.8</a> of [[CSS2]] for the normative CSS definition or the <a href="https://www.w3.org/TR/2002/WD-css3-linebox-20020515/">2002 Working Draft</a> if you want pretty pictures. (But ignore the old text, half of it's wrong. We're not specifying which half, that's to be determined.)
	<strong>The CSS2 specification should be used as the guideline for implementation.</strong></p>

	Issue: The CSSWG would like to know which baseline values are necessary: if any can be dropped, or any need to be added. See GitHub issue <a href="https://github.com/w3c/csswg-drafts/issues/859">859</a>.

<h3 id="dominant-baseline-property">
Dominant Baselines: the 'dominant-baseline' property</h3>

	<pre class="propdef">
	Name: dominant-baseline
	Value: auto | text-bottom | alphabetic | ideographic | middle | central | mathematical | hanging | text-top
	Initial: normal
	Applies to: block containers, inline boxes, table rows, table columns, grid containers, and flex containers
	Inherited: yes
	Percentages: N/A
	Computed value: as specified
	</pre>

	This property specifies the <dfn>dominant baseline</dfn>,
	which is the baseline used to align the box's text and inline-level contents.
	It is also indicates the default <a>alignment baseline</a>
	of any boxes participating in <a>baseline alignment</a>
	in the box’s <a>alignment context</a>.
	Values have the following meanings:

	<dl dfn-for=dominant-baseline dfn-type=value>
		<dt><dfn>auto</dfn>
		<dd>
			Equivalent to ''dominant-baseline/alphabetic'' in <a>horizontal writing modes</a>
			and in <a>vertical writing modes</a>
			when 'text-orientation' is ''sideways'', ''sideways-right'', or ''sideways-left''.
			Equivalent to ''dominant-baseline/central'' in <a>vertical writing modes</a>
			when 'text-orientation' is ''mixed'' or ''upright''.

			However, in SVG text, the origin point of glyphs
			(used for coordinate-based glyph positioning)
			is always handled as for ''dominant-baseline/central''
			in <a>vertical writing modes</a>.

		<dt><dfn>text-bottom</dfn>
		<dd>
			Use the bottom of the em box as the baseline.

		<dt><dfn>alphabetic</dfn>
		<dd>
			Use the alphabetic baseline.

		<dt><dfn>ideographic</dfn>
		<dd>
			Match the box's ideographic character face under-side baseline to that of its parent.

		<dt><dfn>middle</dfn>
		<dd>
			Use the “middle” baseline: halfway between the alphabetic baseline and the ex-height.

		<dt><dfn>central</dfn>
		<dd>
			Use the central baseline
			(halfway between the ascent and descent).

		<dt><dfn>mathematical</dfn>
		<dd>
			Use the mathematical baseline.

		<dt><dfn>hanging</dfn>
		<dd>
			Use the hanging baseline.

		<dt><dfn>text-top</dfn>
		<dd>
			Use the top of the em box as the baseline.
	</dl>

	See [[CSS3-WRITING-MODES]] for an introduction to dominant baselines.

	Issue: Should be text-over and text-under instead of text-top and text-bottom,
	but maybe it's better not to use those terms for consistency with legacy 'vertical-align'.
	See GitHub issue <a href="https://github.com/w3c/csswg-drafts/issues/860">860</a>.

	Issue: Add <css>first</css> and <css>last</css> values.
	Note, in this property, these are combinatorial,
	whereas in the <css>align/justify-self/content</css> properties, it's singular.
	Do we want to align the syntaxes wrt hyphens vs. spaces or what?
	See GitHub issue <a href="https://github.com/w3c/csswg-drafts/issues/861">861</a>.

<h3 id="transverse-alignment">
Transverse Box Alignment: the 'vertical-align' property</h3>

	<pre class="propdef">
	Name: vertical-align
	Value: <<'baseline-shift'>> || <<'alignment-baseline'>>
	Initial: baseline
	Applies to: inline-level boxes
	Inherited: no
	Percentages: N/A
	Computed value: as specified
	</pre>

	<p>This shorthand property specifies how an inline-level box is aligned within the line.
	Values are the same as for its longhand properties, see below.

	<p class="advisement">
		Authors should use this property ('vertical-align') instead of its longhands.

<h4 id="alignment-baseline-property">
Alignment Point: 'alignment-baseline' longhand</h4>

	<pre class="propdef">
	Name: alignment-baseline
	Value: baseline | text-bottom | alphabetic | ideographic | middle | central | mathematical | text-top | bottom | center | top
	Initial: baseline
	Applies to: inline-level boxes, flex items, grid items, table cells
	Inherited: no
	Percentages: N/A
	Computed value: as specified
	</pre>

	<p>Specifies what point of an inline-level box is aligned to what point in the parent.
	Also selects the <a>alignment baseline</a> of boxes aligned with 'align-self'/'justify-self'.

	ISSUE: Clean up this prose to correctly handle alignment contexts other than inline formatting contexts.

	Values are defined below:

	For the following definitions,
	the margin box is used for atomic inlines,
	the leading box for non-replaced inlines,
	and the baselines of the box are <a lt="synthesized baseline">synthesized</a> if missing in the line-box's inline axis:

	<dl dfn-for=alignment-baseline dfn-type=value>
		<dt><dfn>baseline</dfn>
		<dd>
			Use the <a>dominant baseline</a> choice of the parent.
			Match the box's corresponding baseline to that of its parent.

		<dt><dfn>text-bottom</dfn>
		<dd>
			Match the bottom of the box to the bottom of the parent's content area.

		<dt><dfn>alphabetic</dfn>
		<dd>
			Match the box's alphabetic baseline to that of its parent.

		<dt><dfn>ideographic</dfn>
		<dd>
			Match the box's ideographic character face under-side baseline to that of its parent.

		<dt><dfn>middle</dfn>
		<dd>
			Align the vertical midpoint of the box with
			the baseline of the parent box plus half the x-height of the parent.

		<dt><dfn>central</dfn>
		<dd>
			Match the box's central baseline to the central baseline of its parent.

		<dt><dfn>mathematical</dfn>
		<dd>
			Match the box's mathematical baseline to that of its parent.

		<dt><dfn>text-top</dfn>
		<dd>
			Match the top of the box to the top of the parent's content area.
	</dl>

	For the following definitions, the <a>alignment subtree</a>
	is as defined in [[!CSS2]].

	<dl dfn-for=alignment-baseline dfn-type=value>
		<dt><dfn>top</dfn>
		<dd>
			Align the top of the aligned subtree with the top of the line box.

		<dt><dfn>center</dfn>
		<dd>
			Align the center of the aligned subtree with the center of the line box.

		<dt><dfn>bottom</dfn>
		<dd>
			Align the bottom of the aligned subtree with the bottom of the line box.
	</dl>

	SVG implementations <em>may</em> support the following aliases
	in order to support legacy content:
	<pre dfn-for=alignment-baseline dfn-type=value>
		<dfn>text-before-edge</dfn> = ''alignment-baseline/text-top''
		<dfn>text-after-edge</dfn> = ''alignment-baseline/text-bottom''
	</pre>
	These values are not allowed in the 'vertical-align' shorthand.

<h4 id="baseline-shift-property">
Alignment Shift: 'baseline-shift' longhand</h4>

	<pre class="propdef">
	Name: baseline-shift
	Value: <<length>> | <<percentage>> | sub | super
	Initial: 0
	Applies to: inline-level boxes, flex items, grid items
	<!-- table cells left out b/c CSS2.1 vertical-align values must have no effect... -->
	Inherited: no
	Percentages: refer to the used value of 'line-height'
	Computed value: absolute length, percentage, or keyword specified
	</pre>

	<p>This property specifies by how much the box is shifted up
	from its alignment point.
	It does not apply when 'alignment-baseline' is ''alignment-baseline/top'' or ''alignment-baseline/bottom''.

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

	Values have the following meanings:

	<dl dfn-for="baseline-shift" dfn-type=value>
		<dt><dfn><<length>></dfn>
		<dd>Raise (positive value) or lower (negative value) by the specified length.

		<dt><dfn><<percentage>></dfn>
		<dd>Raise (positive value) or lower (negative value) by the specified percentage of the 'line-height'.

		<dt><dfn>sub</dfn>
		<dd>Lower by the offset appropriate for subscripts of the parent’s box.
		(The UA should use the parent’s font data to find this offset whenever possible.)

		<dt><dfn>super</dfn>
		<dd>Raise by the offset appropriate for superscripts of the parent’s box.
		(The UA should use the parent’s font data to find this offset whenever possible.)
	</dl>

	<p>User agents <em>may</em> additionally support the keyword <dfn for=baseline-shift>baseline</dfn>
	as computing to ''0''
	if is necessary for them to support legacy SVG content.

	Issue: We would prefer to remove this, and are looking for feedback from SVG user agents as to whether it's necessary.

<h2 id="initial-letter-styling">
<!--<a name="Initial"></a>-->
Initial Letters</h2>

	<p class="issue">The editors would appreciate any examples of drop initials in non-western scripts, especially Arabic and Indic scripts.</p>

<h3 id="initial-letter-intro">
<!--<a name="DropInitial"></a>-->
An Introduction to Initial Letters</h3>

	<em>This section is non-normative.</em>

	Large, decorative letters have been used to start new sections of text since before the invention of printing.
	In fact, their use predates lowercase letters entirely.

<h4 id="drop-initial">
Drop Initial</h4>

	A <dfn>dropped initial</dfn> (or “drop cap”)
	is a larger-than-usual letter at the start of a paragraph,
	with a baseline at least one line lower than the first baseline of the paragraph.
	The size of the drop initial is usually indicated by how many lines it occupies.
	Two- and three-line drop initials are very common.

	<figure>
		<img src="images/Dropcap-E-acute-3line.png" width="480"
		     alt="3-line drop cap with E Acute"  >
		<figcaption>
			Three-line drop initial with E acute.
			Since the cap-height of the drop initial aligns with the cap-height of the main text,
			the accent extends above the paragraph.
		</figcaption>
	</figure>

	The exact size and position of a <a>dropped initial</a>
	depends on the alignment of its glyph.
	Reference points on the drop cap must align precisely
	with reference points in the text.
	The alignment constraints for drop initials depend on the writing system.

	In Western scripts, the top reference points are
	the cap height of the initial letter and of the first line of text.
	The bottom reference points are
	the alphabetic baseline of the initial letter
	and the baseline of the Nth line of text.
	<a href="#f2">Figure 2</a> shows a simple two-line drop cap, with the relevant reference lines marked.

	<figure id="f2">
		<img src="images/Dropcap-lines.png" width="600"
		     alt="drop cap showing alignment">
		<figcaption>Two-line drop cap showing baselines (green lines), cap-height (red line), and ascender (cyan line).</figcaption>
	</figure>

	In Han-derived scripts, the initial letter extends
	from the <a>block-start</a> edge of the glyphs on the first line
	to the <a>block-end</a> edge of the glyphs on the Nth line.

	<figure>
		<img src="images/Initial-2line-JapaneseVertical六.png" width="480"
		     alt="Japanese Vertical Initial">
		<figcaption>Two-line drop initial in vertical writing mode</figcaption>
	</figure>

	In certain Indic scripts,
	the top alignment point	is the hanging baseline,
	and the bottom alignment point is the text-after-edge.

	<figure>
		<img src="images/Devangari-Initial.png" width="480"
		     alt="Devangari initial letter">
		<figcaption>Devangari <a>initial letter</a> aligned with hanging baseline. Alignment points shown in red.</figcaption>
	</figure>


<h4 id="sunk-initial">
Sunken Initial Letters</h4>

	Some styles of drop initials do not align with the first line of text.
	A <dfn>sunken initial</dfn> (or “sunken cap”)
	both sinks below the first baseline,
	and extends above the first line of text.

	<figure>
		<img src="images/SunkenCapA.png" width="480"
		     alt="sunken drop initial">
		<figcaption>Sunken cap. The letter drops two lines, but is the size of a three-line initial letter.</figcaption>
	</figure>

<h4 id="raise-initial">
Raised Initial Letters</h4>

	A <dfn>raised initial</dfn> (often called a “raised cap” or “stick-up cap”) “sinks” to the first text baseline.

	Note: A proper raised initial has several advantages over
	simply increasing the font size of a first letter.
	The line spacing in the rest of the paragraph will not be altered,
	but text will still be excluded around large descenders.
	And if the size of raised initial is defined to be an integral number of lines,
	implicit baseline grids can be maintained.

	<figure>
		<img src="images/RaisedCap.png" width="480"
		     alt="raised cap">
		<figcaption>Raised cap. The initial letter is the size of a 3-line initial, but does not drop.</figcaption>
	</figure>

<h3 id="selecting-drop-initials">Selecting Initial Letters</h3>

	Initial letters are typically a single letter, although
	they may include punctuation or a sequence of characters which
	are perceived by the user to be a single typographic unit.
	The <code>::first-letter</code> pseudo-element, as defined in [[SELECT]],
	can be used to select the character(s) to be formatted as <a>initial letters</a>.

	Authors who need more control over which characters are included in an initial letter,
	or who want to apply initial-letters formatting to replaced elements or multiple words
	can alternately apply the 'initial-letters' property to the first inline-level child of a block container.

	<div class="example">
	<pre>
		&lt;p>This paragraph has a dropped “T”.
		&lt;p>&lt;img alt="H" src="illuminated-h.svg">ere we have an illuminated “H”.
		&lt;p>&lt;span>Words may also&lt;/span> be given initial letter styling at the beginning of a paragraph.
	</pre>

	<pre>
		::first-letter, /* style first paragraph's T */
		img, /* style illuminated H */
		span /* style phrase inside span */
		{ initial-letters: 2; }
	</pre>
	</div>

<h4 id="initial-letter-punctuation">Initial Letter Punctuation</h4>

	Since ''::first-letter'' selects punctuation before or after the first letter,
	these characters are included in the initial-letters when ''::first-letter'' is used.

	<figure>
		<img src="images/initial-letter-punctuation-quote.png" width="604"
		     alt="Paragraph showing both opening quote and first letter set as three-line drop cap">
		<figcaption>The <code>::first-letter</code> pseudo-element selects the quotation mark as well as the “M.”</figcaption>
	</figure>

	Issue: Should there be a way to opt out of this behavior? See <a href="https://github.com/w3c/csswg-drafts/issues/310">Github Issue 310</a>.

<h3 id="sizing-drop-initials">
Creating Initial Letters: the 'initial-letters' property</h3>

	<pre class="propdef">
	Name: <dfn id="propdef-initial-letters">initial-letters</dfn>
	Value: normal | [<<number>> <<integer>>?]
	Initial: normal
	Applies to: certain inline-level boxes and <css>::first-letter</css> and inside <css>::marker</css> boxes (<a href="#first-most-inline-level">see prose</a>)
	Inherited: no
	Percentages: N/A
	Computed value: as specified
	</pre>

	ISSUE: Renaming this property (and the others in this section)
	is currently <a href="https://github.com/w3c/csswg-drafts/issues/2950">under discussion</a>.

	This property specifies styling for dropped, raised, and sunken initial letters.
	It takes the following values:

	<dl dfn-for=initial-letters dfn-type=value>
		<dt><dfn>normal</dfn>
		<dd>
			No special initial-letters effect. Text behaves as normal.

		<dt><dfn><<number>></dfn>
		<dd>
			This first argument defines the size of the initial letter
			in terms of how many lines it occupies.
			Values less than one are invalid.

		<dt><dfn><<integer>></dfn>
		<dd>
			This optional second argument 
			defines the number of lines the initial letter should <dfn>sink</dfn>.
			Values less than one are invalid.
			If omitted, it duplicates the first argument,
			floored to the nearest positive whole number.
	</dl>

	An <dfn lt="initial letter | initial letter box">initial letter</dfn> is
	an <a>in-flow</a> box
	to which 'initial-letters' applies and is not ''initial-letters/normal'';
	this triggers the special layout considerations described below.

	<div class="example">
		Here are some examples of 'initial-letters' usage:

		<dl>
			<dt>''initial-letters: 3''
			<dt>(''initial-letters: 3 3'')
			<dd>
				Represents a <a>dropped initial</a> 3 lines high, 3 lines deep.

				<img src="images/InitialLetter33.png" width="360"
				     alt="3 lines high, 3 lines deep">

			<dt>''initial-letters: 3 2''
			<dd>
				Represents a <a>sunken initial</a> 3 lines high, 2 lines deep.

				<img src="images/InitialLetter32.png" width="360"
					alt="3 lines high, 2 lines deep">

			<dt>''initial-letters: 3 1''
			<dd>
				Represents a <a>raised initial</a> 3 lines high, 1 line deep.

				<img src="images/InitialLetter31.png" width="360"
				     alt="3 lines high, 1 line deep">

			<dt>''initial-letters: 2.51 3''
			<dd>
				The size of the initial letter does not have to be an integral number of lines.
				In this case only the bottom aligns.

				<img src="images/non-integer-initial.png" width="360"
				     alt="Non-integral initial letter that only aligns at base">
		</dl>
	</div>

	<div class="example">
		The following code will create a 2-line dropped initial letter at the beginning of each paragraph:
		<pre>p::first-letter { initial-letters: 2; }</pre>
	</div>

<h4 id="first-most-inline-level">
Applicability</h4>

	To give authors more control over which characters can be styled as an <a>initial letter</a>
	and to allow the possibility of multi-character <a>initial letters</a>
	(such as for first word or first phrase styling),
	the 'initial-letters' property applies not just
	to the CSS-defined ''::first-letter'' pseudo-element,
	but also to
	''list-style-position/inside''-positioned ''::marker'' pseudo-elements and
	inline-level boxes
	that are placed at the start of the first line.
	Specifically, 'initial-letters' applies to
	any <a>inline-level box</a>--
	including any such ''::first-letter'' or ''::marker'' box--
	that is the first child of its parent box
	and whose ancestors (if any) that are descendants of its <a>containing block</a>
	are all first-child <a>inline boxes</a>
	that have a <a lt="computed value">computed</a> 'initial-letters' value
	of ''initial-letters/normal''.

	<div class="example">
		For example,
		the <code>&lt;span></code>, <code>&lt;em></code>, and <code>&lt;b></code> elements
		in the following example are
		"first-most inline-level descendants" of the <code>&lt;p></code>,
		but the <code>&lt;strong></code> element
		is not:
		
		<xmp>
			<p><span><em><b>This phrase</b> is styled</em> <strong>specially</strong>. &hellip;</span>
		</xmp>
		
		If we apply the following rules:
		
		<pre>
			em { initial-letters: 2; }
			b { initial-letters: 3; }
		</pre>
		
		The result might be rendered as
		
		<pre>
			[ADD RENDERING HERE]
			THIS PHRASE IS STYLED specially. &hellip;
		</pre>
		
		(Note that the styling on <code>&lt;b></code>
		is ignored,
		as it has an ancestor already styled as an <a>initial letter</a>.)
	</div>

	If 'initial-letters' is applied to an <a>inline-level box</a>
	that is not positioned at the start of the line due to bidi reordering
	or which is otherwise preceded by other <a>inline-level</a> content,
	its <a>used value</a> is ''initial-letters/normal'',
	and it is not formatted as an <a>initial letter</a>.

	Note: The 'initial-letters' property cannot apply to any element
	whose 'float' is not ''float/none'' or 'position' is not ''static'',
	because these values cause its 'display' to compute to ''block''.

	The effect of the 'initial-letters' property is undefined
	on children of <a>ruby</a> base container boxes
	and on <a>ruby</a> container boxes.

<h4 id="initial-letter-properties">
Properties</h4>

	All properties that apply to an <a>inline box</a>
	also apply to an <a>initial letter</a> 
	(unless it is an <a>atomic inline</a>,
	in which case the set of properties that apply to an <a>atomic inline</a> apply)
	except for 'vertical-align' and its <a>sub-properties</a>,
	'font-size', and 'line-height'.
	<!-- Basically, any properties defined in css-inline
	except those specific to initial letters,
	so keep this list updated as we add things to this spec. -->
	Additionally, all of the <a>sizing properties</a>
	and 'box-sizing' also apply to <a>initial letters</a>.

<h4 id="initial-letter-model">
Layout Model</h4>

	An <a>initial letter</a> is laid out following the steps outlined below:

	<ol>
		<li>
			Find the used font size based on its 'initial-letters' size,
			'initial-letters-align' alignment points,
			and font metrics.
			Note that no layout is required in this step.
			The font size used for sizing the <a>initial letter</a> contents
			<em>does not</em> affect its computed 'font-size' property
			(and therefore has no effect on the computation of ''em'' length values, etc.).

		<li>
			Size the <a>initial letter</a>’s content box.

			If its <a>width</a>/<a>height</a> is definite,
			use that value
			(clamped as required by the <a>min size</a> and <a>max size</a> properties,
			and handling 'box-sizing' as required)
			for that dimension of the box.
			In the case of a definite <a>inline size</a>,
			'text-align' is honored
			for aligning the contents of the <a>initial letter</a> within its box
			in the <a>inline axis</a>
			(using its <a>inline-axis</a> bearings as usual,
			not the bounding box of its glyph outlines).
			In the case of a definite <a>block size</a>,
			'align-content' is honored
			for aligning its contents in the <a>block axis</a>
			(using its <a>block-axis</a> bearings,
			synthesizing them if needed).

			Otherwise
			it is considered to have an <a>automatic size</a> in that dimension
			and is sized and positioned to coincide with
			the smallest rectangle that would include
			the bounding boxes of all its glyphs--
			excluding any that <a spec="css-text-3">hang</a>
			(see 'hanging-punctuation')--
			as well as the margin boxes of any atomic inlines it contains.

			ISSUE: Should the hanging punctuation be included in the box instead
			(so that the box is drawn around the punctuation when it is made visible through borders/background),
			but rather only excluded when positioning the box
			(so that the initial letter remains flush,
			with the hanging punctuation properly hanging)?
			See <a href="https://github.com/w3c/csswg-drafts/issues/310">discussion</a>.

		<li>
			In the <a>inline axis</a>,
			the initial letter's margin box is placed at the start edge of the line.
			If it is a non-atomic inline
			with an <a lt="automatic size">automatic</a> <a>inline size</a>
			and has no padding or borders,
			it is negatively offset
			by the distance from the start edge of its content box
			to the point in the content that would have been placed
			at the start edge of the containing block
			if it had ''initial-letters: none''.

			In the <a>block axis</a>,
			the initial letter is anchored to the dominant baseline
			of the <a>first formatted line</a>,
			positioned with respect to that baseline
			such that it would sink the number of lines
			specified by 'initial-letters'’s second argument
			if its containing block held only
			the <a>initial letter</a> itself
			followed by an infinite sequence of plain text
			as the direct contents of its <a>root inline box</a>.
			
			<figure>
				<img src="images/infinite-text.png" width="300"
		     alt="text underlay shows how initial letter alignment is not affected
		     by the content of the spanned lines">
			</figure>

		<li>
			Exclude content within the inline letter's margin box
			according to 'initial-letters-wrap'.
	</ol>

<h4 id="initial-letter-box">
Content-box Size, Margins, Borders, and Padding</h4>

	Initial letters can be styled with margins, padding, and borders
	just like any other box.
	Unless 'initial-letters-align' is ''initial-letters-align/border-box'',
	its vertical alignment and sizing are not affected;
	however the effective exclusion area is
	(and corresponds to the margin area).

	When padding and borders are zero,
	the initial letter may be kerned;
	see below.

<h3 id="aligning-initial-letter">
Alignment of Initial Letters: the 'initial-letters-align' property</h3>

	As mentioned earlier, the alignment of initial letters
	depends on the script used.
	The 'initial-letters-align' property can be used to specify the proper alignment.

	<pre class="propdef" id="initial-letters-align">
	Name: <dfn id="propdef-initial-letters-align">initial-letters-align</dfn>
	Value: border-box? [ alphabetic | ideographic | hebrew | hanging ] | border-box
	Initial: alphabetic
	Applies to: certain inline-level boxes and <css>::first-letter</css> and inside <css>::marker</css> boxes (<a href="#first-most-inline-level">see prose</a>)
	Inherited: yes
	Percentages: N/A
	Computed value: specified value
	</pre>

	This property specifies the alignment points
	used to size and position an <a>initial letter</a>.
	Two sets of alignment points are necessary:
	the <a>over</a> and <a>under</a> alignment points of the <a>initial letter</a>
	are matched to corresponding <a>over</a> and <a>under</a> points of the surrounding text.

	Values have the following meanings:

	<dl dfn-type="value" dfn-for="initial-letters-align">
		<dt><dfn>alphabetic</dfn>
		<dd>
			Use the alphabetic and cap-height baselines of the surrounding text
			to align the <a>initial letter</a>.

		<dt><dfn>ideographic</dfn>
		<dd>
			Use the ideographic character face bottom and top edge baselines of the surrounding text
			to align the <a>initial letter</a>.

		<dt><dfn>hebrew</dfn>
		<dd>
			Use the alphabetic and (as yet theoretical) hebrew hanging baseline of the surrounding text
			to align the <a>initial letter</a>.

		<dt><dfn>hanging</dfn>
		<dd>
			Use the alphabetic and hanging baselines of the surrounding text
			to align the <a>initial letter</a>.

		<dt><dfn>border-box</dfn>
		<dd>
			Use the <a>initial letter box</a>’s <a>line-over</a> and <a>line-under</a> border edges
			as the <a>over</a> and <a>under</a> alignment points, respectively.
	</dl>

	Issue: Is there a proper typographic term for the hebrew “hanging” baseline?

	<div class="example">
		The vertical writing mode example from <a href="#f2">Figure 2</a> could be coded as:

		<pre>
			span.initial {
			  initial-letters: 2;
			  initial-letters-align: ideographic;
			}
		</pre>
	</div>



	<div class="example">
		Initial letter in Hebrew
		<pre>
			span.initial {
			initial-letters: 2;
			initial-letters-align: hebrew;
			}
		</pre>
		<img src="images/hebrew-initial-letter.png" width="480"
		     alt="optical kerning in the presence or absence of a space after the initial letter">
	</div>

	Except when ''border-box'' is specified,
	the alignment points of the <a>initial letter</a>
	are automatically determined from its contents:

		<ol>
			<li>If the <a>initial letter</a>
			is an atomic inline,
			use its <a>over</a> and <a>under</a> content-box edges.

			<li>Else if the <a>initial letter</a>
			contains any character from the Han, Hangul, Kana, or Yi <a>Unicode scripts</a>,
			use the ideographic character face bottom and top edge baselines.

			<li>Else if the <a>initial letter</a>
			contains any character from the Devanagari, Bengali, and Gurmukhi <a>Unicode scripts</a>,
			use the hanging and alphabetic baselines.

			<li>Else if the <a>initial letter</a>
			contains any character from the Hebrew <a>Unicode scripts</a>,
			use the ideographic character face bottom and top edge baselines.

			<li>Else use the alphabetic and cap-height baselines.
		</ol>

	Issue: What is the proper alignment for South Asian scripts
	that do not have the explicit hanging baseline, such as Tamil or Telugu?
	See GitHub issue <a href="https://github.com/w3c/csswg-drafts/issues/864">864</a>

	Note: The ordering of keywords in this property is fixed in case ''border-box''
	is expanded to ''[ border-box | alphabetic | ideographic | hebrew | hanging ]''
	to allow explicitly specifying the <a>initial letter</a>’s alignment points.

<h4 id="initial-letter-align-defaults">
UA Default Stylesheet for 'initial-letters-align'</h4>

	In order to provide the better behavior by default,
	UAs must include in their default UA style sheet the following rules:

	<pre>
		[lang]:lang(zh, ja, ko, ii) {
		  initial-letters-align: ideographic;
		}
		[lang]:lang(iw, yi, lad, jrb) {
		  initial-letters-align: hebrew;
		}
		[lang]:lang(hi, mr, ne, pi, kok, brx, mai, sd, sa) {
		  initial-letters-align: hanging;
		}
		/* Script tags override language tags */
		[lang]:lang('*-Latn', '*-Cyrl') {
		  initial-letters-align: alphabetic;
		}
		[lang]:lang('*-Hani', '*-Hant', '*-Hans') {
		  initial-letters-align: ideographic;
		}
	</pre>

	Issue: This only covers the most common cross-linguistic transcription systems.
	Should we include any other / all script tags in the UA style sheet?

<h3 id="sizing-initial-letters">
Sizing Initial Letters</h3>

	The size of a drop initial is determined
	by the need to satisfy the required alignment.
	For an <var>N</var>-line drop initial in a Western script,
	the cap-height of the letter needs to be (<var>N</var> – 1) times the line-height,
	plus the cap-height of the surrounding text.
	Note this height is <em>not</em> the font size of the drop initial.

	Actually calculating this font size is tricky.
	For an <var>N</var>-line drop initial,
	we find the drop initial font size to be:

	<figure>
		<img src="images/InitialCapEquation.png" width="604"
		     alt="Font size of drop cap = ((N-1) * line-height + [cap-height of para] * [font size of paragraph])/[cap-height ratio of drop initial font]">
	</figure>

	<!--
	<div>
		<math display="block"><mrow><mi>Font size of drop initial</mi><mo>=</mo></mrow><mfrac><mrow><mo>(</mo><mi>N</mi><mo>-</mo><mn>1</mn><mo>)</mo><mo>&#x00D7;</mo><mi>line-height</mi><mo>+</mo><mo>(</mo><mi>cap-height ratio of para font</mi><mo>&#x00D7;</mo><mi>font size of para</mi><mo>)</mo></mrow><mrow><mi>cap-height ratio of drop initial font</mi></mrow></mfrac></math>
	</div>
	-->

	<div class="example">
		A three-line drop initial in Adobe Minion Pro
		would have a font size of 61.2pt given
		12pt text, 16pt line-height, and a cap-height of 651/1000 (from the font’s OS/2 table).
	</div>

	The line height used in this calculation
	is the 'line-height' of the containing block
	(or, in the case where a baseline grid is in use,
	the baseline-to-baseline spacing required by the baseline grid [[CSS3-LINE-GRID]]).
	The contents of the lines spanned,
	and therefore any variation in their heights and positions,
	is not accounted for.

<h4 id="initial-letter-shaping">
Shaping and Glyph Selection</h4>

	When 'initial-letters' is not ''normal'',
	shaping <em>should</em> still occur across the box's boundaries,
	see [[css-text-3#boundary-shaping]].
	For example, if the first letter of the Farsi word “پس”
	were styled with ''initial-letters: 2 1'',
	both letters would be styled in their joined forms,
	with initial-form “ﭘ” as the <a>initial letter</a>,
	followed by the normally-styled final-form “ﺲ”.
	Note that the two letters might not always graphically connect,
	even when shaped in their joining forms.

	Issue: Are there other things we need to consider here?
	
<h3 id="initial-letter-exclusions">
Space Around Initial Letters</h3>

	The glyph(s) of an initial letter do not always fit within the specified sink.
	For example, if an initial letter has a descender,
	it could crash into the (n+1)th line of text.
	This is not desirable.

	<figure>
		<img src="images/Dropcap-J-3line-crash.png" width="480"
		     alt="3-line drop cap with J, with descender crashing into fourth line of text">
		<figcaption>Incorrect: three-line initial letter with descender.
		In this font, the capital “J” extends well below the baseline (shown in red).</figcaption>
	</figure>

	Text is therefore excluded around the glyph bounding boxes of the initial letters.

	Specifically, for non-atomic initial letters,
	the content box of the element is sized to fit:

	<ul>
		<li>The specified amount of sink
		(i.e the distance from the top alignment point to the bottom alignment point).

		<li>The actual ascent and descent and side bearings of all the glyphs it contains
		that are part of its inline formatting context,
		even if they leak outside their em boxes.

		<li>The margin boxes of all the atomic inlines it contains
		that are part of its inline formatting context,
		even if they leak outside its own line-height.
	</ul>

	The margin box of the initial letter is then made an exclusion area for subsequent text.

	<figure>
		<img src="images/Dropcap-J-3line-exclude.png" width="480"
		     alt="3-line drop cap with J, but four-line exclusion">
		<figcaption>Correct: text excluded around glyph bounding box</figcaption>
	</figure>

<h3 id="initial-letter-position">
Positioning and Kerning Initial Letters</h3>

	In the <a>block axis</a>, the <a>initial letter</a> is positioned
	to satisfy its alignment requirements. (See 'initial-letters-align'.)

	In the <a>inline axis</a>, the position of the inline letter
	is given by aligning its start margin edge to the start edge of the containing block.

	However, if the <a>initial letter</a> is a non-atomic inline with zero padding and borders,
	the UA must apply an additional negative offset on the start side,
	of the amount necessary to optically align the first glyph
	to the containing block edge as it would be in normal text.

<h3 id="initial-letter-wrapping">
Initial Letter Wrapping: the 'initial-letters-wrap' property</h3>

	Note: 'initial-letters-wrap' is at risk.

	<pre class="propdef">
	Name: <dfn id="propdef-initial-letters-wrap">initial-letters-wrap</dfn>
	Value: none | first | all | grid | <<length>> | <<percentage>>
	Initial: none
	Applies to: certain inline-level boxes and <css>::first-letter</css> and inside <css>::marker</css> boxes (<a href="#first-most-inline-level">see prose</a>)
	Inherited: yes
	Percentages: relative to <a>logical width</a> of (last fragment of) initial letter
	Computed value: as specified
	</pre>

	This property specifies whether lines impacted by an <a>initial letter</a>
	are shortened to fit the rectangular shape of the <a>initial letter</a> box
	or follow the contour of its end-edge glyph outline.

	<dl dfn-for=initial-letters-wrap dfn-type=value>
		<dt><dfn>none</dfn>
		<dd>
			No contour-fitting is performed:
			each impacted line is aligned flush to the end margin edge of the <a>initial letter</a>.

		<dt><dfn>first</dfn>
		<dd>
			Behaves as ''initial-letters-wrap/none''
			if the first <a>typographic character unit</a> after the <a>initial letter</a>
			belongs to Unicode General Category Zs.
			Otherwise behaves as for ''all''
			on the first line of the block containing the initial letter
			and as ''initial-letters-wrap/none'' on the rest.

			<div class="example">
				This example shows why contour-fitting the first line is necessary,
				and why it is dropped when the <a>initial letter</a> is followed by a space:
				<figure>
					<img src="images/OpticalKerning.png" width="200"
					     alt="optical kerning in the presence or absence of a space after the initial letter">
					<figcaption>
						In the top paragraph, the initial letter "A" has a word space after it:
						the gap between the top of the "A" and the next letter
						provides the necessary word separation.
						In the next paragraph, the initial letter "A"
						is part of the first word,
						and leaving a gap between the top of the "A" and the next letter
						would create a jarring visual break within the word.
						In this case, the first line of text
						should be kerned into the initial letter's area,
						as shown in the bottom paragraph.
					</figcaption>
				</figure>
			</div>

			Issue: Do we need an unconditional ''first''?
			(I.e. Should we rename this value to ''auto'' and add a ''first'' value 
			that does not check for spaces?) See GitHub issue 
			<a href="https://github.com/w3c/csswg-drafts/issues/410">410</a>

		<dt><dfn>all</dfn></dt>
		<dd>
			For each line of text impacted by the initial letter,
			the line box adjacent to the initial letter starts
			at the start-most point that touches the ink of the initial letter,
			plus the amount of the <a>initial letter</a>’s end-side border+padding+margin.
			
			If the value of ''shape-outside'' is not ''none'', 
			''shape-outside'' is used instead of the glyph outline.
			</dd>

			Note: This value is at-risk.

		<dt><dfn>grid</dfn>
		<dd>
			This value is the same as ''initial-letters-wrap/none'',
			except that the exclusion area of the impacted lines
			is increased as necessary for its end-edge to land on the character grid,
			i.e. to be a multiple of (''1ic'' + 'letter-spacing')
			as computed on the containing block.
			The 'justify-self' property can then be used to align
			the initial letter box within the exclusion area.

			<figure>
				<img src="images/CJK-Initial.001.png" width="480"
				     alt="Diagram of Japanese initial letter in vertical writing mode">
				<figcaption>Diagram of Japanese initial letter in vertical writing mode</figcaption>
			</figure>

			Note: In this example, the exclusion area for the drop initial
			is larger than its glyph in order to preserve inline-axis alignment.

			Note: This value is also at-risk.


		<dt><dfn><<length>></dfn>
		<dt><dfn><<percentage>></dfn>
		<dd>
			This value behaves the same as ''first''
			except that the adjustment to the first line is given explicitly
			instead of being inferred from the glyph shape.

			Issue: This really needs font-relative lengths to be relative to the used size.

			Note: This value exists because it is easier to implement.
			Authors are encouraged to use the ''first'' value
			and to set margins to control spacing,
			and to use this as a fallback for glyph detection if necessary.

			<div class="example">
				In the following example, UAs that support ''first'' will use the glyph outline
				plus the specified margin in order to place the first line,
				whereas UAs that only support <<length>> or <<percentage>> values
				will pull in the first line by 40% of the initial letter's width
				(and then add the margin to that point).
				<pre>
					h1 + p:first-letter {
						initial-letters: 3; /* 3-line drop-cap */
						initial-letters-wrap: first;
						margin-right: 0.1em;
					}
					@supports (not (initial-letters-wrap: first)) {
						/* Classes auto-generated on paragraphs to match first letter. */
						p.A:first-letter {
							initial-letters-wrap: -40%; /* Start of glyph outline, assuming correct font. */
						}
					}
				</pre>
			</div>

			Issue: These values and related annoyance is likely unnecessary if someone submits a patch to Blink to support ''first''.
	</dl>

	Issue: Edit figure to show how auto behaves in varying contexts

	<div class="example">
		<pre>
			p::first-letter {
			  initial-letters: 3;
			  initial-letters-wrap: none;
			}
		</pre>

		<figure>
			<img src="images/A-wraparound-none.png" width="600"
			     alt="regular dropcap A">
			<figcaption>Ordinary initial letter with no wrapping.</figcaption>
		</figure>
	</div>


	<div class="example">
		<pre>
			p::first-letter {
			  initial-letters: 3;
			  initial-letters-wrap: all;
			}
		</pre>

		<img src="images/A-wraparound.png" width="600"
		     alt="text wrapping around dropcap A" >

		Text follows shape of initial letter.
		Each line box should just touch the ink of the letter,
		with some offset (represented by the shaded box).
	</div>

	<div class="example">
		<pre>
			p::first-letter {
			  initial-letters: 3;
			  initial-letters-wrap: first;
			}
		</pre>

		<img src="images/A-wraparound-first.png" width="600"
		     alt="text wrapping around dropcap A but only on first line">

		Only the first line is moved up against the ink of the initial letter.
	</div>

	<div class="example">
		<img src="images/V-wraparound.png" width="600"
			alt="text wrapping around dropcap V">
	</div>

	<div class="example">
		<img src="images/P-wraparound.png" width="600"
		     alt="text wrapping around dropcap P">
	</div>

	<div class="example">
		<img src="images/W-wraparound.png" width="600"
		     alt="text wrapping around dropcap W">
	</div>

<h3 id="initial-letter-indentation">
Line Layout</h3>

	An <a>initial letter box</a> is considered in-flow in its <a>block formatting context</a>,
	and is part of the contents of the <a>line box</a> in which it originates.
	Aside from vertical alignment,
	its interaction with the rest of the contents of the line is as normal,
	except in a few specific circumstances&hellip;

<h4 id="initial-letter-inline-flow">
Inline Flow Layout: Alignment and Justification</h4>

	For a raised <a>initial letter box</a> (<a>sink</a> of ''1'')
	no special consideration is given for alignment and justification:
	it is treated similar to any other inline-level content.

	However, if the <a>initial letter box</a> is sunk by more than ''1'',
	then its inline-start edge is anchored to the inline-start edge
	of the line box (after indentation)
	and text alignment affects the remaining content of the line
	in the remaining space,
	without moving the <a>initial letter box</a> itself.

	Note: The CSSWG was not aware of any reasonable use cases
	for mixing non-start text alignment with dropped initial letters,
	and this was the most sensible behavior proposed.
	This behavior may be reconsidered if use cases require otherwise.

	In addition, to ensure consistent alignment of all the impacted lines,
	any 'letter-spacing' or <a>justification opportunity</a>
	that would normally be introduced by
	the juxtaposition of the contents of a sunken <a>initial letter</a>
	and the subsequent contents of the line
	is suppressed.
	(Note that this does not affect 'word-spacing' or
	the <a>justification opportunity</a> introduced by a <a>word separator</a>
	because that space is provided by the <a>typographic character unit</a> alone
	and not by its juxtaposition with an adjacent character.)

<h4 id="initial-letter-indentation">
Edge Effects: Indentation and Hanging Punctuation</h4>

	'text-indent' and 'hanging-punctuation'
	apply to the first line of text as normal in the presence of initial letters.
	Lines affected by the exclusion are shortened, as in the presence of floats,
	and are affected the same way.
	
	<figure>
		<img src="images/InitialLetterWithTextIndent.png" width="300"
		     alt="initial letter with text indent">
		<figcaption>Initial letter with text indent. </figcaption>
	</figure>

	ISSUE: The interaction of 'initial-letter' and 'hanging-punctuation'
	is <a href="hhttps://github.com/w3c/csswg-drafts/issues/310#issuecomment-396765893">under discussion</a>.

<h4 id="initial-letter-ancestors">
Ancestor Inlines</h4>

	If the <a>initial letter box</a> is contained by <a>inline box</a> ancestors,
	the boundaries of those <a>inline boxes</a> are drawn
	to exclude the <a>initial letter box</a>,
	as if it were outside their startmost <a>margin edge</a>.
	This is a purely geometric operation:
	it does not affect e.g.
	property inheritance or
	the effective 'letter-spacing' between the <a>initial letter box</a>
	and subsequent content.

<h4 id="initial-letter-multi-line">
Multi-line Initial Letters</h4

	If an initial letter is too long to fit on one line,
	it wraps (according to the usual text-wrapping rules),
	each line filled and formatted exactly as if it were the first line
	and the initial letter too long to fit any subsequent normal text.
	Any normal text after the initial letter starts on its last line,
	affected exactly as if that line were the first line.

	<figure>
		<img src="images/Multi-line-initial.png" width="300"
		     alt="multi-line drop cap">
		<figcaption>Drop cap extends to two lines.</figcaption>
	</figure>

<h3 id="initial-letter-paragraphs">
Clearing Initial Letters</h3>

<h4 id="raised-sunken-caps">
Raised and sunken caps</h4>
<!--old text
	An initial letter does not affect the position of its containing element.
	For “raised caps” or “sunken caps,”
	the effect is created as if the text around the initial letter was pushed down,
	rather than the letter extending up into previous elements.

-->

	The margin box of an initial letter contributes to the size
	of its containing element.
	Initial letters that extend above the first line of text,
	known as “raised caps” or “sunken caps,”
	do not extend up into previous elements.
	Since the content box for an initial letter includes all glyph ink,
	this also means that accents or other ink
	above the cap height of an initial letter
	will not impinge on previous elements.



	<figure>
		<img src="images/initial-letter-drop-para-compare.png" width="600"
		     alt="raised cap para after normal para">
		<figcaption>
			Raised cap (<code>initial-letters: 3 1</code>) on right;
			note that the position of the “C” is the same in both cases,
			but on the right all text is moved down relative to the initial letter.
		</figcaption>
	</figure>

	Issue: Handle glyph ink above cap height of font.
	Proposal: Make it an exclusion area for line boxes and border boxes. Include margin specified on initial-letters as part of exclusion area in order to control spacing.

	Issue: Draw a box model diagram here. Does the margin of the initial letter collapse with its container?


<h4 id="short-para-initial-letter">
Short paragraphs with initial letters</h4>

	A paragraph with an initial letter can have fewer lines of text
	than the initial letter occupies.
	In this case, the initial letter’s top alignment is still honored,
	and its exclusion area continues into any subsequent blocks.
	This forces the subsequent inline-level content to wrap around the initial letter--
	exactly as if that block's text were part of its own containing block.
	(This is similar to how floats exclude content in subsequent block boxes.)

	<figure>
		<img src="images/initial-letter-short-para.png" width="600"
			 alt="short para with initial letter">
		<figcaption>
			The red text is a short paragraph with an initial letter.
			Note the subsequent paragraph wraps around the initial letter
			just as text in the paragraph with the initial letter does.
		</figcaption>
	</figure>

	If the subsequent block starts with an initial letter,
	establishes an [=independent formatting context=],
	or specifies 'clear' in the initial letter’s containing block’s start direction,
	then it must clear the previous block’s initial letter.

	<figure>
		<img src="images/initial-letter-short-para-initial.png" width="600"
		     alt="short para with initial letter followed by para with initial">
		<figcaption>
			The red text is a short paragraph with an initial letter.
			The subsequent paragraph clears because it also has an initial letter.
		</figcaption>
	</figure>

<h4 id="initial-letter-floats">
Interaction with floats</h4>

	<a>Initial letters</a> are not <a href="https://www.w3.org/TR/CSS21/visuren.html#floats">floats</a>:
	they are <a>in-flow</a> <a>inline-level</a> content
	that belongs to a <a>line box</a>.
	Therefore:

	<ul>
		<li>
			The 'clear' property does not care about <a>initial letters</a>:
			it neither applies to <a>initial letters</a>
			nor clears them when applied to nearby floats.
		<li>
			Like line boxes or floats,
			<a>initial letter boxes</a>
			must not overlap the <a>margin boxes</a>
			of any floats participating in the same <a>block formatting context</a>.
			An overlapping <a>initial letter box</a>
			is shifted inward or downward
			until either it fits without overlapping
			or there are no more floats present.
		<li>
			If a line box’s start edge shifts or moves down to clear a float,
			an <a>initial letter</a> originating in it moves with it;
			likewise if an <a>initial letter</a> shifts inward or moves downward
			to clear a float,
			its originating line box and subsequent line boxes
			shorten and/or move accordingly.
		<li>
			If an <a>inline-start</a> float
			originates in the first line of content
			adjacent to an <a>initial letter</a>,
			then it moves past the <a>initial letter</a>
			towards the containing block edge,
			exactly as if the <a>initial letter</a> were any other inline-level content.

			However, if such a float originates
			in subsequent lines of content adjacent to a (sunk) <a>initial letter</a>,
			then that float must clear the <a>initial letter</a>.
	</ul>
	
		<figure>
		<img src="images/float-interaction.png" width="480"
		     alt="initial letter interacting with floats">
		<figcaption>
			In the absence of an initial letter, the first line of text could abut the blue float. 
			But the presence of the initial letter requires that the text move over.
		</figcaption>
	</figure>


	See <a href="https://www.w3.org/TR/CSS21/visuren.html#floats">CSS2&sect;9.5</a>
	for more information about the layout of floats
	and adjacent content.
	[[!CSS2]]

	ISSUE: Whether an inline-end float originating in subsequent lines
	must clear the initial letter (as inline-start floats do)
	is <a href="https://lists.w3.org/Archives/Public/www-style/2018Jul/0019.html">still under discussion</a>.
	There is no aesthetic reason to require it;
	however it’s yet unclear how the underlying layout model
	would distinguish between the two cases.

<h4 id="intial-letter-breaking">
Interaction with Fragmentation (Pagination)</h4>

	Since a single glyph cannot be <a>fragmented</a> across
	pages (or columns or other <a>fragmentation containers</a>),
	an <a>initial letter</a> is considered <a spec="css-break-3">monolithic</a> [[css-break-3]]
	for the purpose of block-axis <a>fragmentation</a>
	(breaking across pages, columns, regions, etc.).
	Additionally,
	breaks between the in-flow lines alongside an <a>initial letter box</a>
	are avoided,
	much as breaks between line boxes affected be 'widows' and 'orphans'
	are avoided.
	However,
	if there is a <a>forced break</a>
	alongside the <a>initial letter box</a>,
	then it takes precedence;
	but has no effect on the <a>initial letter box</a> itself.

	As with other <a spec="css-break-3">monolithic</a> objects,
	if an <a>initial letter box</a> occurs
	at the top of a <a>fragmentation container</a>
	and that <a>fragmentation container</a> is too short to contain it,
	it may be either truncated or sliced.
	Adjacent content, however, must be <a>fragmented</a> according to its own rules,
	not truncated or sliced along with the <a>initial letter</a>.

<h2 class="no-num" id="baseline-synthesis">
Appendix A: Synthesizing Alignment Metrics</h2>

	<h3 class="no-num" id="baseline-synthesis-fonts">
	A.1: Synthesizing Baselines (and Other Font Metrics) for Text</h3>

	Some fonts might not contain the metrics information necessary
	to align text properly as described in this module.
	User agents may use the following strategies
	in the absence of a required metric:

	<dl>

		<dt>Measure the font
		<dd>
			Metrics may be derived from the glyph shapes.
			For example,
			<ol>
				<li>
					The center of the minus sign (U+2212)
					can be taken as the mathematical baseline.

				<li>
					The amount by which the lowercase “o”
					descends below the alphabetic baseline
					can be subtracted from its highest point
					to <a href="https://drafts.csswg.org/css-values/#ex">measure the x-height</a>.

					<figure>
						<img src="images/measuring-x-height-o.png" width="240"
						alt="measuring the x height of the letter o"  >
						<figcaption>
							Measuring the x height.
						</figcaption>
					</figure>

				<li>
					The amount by which the uppercase “O”
					descends below the alphabetic baseline
					can be subtracted from its highest point
					to measure the cap-height.



				<li>
					The top edge of the below ideograph (U+4E05 “丅”)
					and the bottom edge of the above ideograph (U+4E04 “丄”)
					can be taken as the ideographic character face edges.
					In the horizontal dimension,
					the left and right edges of the nation ideograph (U+56FD “国”)
					or reason ideograph (U+56E0 “因”)
					can be used.
					In all cases, the these edges should be measured
					at their intersection with the central baseline in that axis.

					Issue: What is the best character to use for the sides?

				<li>
					The top edge of the center of the Hebrew maqaf (U+05B3 “־”)
					can be taken as the Hebrew hanging baseline.

				<li>
					The top edge of the center of the letter Ka
					can be taken as the hanging baseline.
					Which Ka is used should depend on the <a>content language</a>:

					<table class="data">
						<thead>
							<tr>
								<th>Language
								<th>Script
								<th>Letter
						<tbody>
							<tr>
								<td>
								<td>Devanagari
								<td>क U+0915 KA
							<tr>
								<td>
								<td>Bengali
								<td>ক U+0995
							<tr>
								<td>
								<td>Gurmukhi
								<td>ਕ U+0A15
							<tr>
								<td>
								<td>Tibetan
								<td>ཀ U+0F40
					</table>

					Issue: Pick a default.

					<figure>
						<img src="images/measuring-hanging-baseline-ka.png" width="240"
						alt="finding the position of the hanging baseline of the letter ka"  >
						<figcaption>
							The hanging baseline is at the top edge of the character ink.
						</figcaption>
					</figure>

				<li>Issue: Add more notes here?
			</ol>

			Issue: Somebody sanity-check these heuristics please.

		<dt>Use a heuristic for the script
		<dd>
			Issue: What does this mean?

		<dt>Use fallback values
		<dd>
			The following fallback values
			<ul>
				<li>x-height: .5em;
				<li>cap-height: .66em;
				<li>hanging baseline: .6em;
				<li>Hebrew hanging baseline: ???
			</ul>
	</ol>

<h3 class="no-num" id="baseline-synthesis-replaced">
A.2: Synthesizing Baselines for Replaced Content</h3>

	Issue: Copy over text from <a href="https://www.w3.org/TR/css-writing-modes-3/#replaced-baselines">CSS Writing Modes</a>
	and expand for additional baseline values.

	Note: Authors can use margins (positive or negative)
	to adjust the alignment of replaced content within a line.

	<div class="example">
		In this example, the author is using a set of images
		to display characters that don't exist.

		<pre>
			img[src^="/text/"] {
				height: 1em; /* Size to match adjacent text */
				margin-bottom: -0.2em; /* Baseline at 20% above bottom */
			}
			...
			&lt;p>This is some text with words written in an unencoded script:
			&lt;img src="/text/ch3439.png" alt="...">
				&lt;img src="/text/ch3440.png" alt="...">
				&lt;img src="/text/ch3442.png" alt="...">
		</pre>
	</div>

	Note: A future level of CSS may include a way of specifying a full baseline table for replaced elements.
	(This will probably look like a <css>baseline-table</css> property
	that accepts ''[&lt;baseline-keyword> <<percentage>>]+''.)

<h2 class="no-num" id="changes">
Changes</h2>

	Changes since the
	<a href="https://www.w3.org/TR/2015/WD-css-inline-3-20150917/">17 September 2015 Working Draft</a>
	include:

	<ul>
		<li>Adding values for the ideographic and middle baselines.
		<li>Clarifying interaction of the ''auto'' 'dominant-baseline' value with SVG glyph positioning.
		<li>A few other minor editorial improvements.
	</ul>

<h2 class="no-num" id="ack">
Acknowledgments</h2>

	Special thanks goes to the initial authors,
	Eric A. Meyer and Michel Suignard.

	In additions to the authors, this specification would not have been possible without the help from:

	David Baron,
	David M Brown,
	Oriol Brufau,
	John Daggett,
	Stephen Deach,
	Sylvain Galineau,
	David Hyatt,
	Shinyu Murakami,
	Tess O’Connor,
	Sujal Parikh,
	Florian Rivoal,
	Alan Stearns,
	Bobby Tung,
	Chris Wilson,
	Grzegorz Zygmunt.