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
@@ -442,40 +441,34 @@ tune these values for different fonts or different types of display devices.</p>
442
441
<td style="width:8%"> </td>
443
442
</tr>
444
443
<tr>
445
-
<th style="width:16%">scaling factor</th>
446
-
<td style="width:12%">3/5</td>
447
-
<td style="width:9%">3/4</td>
448
-
<td style="width:10%">8/9</td>
449
-
<td style="width:11%">1</td>
450
-
<td style="width:11%">6/5</td>
451
-
<td style="width:12%">3/2</td>
452
-
<td style="width:11%">2/1</td>
453
-
<td style="width:8%">3/1</td>
444
+
<th>HTML headings</th>
445
+
<td>h6</td>
446
+
<td> </td>
447
+
<td>h5</td>
448
+
<td>h4</td>
449
+
<td>h3</td>
450
+
<td>h2</td>
451
+
<td>h1</td>
452
+
<td> </td>
454
453
</tr>
455
454
<tr>
456
-
<th style="width:16%">HTML headings</th>
457
-
<td style="width:12%">h6</td>
458
-
<td style="width:9%"> </td>
459
-
<td style="width:10%">h5</td>
460
-
<td style="width:11%">h4</td>
461
-
<td style="width:11%">h3</td>
462
-
<td style="width:12%">h2</td>
463
-
<td style="width:11%">h1</td>
464
-
<td style="width:8%"> </td>
465
-
</tr>
466
-
<tr>
467
-
<th style="width:16%">HTML font sizes</th>
468
-
<td style="width:12%">1</td>
469
-
<td style="width:9%"> </td>
470
-
<td style="width:10%">2</td>
471
-
<td style="width:11%">3</td>
472
-
<td style="width:11%">4</td>
473
-
<td style="width:12%">5</td>
474
-
<td style="width:11%">6</td>
475
-
<td style="width:8%">7</td>
455
+
<th>HTML font sizes</th>
456
+
<td>1</td>
457
+
<td> </td>
458
+
<td>2</td>
459
+
<td>3</td>
460
+
<td>4</td>
461
+
<td>5</td>
462
+
<td>6</td>
463
+
<td>7</td>
476
464
</tr>
477
465
</table>
478
466
467
+
<p class="note">Note: implementation experience has demonstrated that a fixed ratio between adjacent absolute-size keywords is problematic, and this specification does NOT recommend such a fixed ratio, in contrast to previous specifications (<a href="http://www.w3.org/TR/REC-CSS1#font-size">CSS1 suggested 1.5</a>, and <a href="http://www.w3.org/TR/REC-CSS2/fonts.html#font-size-props">CSS2 suggested 1.2</a>).</p>
468
+
469
+
<p>Implementors should build a table of scaling factors for absolute-size keywords relative to the 'medium' font size and the particular device and its characteristics (e.g. the resolution of the device).
470
+
</p>
471
+
479
472
<p>
480
473
Different media may need different scaling factors. Also, the UA
481
474
should take the quality and availability of fonts into account when
@@ -93,7 +93,7 @@ have the following meanings:</p>
93
93
94
94
<dl>
95
95
<dt>left, right, center, justify</dt>
96
-
<dd>Left, right, center, and justify text, respectively.</dd>
96
+
<dd>Left, right, center, and justify text, respectively, as described in <a href="visuren.html#inline-formatting">the section on inline formatting</a>.</dd>
97
97
</dl>
98
98
99
99
<p>A block of text is a stack of <a href="visuren.html#line-box">line
@@ -428,7 +428,7 @@ inline) should be treated as an anonymous inline element.
428
428
</p>
429
429
<p>
430
430
For each inline (including anonymous inlines), the following steps are
431
-
performed, ignoring bidi formatting characters as if they were not
431
+
performed, treating bidi formatting characters as if they were not
432
432
there:
433
433
</p>
434
434
<ol>
@@ -439,7 +439,7 @@ character surrounding a linefeed (U+000A) character is removed if
439
439
</li>
440
440
<li>If 'white-space' is set to 'pre' or 'pre-wrap', any sequence of
441
441
spaces (U+0020) unbroken by an element boundary is treated as a
442
-
sequence of non-breaking spaces. However, a line breaking
442
+
sequence of non-breaking spaces. However, for 'pre-wrap', a line breaking
443
443
opportunity exists at the end of the sequence.
444
444
</li>
445
445
<li>If 'white-space' is set to 'normal' or 'nowrap', linefeed
@@ -519,6 +519,18 @@ to avoid spaces immediately inside start and end tags, as these tend
519
519
to do weird things when dealing with white space collapsing.
520
520
</p>
521
521
522
+
<h3 id="ctrlchars">Control and combining characters' details</h3>
523
+
524
+
<p>Control characters other than U+0009 (tab), U+000A (line feed),
525
+
U+0020 (space), and U+202x (bidi formatting characters) are treated as
526
+
characters to render in the same way as any normal character.</p>
527
+
528
+
<p>Combining characters should be treated as part of the character
529
+
with which they are supposed to combine. For example, :first-letter
530
+
styles the entire glyph if you have content like
531
+
"<code>o<span>&#x308;</span></code>"; it doesn't just
0 commit comments