You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h2class="heading settled" data-level="1" id="line-height"><spanclass="secno">1. </span><spanclass="content">Line Heights and Baseline Alignment</span><aclass="self-link" href="#line-height"></a></h2>
205
210
<pclass="issue" id="issue-1a1ecd92"><aclass="self-link" href="#issue-1a1ecd92"></a>This section is being rewritten. Refer to <ahref="http://www.w3.org/TR/CSS21/visudet.html#line-height">section 10.8</a> of <adata-link-type="biblio" href="#biblio-css21">[CSS21]</a> for the normative CSS definition or the <ahref="http://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.)</p>
211
+
<pclass="issue" id="issue-95a9f423"><aclass="self-link" href="#issue-95a9f423"></a> The CSSWG would like to know which baseline values are necessary: if any can be dropped, or any need to be added.</p>
<pclass="issue" id="issue-76db6c38"><aclass="self-link" href="#issue-76db6c38"></a> These values and related annoyance is likely unnecessary if someone submits a patch to Blink to support <aclass="css" data-link-type="maybe" href="#valdef-initial-letter-wrap-first">first</a>.</p>
811
818
</dl>
812
819
<pclass="issue" id="issue-c4ff3304"><aclass="self-link" href="#issue-c4ff3304"></a> Edit figure to show how auto behaves in varying contexts</p>
<h4class="heading settled" data-level="2.10.3" id="initial-letter-floats"><spanclass="secno">2.10.3. </span><spanclass="content"> Interaction with floats</span><aclass="self-link" href="#initial-letter-floats"></a></h4>
885
892
<p>Floats always clear an initial letter when floated to the same side. When floated to the opposite side, they are pushed down to clear the initial letter only if they have specified <aclass="property" data-link-type="propdesc" href="https://drafts.csswg.org/css2/visuren.html#propdef-clear">clear</a> to this side or they do not fit without overlapping the initial letter.</p>
886
893
<pclass="issue" id="issue-2ad0a0cb"><aclass="self-link" href="#issue-2ad0a0cb"></a> Is this the behavior we want? What if the float is on the same line as the initial letter?</p>
<p>In additions to the authors, this specification would not have been possible without the help from: </p>
908
-
<p>David Baron, John Daggett, Stephen Deach, Sujal Parikh, Grzegorz Zygmunt, Chris Wilson, David M Brown, Bobby Tung, Shinyu Murakami, David Hyatt, Sylvain Galineau, Alan Stearns, Ted O’Connor. </p>
<pclass="issue" id="issue-b76fe1d3"><aclass="self-link" href="#issue-b76fe1d3"></a> Copy over text from <ahref="http://www.w3.org/TR/css-writing-modes-3/#replaced-baselines">CSS Writing Modes</a> and expand for additional baseline values.</p>
915
+
<pclass="note" role="note">Note: Authors can use margins (positive or negative)
916
+
to adjust the alignment of replaced content within a line.</p>
917
+
<divclass="example" id="example-f7450f42">
918
+
<aclass="self-link" href="#example-f7450f42"></a> In this example, the author is using a set of images
919
+
to display characters that don’t exist.
920
+
<pre>img[src^="/text/"] {
921
+
height: 1em; /* Size to match adjacent text */
922
+
margin-bottom: -0.2em; /* Baseline at 20% above bottom */
923
+
}
924
+
...
925
+
<p>This is some text with words written in an unencoded script:
926
+
<img src="/text/ch3439.png" alt="...">
927
+
<img src="/text/ch3440.png" alt="...">
928
+
<img src="/text/ch3442.png" alt="...">
929
+
</pre>
930
+
</div>
931
+
<pclass="note" role="note">Note: A future level of CSS may include a way of specifying a full baseline table for replaced elements.
932
+
(This will probably look like a <spanclass="css">baseline-table</span> property
933
+
that accepts ''[<baseline-keyword><aclass="production css" data-link-type="type" href="https://drafts.csswg.org/css-values-3/#percentage-value"><percentage></a>]+''.)</p>
<p>In additions to the authors, this specification would not have been possible without the help from: </p>
938
+
<p>David Baron, John Daggett, Stephen Deach, Sujal Parikh, Grzegorz Zygmunt, Chris Wilson, David M Brown, Bobby Tung, Shinyu Murakami, David Hyatt, Sylvain Galineau, Alan Stearns, Ted O’Connor. </p>
<h3class="no-num heading settled" id="index-defined-here"><spanclass="content">Terms defined by this specification</span><aclass="self-link" href="#index-defined-here"></a></h3>
1002
1031
<ulclass="indexlist">
1003
-
<li><ahref="#valdef-alignment-baseline-after-edge">after-edge</a><span>, in §1.2.1</span>
1004
1032
<li><ahref="#propdef-alignment-baseline">alignment-baseline</a><span>, in §1.2.1</span>
1005
1033
<li><ahref="#valdef-initial-letter-wrap-all">all</a><span>, in §2.8</span>
<divclass="issue">This section is being rewritten. Refer to <ahref="http://www.w3.org/TR/CSS21/visudet.html#line-height">section 10.8</a> of <adata-link-type="biblio" href="#biblio-css21">[CSS21]</a> for the normative CSS definition or the <ahref="http://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.)<ahref="#issue-1a1ecd92"> ↵ </a></div>
1327
+
<divclass="issue"> The CSSWG would like to know which baseline values are necessary: if any can be dropped, or any need to be added.<ahref="#issue-95a9f423"> ↵ </a></div>
1300
1328
<divclass="issue"> Should be text-over and text-under instead of text-top and text-bottom,
1301
1329
but maybe it’s better not to use those terms for consistency with legacy <aclass="property" data-link-type="propdesc" href="#propdef-vertical-align">vertical-align</a>.<ahref="#issue-5c2889ea"> ↵ </a></div>
1302
1330
<divclass="issue"> Putting <aclass="css" data-link-type="maybe" href="#valdef-alignment-baseline-top">top</a>, <aclass="css" data-link-type="maybe" href="#valdef-alignment-baseline-center">center</a>, and <aclass="css" data-link-type="maybe" href="#valdef-alignment-baseline-bottom">bottom</a> in here is awkward,
<divclass="issue"> Do we need an unconditional <aclass="css" data-link-type="maybe" href="#valdef-initial-letter-wrap-first">first</a>?
1316
1344
(I.e. Should we rename this value to <aclass="css" data-link-type="maybe" href="#valdef-dominant-baseline-auto">auto</a> and add a <aclass="css" data-link-type="maybe" href="#valdef-initial-letter-wrap-first">first</a> value that does not check for spaces?)<ahref="#issue-a826765c"> ↵ </a></div>
1317
1345
<divclass="issue"> This really needs font-relative lengths to be relative to the used size.<ahref="#issue-645378a9"> ↵ </a></div>
1346
+
<divclass="issue"> These values and related annoyance is likely unnecessary if someone submits a patch to Blink to support <aclass="css" data-link-type="maybe" href="#valdef-initial-letter-wrap-first">first</a>.<ahref="#issue-76db6c38"> ↵ </a></div>
1318
1347
<divclass="issue"> Edit figure to show how auto behaves in varying contexts<ahref="#issue-c4ff3304"> ↵ </a></div>
1319
1348
<divclass="issue"> Handle glyph ink above cap height of font.<ahref="#issue-f77cbeb9"> ↵ </a></div>
1320
1349
<divclass="issue"> Is this the behavior we want? What if the float is on the same line as the initial letter?<ahref="#issue-2ad0a0cb"> ↵ </a></div>
1321
1350
<divclass="issue">Describe in more detail.
1322
1351
Should we document which characters in which scripts are useful,
1323
1352
such as lowercase "o" to measure x-height? See https://drafts.csswg.org/css-values/#ex<ahref="#issue-3c6d3ab2"> ↵ </a></div>
1353
+
<divclass="issue"> Copy over text from <ahref="http://www.w3.org/TR/css-writing-modes-3/#replaced-baselines">CSS Writing Modes</a> and expand for additional baseline values.<ahref="#issue-b76fe1d3"> ↵ </a></div>
0 commit comments