-
Notifications
You must be signed in to change notification settings - Fork 709
/
Copy pathtest-coverage.html
568 lines (381 loc) · 22.6 KB
/
test-coverage.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
<!doctype html>
<meta charset=utf-8>
<title>CSS Text 3 test coverage report</title>
<meta name="viewport" content="width=device-width, initial-scale=1"><Paste>
<link href="../default.css" rel="stylesheet" type="text/css">
<div class=head>
<h1 id=title>CSS Text 3 test coverage report</h1>
<h2 class=subtitle>2019-07-02</h2>
<dl>
<dt class="editor">Prepared by:
<dd class="editor p-author h-card vcard" data-editor-id="43241"><a class="p-name fn u-url url" href="https://florian.rivoal.net">Florian Rivoal</a> (<span class="p-org org">Invited Expert</span>)
</dl>
<hr title="Separator for header">
</div>
<div class="p-summary">
<h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="content">Abstract</span></h2>
<p>
This report evaluates the test coverage of the <a href="https://drafts.csswg.org/css-text-3/">CSS Text Module Level 3</a>
as it was on 2019-05-02
when the latest commit was <a href="https://github.com/w3c/csswg-drafts/blob/643729ea032b5ae0c29e3f456cdc96107175ae3d/css-text-3/Overview.bs">643729ea032b5ae0c29e3f456cdc96107175ae3d</a>.
It is provided for discussion only and may change at any moment.
Its publication here does not imply endorsement of its contents by W3C,
or the CSS-Working Group.
Don’t cite this document other than as work in progress.
<p>
It takes into account tests in:
<ul>
<li><a href="https://github.com/web-platform-tests/wpt/tree/master/css/css-text/">wpt/css/css-text/</a> and subdirectories
<li>All tests in <a href="https://github.com/web-platform-tests/wpt/tree/master/css/CSS2/">wpt/css/CSS2/</a> and subdirectories <em>that relate to the <code>white-space</code> property</em>.
<li><a href="https://github.com/web-platform-tests/wpt/tree/master/css/vendor-imports/mozilla/mozilla-central-reftests/text3">wpt/css/vendor-imports/mozilla/mozilla-central-reftests/text3/</a>
</ul>
<p>
It does <strong>not</strong> include tests from:
<ul>
<li><a href="https://github.com/web-platform-tests/wpt/tree/master/css/CSS2">wpt/css/CSS2/</a>, other than those related to the <code>white-space</code> property.
</ul>
</div>
<p>
The following sections mirror
the outline of the specification itself,
and each section links to the corresponding one in he specification.
<div class=issue>Issue:
<p>Problems other than missing spec coverage are highlighted he same as as this paragraph is.
</div>
<hr>
<h2 id="introduction">1 <a href="https://drafts.csswg.org/css-text-3/#intro">Introduction</a></h2>
<p>Tests not needed.
<h3 id="module-interactions">1.1 <a href="https://drafts.csswg.org/css-text-3/#placement">Module Interactions</a></h3>
<p>Tests not needed.
<h3 id="values">1.2 <a href="https://drafts.csswg.org/css-text-3/#values">Values</a></h3>
<p>Tests not really needed.
<p>Possible addition:
<ul>
<li>Check that the css-wide keywords work on every property.
</ul>
<h3 id="languages-and-typesetting">1.3 <a href="https://drafts.csswg.org/css-text-3/#languages">Languages and Typesetting</a></h3>
<p>Tests not really needed: these are definitions, they get tested through their applications, not standalone.
<p>Possible addition:
<ul>
<li>whether The HTTP Content-Language header is having the desired effect on things that depend on content language
</ul>
<h3 id="characters-and-letters">1.4 <a href="https://drafts.csswg.org/css-text-3/#characters">Characters and Letters</a></h3>
<p>For the most part, tests not really needed:
these are definitions, they get tested through their applications, not standalone.
The few testable assertions that are made have coverage.
<p>Possible addition:
<ul>
<li>turning the content of example 1 into tests (first, check that it’s not already done)
</ul>
<h3 id="text-processing">1.5 <a href="https://drafts.csswg.org/css-text-3/#text-encoding">Text Processing</a></h3>
Exhaustive coverage unrealistic, since this section is effectively a dependency on all of Unicode.
Some tests nonetheless provided for sanity checking
(such as the effect of certain control characters on Arabic shaping).
<h2 id="transforming-text">2 <a href="https://drafts.csswg.org/css-text-3/#transforming">Transforming Text</a></h2>
<p>Test only needed in subsection.
<h3 id="case-transforms-the-text-transform-property">2.1 <a href="https://drafts.csswg.org/css-text-3/#text-transform-property"> Case Transforms: the text-transform property</a></h3>
<p>Overall good coverage. Very good i18n coverage.
<p>Missing:
<ul>
<li>No test of Animation type.
<li>“full-width only transforms U+0020 spaces to U+3000 within preserved white space.”
</ul>
<p>Possible addition:
<ul>
<li>An automated test for plain text copy&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.
</ul>
<h2 id="white-space-and-wrapping-the-white-space-property">3 <a href="https://drafts.csswg.org/css-text-3/#white-space-property">White Space and Wrapping: the white-space property</a></h2>
<p>Good overal coverage through section 4 (white space processing details) and subsections.
<p>Missing tests:
<ul>
<li>wrappable inlines inside white-space:pre blocks don’t get ignored
<li>No test of Animation type.
<li>intrinsic (min and max) sizing tests for values other than pre-wrap and break-spaces
</ul>
<p>Tests that need to be updated:
<ul>
<li>intrinsic sizing & pre-wrap. See <a href="https://github.com/w3c/csswg-drafts/issues/3440#issuecomment-465671641">CSS WG Minutes for the behavior change</a>
</ul>
<p>Possible addition:
<ul>
<li>coverage of "break-spaces" not as exhaustive as other values. Basic behavior is covered, and difference from "pre-wrap" is covered as well, so this is adequate, but it doesn't have the long list of basic tests that other values got from the CSS2 test suite.
</ul>
<h2 id="white-space-processing-details">4 <a href="https://drafts.csswg.org/css-text-3/#white-space-processing">White Space Processing Details</a></h2>
<p>Partial coverage.
<p>Missing tests:
<ul>
<li>As required by [UNICODE], unsupported Default_ignorable characters must be ignored for rendering.
</ul>
<h3 id="the-white-space-processing-rules">4.1 <a href="https://drafts.csswg.org/css-text-3/#white-space-rules">The White Space Processing Rules</a></h3>
<p>Sufficient coverage. All parts of this section are well exercised.
<p>Most tests to be found in subsections.
<h4 id="phase-i-collapsing-and-transformation">4.1.1 <a href="https://drafts.csswg.org/css-text-3/#white-space-phase-1">Phase I: Collapsing and Transformation</a></h4>
<p>Almost Sufficient coverage. Most parts of this section are well exercised.
<p>Missing tests:
<ul>
<li>
a soft wrap opportunity exists at the end of a sequence of spaces <strong>and/or tabs</strong>,
while for break-spaces, soft wrap opportunity exists after every space <strong>and every tab</strong>.
</ul>
<h4 id="segment-break-transformation-rules">4.1.2 <a href="https://drafts.csswg.org/css-text-3/#line-break-transform">Segment Break Transformation Rules</a></h4>
<p>Partial coverage.
<p>Indirectly tested, no dedicated tests:
<ul>
<li>When 'white-space' is ''break-spaces'' segment breaks are not collapsible and are instead transformed into a preserved line feed (U+000A).
</ul>
<p>Missing tests:
<ul>
<li>the first 3 bullet points are not tested for “nowrap”
<li>“Otherwise, if the writing system of the segment break is Chinese, Japanese, or Yi, […]”
<li>For this purpose, Emoji (Unicode property Emoji) with an East Asian Width property of W or N are treated as having an East Asian Width property of A.
<li>“Otherwise, the segment break is converted to a space (U+0020).”
</ul>
<h4 id="phase-ii-trimming-and-positioning">4.1.3 <a href="https://drafts.csswg.org/css-text-3/#white-space-phase-2">Phase II: Trimming and Positioning</a></h4>
<p>Almost sufficient coverage. Most parts of this section are well exercised.
<p>Missing tests:
<ul>
<li>See [UAX9] for rules on how U+0009 tabulation interacts with bidi.
<li>tabs hang with ''pre-wrap'' and wrap with ''break-spaces''
</ul>
<h3 id="tab-character-size-the-tab-size-property">4.2 <a href="https://drafts.csswg.org/css-text-3/#tab-size-property">Tab Character Size: the tab-size property</a></h3>
<p>Partial coverage.
<p>Missing tests
<ul>
<li>No test of Animation type.
</ul>
<h2 id="line-breaking-and-word-boundaries">5 <a href="https://drafts.csswg.org/css-text-3/#line-breaking">Line Breaking and Word Boundaries</a></h2>
<p>Tests not really needed: these are definitions, they get tested through their applications, not standalone.
<p>Can be a good section to host tests for i18n requirements not covered in detail by the spec.
<p>Possible Additions:
<ul>
<li>Basic line breaking tests for any language mentioned (Thai, Lao, Khmer, Javanese, Balinese, Yi…)
</ul>
<div class=issue>Issue:
The following tests need to be reviewed for correctness: i18n/css3-text-line-break-baspglwj-( >002, <120) and i18n/css3-text-line-break-opclns-*
</div>
<h3 id="line-breaking-details">5.1 <a href="https://drafts.csswg.org/css-text-3/#line-break-details">Line Breaking Details</a></h3>
<p>Spotty Coverage.
<p>Missing tests:
<ul>
<li>“Regardless of the white-space value […] the BK, NL […] classes […] must be honored”
<li>tests of WJ, ZW, and GL and ZWJ for values of white-space other than normal
(GL is tested for pre-wrap and break-spaces)
<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.
</ul>
<p>Untestable(?):
<ul>
<li>UAs that allow wrapping at punctuation other than spaces should prioritize breakpoints. […]
</ul>
<h3 id="breaking-rules-for-letters-the-word-break-property">5.2 <a href="https://drafts.csswg.org/css-text-3/#word-break-property">Breaking Rules for Letters: the word-break property</a></h3>
<p>Partial Coverage.
<p>Missing tests:
<ul>
<li>keep-all and break-word apply to inlines
<li>No test of Animation type.
<li>affects intrinsic sizing
<li>and/or non-letter typographic character units belonging to the NU, AL, AI, or ID Unicode line breaking classes [UAX14]
<li>It does not affect rules governing the soft wrap opportunities created by [...] U+3000 IDEOGRAPHIC SPACE
<li>effect of word-break:keep-all on NU and AI classes
<li>Symbols that line-break the same way as letters of a particular category are affected the same way as those letters.
<li>does not suppress <code><wbr></code>
<li>line-break:anywhere wins over word-break:keep-all
</ul>
<p>Covered, but could have more:
<ul>
<li>It does not affect rules governing the soft wrap opportunities created around punctuation
</ul>
<h3 id="line-breaking-strictness-the-line-break-property">5.3 <a href="https://drafts.csswg.org/css-text-3/#line-break-property">Line Breaking Strictness: the line-break property</a></h3>
<p>Extensive CJK coverage.
<p>Missing tests:
<ul>
<li>applies to inlines
<li>No test of Animation type.
<li>affects intrinsic sizing
<li>see <a href="https://github.com/web-platform-tests/wpt/issues/11161">wpt issue 11161</a>
</ul>
<p>Untestable(?):
<ul>
<li>behavior of “auto”
</ul>
<h3 id="hyphenation-the-hyphens-property">5.4 <a href="https://drafts.csswg.org/css-text-3/#hyphenation">Hyphenation: the hyphens property</a></h3>
<p>Spotty coverage.
<p>Covered, but insufficiently:
<ul>
<li>manual value
</ul>
<p>Missing tests:
<ul>
<li>applies to inlines
<li>No test of Animation type.
<li>Affects intrinsic sizing
<li>none value
<li>none does not suppress wrapping after an actual hyphen
<li>basic behavior of auto when lang is declared and there’s no soft hyphen
<li>However, if, even after breaking at such opportunities, a portion of that word is is still too long to fit on one line, an automatic hyphenation opportunity may be used.
</ul>
<h3 id="overflow-wrapping-the-overflow-wrapword-wrap-property">5.5 <a href="https://drafts.csswg.org/css-text-3/#overflow-wrap-property">Overflow Wrapping: the overflow-wrap/word-wrap property</a></h3>
<p>Partial coverage.
<p>Missing tests:
<ul>
<li>No test of Animation type.
</ul>
<h3 id="shaping-across-intra-word-breaks">5.6 <a href="https://drafts.csswg.org/css-text-3/#word-break-shaping">Shaping Across Intra-word Breaks</a></h3>
<p>Good Coverage.
<h2 id="alignment-and-justification">6 <a href="https://drafts.csswg.org/css-text-3/#justification">Alignment and Justification</a></h2>
<p>Test only needed in subsection.
<h3 id="text-alignment-the-text-align-shorthand">6.1 <a href="https://drafts.csswg.org/css-text-3/#text-align-property">Text Alignment: the text-align shorthand</a></h3>
<p>Partial Coverage.
<p>Missing tests:
<ul>
<li>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.
<li>If the UA chooses to adjust the text, then it must ensure that tab stops continue to line up
<li>“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
</ul>
<h3 id="default-text-alignment-the-text-align-all-property">6.2 <a href="https://drafts.csswg.org/css-text-3/#text-align-all-property">Default Text Alignment: the text-align-all property</a></h3>
<p>No Tests.
<h3 id="last-line-alignment-the-text-align-last-property">6.3 <a href="https://drafts.csswg.org/css-text-3/#text-align-last-property">Last Line Alignment: the text-align-last property</a></h3>
<p>Almost no automated tests.
<h3 id="justification-method-the-text-justify-property">6.4 <a href="https://drafts.csswg.org/css-text-3/#text-justify-property">Justification Method: the text-justify property</a></h3>
<p>Light coverage.
<p>Note: all values (other than auto) are tested, but the tests are minimal. Not sure we can do better though.
<p>Missing tests:
<ul>
<li>Applies to inlines
<li>No test of Animation type.
</ul>
<p>Untestable(?):
<ul>
<li>behavior of “auto”
</ul>
<h4 id="expanding-and-compressing-text">6.4.1 <a href="https://drafts.csswg.org/css-text-3/#expanding-text">Expanding and Compressing Text</a></h4>
<p>No tests.
<p>Missing tests:
<ul>
<li>whether a typographic character unit provides a justification opportunity is controlled by the text-justify value of its parent;
<li>whether a justification opportunity exists between two consecutive typographic character units is determined by the text-justify value of their nearest common ancestor.
<li>UAs must not break required ligatures or otherwise disable features required to correctly shape complex scripts
<li>… and maybe more
</ul>
<h4 id="handling-symbols-and-punctuation">6.4.2 <a href="https://drafts.csswg.org/css-text-3/#justify-symbols">Handling Symbols and Punctuation</a></h4>
<p>No tests.
<p>Not sure what is testable though
<h4 id="unexpandable-text">6.4.3 <a href="https://drafts.csswg.org/css-text-3/#justify-limits">Unexpandable Text</a></h4>
<p>No tests.
<p>Missing tests:
<ul>
<li>TBD…
</ul>
<h4 id="cursive-scripts">6.4.4 <a href="https://drafts.csswg.org/css-text-3/#justify-cursive">Cursive Scripts</a></h4>
<p>No automated tests.
<h4 id="minimum-requirements-for-auto-justification">6.4.5 <a href="https://drafts.csswg.org/css-text-3/#justify-algos">Minimum Requirements for auto Justification</a></h4>
<p>No Tests
<h2 id="spacing">7. <a href="https://drafts.csswg.org/css-text-3/#spacing">Spacing</a></h2>
<p>Test only needed in subsections.
<h3 id="word-spacing-the-word-spacing-property">7.1 <a href="https://drafts.csswg.org/css-text-3/#word-spacing-property">Word Spacing: the word-spacing property</a></h3>
<p>Almost No tests.
<p>Missing tests:
<ul>
<li>applies to inlines
<li>inherit lengths as absolute
<li>No test of Animation type.
<li>computed / resolved value of normal
<li><length> Specifies extra spacing in addition
<li>negative values are allowed
<li>doesn’t do anything between words defined by text analysis like in Thai, only on actual word separators
<li>if a word-separating character has a zero advance width (such as the zero width space U+200B) then the user agent must not create an additional spacing between words.
<li>General punctuation and fixed-width spaces (such as U+3000 and U+2000 through U+200A) are not considered word-separator characters.
<li>word-spacing and bidi
</ul>
<p>Problematic test
<ul>
<li>text-word-spacing-001.html is wrong, the property no longer takes percentages
</ul>
<h3 id="tracking-the-letter-spacing-property">7.2 <a href="https://drafts.csswg.org/css-text-3/#letter-spacing-property">Tracking: the letter-spacing property</a></h3>
<p>Spotty Coverage.
<p>Missing tests:
<ul>
<li>applies to inlines
<li>No test of Animation type.
<li>is in addition to any word-spacing
<li>inherit lengths as absolute
<li><length> Specifies extra spacing in addition
<li>negative values are allowed
<li>For legacy reasons, a computed letter-spacing of zero yields a resolved value (getComputedStyle() return value) of normal.
<li>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.
<li>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
<li>However, ligatures and other font features specified via the low-level font-feature-settings property take precedence over this rule
</ul>
<h4 id="cursive-scripts">7.2.1 <a href="https://drafts.csswg.org/css-text-3/#cursive-tracking">Cursive Scripts</a></h4>
<p>No Tests.
<p>Not sure this can be tested automatically.
<h3 id="shaping-across-element-boundaries">7.3 <a href="https://drafts.csswg.org/css-text-3/#boundary-shaping">Shaping Across Element Boundaries</a></h3>
<p>Good Coverage.
<h2 id="edge-effects">8 <a href="https://drafts.csswg.org/css-text-3/#edge-effects">Edge Effects</a></h2>
<p>Test only needed in subsection.
<h3 id="first-line-indentation-the-text-indent-property">8.1 <a href="https://drafts.csswg.org/css-text-3/#text-indent-property">First Line Indentation: the text-indent property</a></h3>
<p>Partial Coverage.
<p>Missing tests:
<ul>
<li>length values
<li>No test of Animation type.
<li>applies to first line only
<li>hanging keyword
<li>applied to the correct side in rtl
<li>each-line keyword
</ul>
<h3 id="hanging-punctuation-the-hanging-punctuation-property">8.2 <a href="https://drafts.csswg.org/css-text-3/#hanging-punctuation-property">Hanging Punctuation: the hanging-punctuation property</a></h3>
<p>Spotty Coverage.
<p>All values tested.
<p>Missing tests:
<ul>
<li>applies to inlines
<li>No test of Animation type.
<li>Affects intrinsic sizing
<li>each value has a test, and checks with some characters, but there isn’t a test for every relevant unicode character
<li>it is not considered when measuring the line’s contents for […] alignment
<li>it is not considered when measuring the line’s contents for […] justification
<li>Non-zero inline-axis borders or padding between a hangable mark and the edge of the line prevent the mark from hanging
<li>At most one punctuation character may hang at each edge of the line.
<li>is still counted as part of the scrollable overflow region
</ul>
<h3 id="bidirectionality-and-line-boxes">8.3 <a href="https://drafts.csswg.org/css-text-3/#bidi-linebox">Bidirectionality and Line Boxes</a></h3>
<p>No tests.
<p>Missing tests:
<ul>
<li>if its containing block has unicode-bidi: plaintext [CSS-WRITING-MODES-3], the line box’s inline base direction must be determined by the inline base direction of the bidi paragraph to which it belongs
<ul>
<li>An empty line box (i.e. one that contains no atomic inlines or characters other than the line-breaking character, if any), takes its inline base direction from the preceding line box (if any), or, if this is the first line box in the containing block, then from the direction property of the containing block.
</ul>
</ul>
<h2 id="appendix-a-text-processing-order-of-operations"><a href="https://drafts.csswg.org/css-text-3/#order">Appendix A: Text Processing Order of Operations</a></h2>
<p>No Tests. Probably not needed anyway.
<h2 id="appendix-b-conversion-to-plaintext"><a href="https://drafts.csswg.org/css-text-3/#plaintext">Appendix B: Conversion to Plaintext</a></h2>
<p>No Tests.
<p>Missing tests:
<ul>
<li>§4.1.1 Phase I: Collapsing and Transformation is applied and any sequence of collapsible spaces at the beginning of a block or immediately following a forced line break is removed.
</ul>
<h2 id="appendix-c-default-ua-stylesheet"><a href="https://drafts.csswg.org/css-text-3/#default-stylesheet">Appendix C: Default UA Stylesheet</a></h2>
<p>Tests not needed.
<h2 id="appendix-d-scripts-and-spacing"><a href="https://drafts.csswg.org/css-text-3/#script-groups">Appendix D: Scripts and Spacing</a></h2>
<p>Tests not needed?
<h2 id="appendix-e-characters-and-properties"><a href="https://drafts.csswg.org/css-text-3/#character-properties">Appendix E: Characters and Properties</a></h2>
<p>No Tests.
<p>Missing tests:
<ul>
<li>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:
<li>Grapheme clusters formed with an Enclosing Mark (Me) of the Common script are considered to be Other Symbols (So) 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 (Zs) as the base are considered to be Modifier Symbols (Sk). 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>
<h2 id="appendix-f-tagging-content-by-writing-system"><a href="https://drafts.csswg.org/css-text-3/#script-tagging">Appendix F. Tagging Content by Writing System</a></h2>
<p>Partial Coverage.
<p>Each of the diverse properties that take the content language into account is tested, except tested on text-justification:auto, but probably not testable anyway.
<p>Missing tests:
<ul>
<li>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.
<li>if the writing system to specified to be one of the Jpan, Hira [ISO15924] codes, then the writing system is Japanese.
<li>if the writing system to specified to be one of the Kore, Hang, or Jamo [ISO15924] codes, then the writing system is Korean.
</ul>
<h2 id="appendix-g-small-kana-mappings"><a href="https://drafts.csswg.org/css-text-3/#small-kana">Appendix G. Small Kana Mappings</a></h2>
<p>Adequate Coverage.
<p>Tested via the text-transform property.