CSS Text 3 test coverage report

The test coverage information in this specification covers wpt/css/css-text/ and subdirectories, as well as those tests in wpt/css/CSS2/ and subdirectories that relate to this specification.

Tests not needed for this section.

Tests not really needed for this section; could possibly test that css-wide keywords apply to every property.

Tests not needed for this section: these are definitions, they get tested through their application, not by themselves.

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

Possible additions:

• turning the content of example 1 into tests (first, check that it’s not already done).

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

This section has good test coverage overall, and very good i18n coverage in particular.

Missing tests:

• no test of Animation type.

• Applies to text

Possible additions:

• An automated test for plain text copy&paste not applying transforms. Not clear such an automated test is possible, but it would be nice to have one if it were.

This section has adequate test coverage.

This section has generally good coverage.

Missing tests:

• no test of Animation type

This section has adequate test coverage.

This section has good overall test coverage, particularly through tests for § 4 White Space Processing & Control Characters and subsections, and longhand properties.

Missing tests:

• No test of Animation type

• Intrinsic (min and max) sizing tests for normal and nowrap.

• shorthand to longhand expansion involving white-space-trim values and preserve-spaces

This section has reasonably good test coverage.

Missing tests:

• “As required by Unicode, unsupported Default_ignorable characters must be ignored for text rendering”

This section has limited direct coverage, but extensive coverage through the white-space shorthand.

Missing tests:

• any direct tests as a longhand (other than syntax and inheritance)

• tests of the preserve-spaces value (direct or indirect)

• tests of the discard value (direct or indirect)

This section mostly lacks tests

This section has good test coverage. Most tests to be found in subsections.

This section has good test coverage, most parts are well exercised.

Missing tests:

• If white-space-collapse is set to preserve-spaces, each tab and segment break is converted to a space.

This section has good test coverage, all parts are well exercised.

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

This section has good test coverage.

Missing test:

• Applies to text

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

This property is tested extensively through its shorthands, but not directly.

Missing test:

• preserved segment breaks are forced line breaks (probably tested already, but need to find those tests)

• CR and LF line breaking class are forced line breaks

• Direct tests of this property as a longhand

This section lacks tests.

This section does not need tests.

This section lacks tests.

This property has limited coverage.

Missing test:

• tests for values other than balance

• Direct tests of this property as a longhand

This section has limited coverage.

This section has partial test coverage.

Missing tests:

• 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.

• Line breaking classes CM and SG must be honored

Untestable(?):

• UAs that allow wrapping at punctuation other than spaces should prioritize breakpoints. […]

This section deals in generalities rather than specific requirements. Exhaustive coverage is neither practical nor needed, as more specific requirements are made in different sections, and can be tested there.

Nonetheless, this can be a good section to host tests for i18n requirements not covered in detail by the spec.

Possible additions:

• tests for at least one language with line breaking based on orthographic syllable boundaries

• Basic line breaking tests for some languages mentioned: Javanese, Balinese, Yi

This section has partial test coverage.

Missing tests:

• Applies to text

• No test of Animation type.

• affects intrinsic sizing (tested for word-break:break-word)

• treating non-letter typographic character units belonging to the NU, AL, AI, or ID Unicode line breaking classes

• any typographic character units resolving to the any typographic letter units (and any typographic character units resolving to the NU (“numeric”), AL (“alphabetic”), or SA (“Southeast Asian”) line breaking classes

• effect of word-break:keep-all on NU and AI classes

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

• does not suppress wbr (tested with auto-phrase, but not with keep-all or manual)

• More tests for “does not affect rules governing the soft wrap opportunities created around punctuation

This section has basic but adequate coverage

This section is untested.

This section has basic but adequate coverage

This section is untested, but it is not clear how it could be.

This section has extensive test coverage for CJK.

Missing tests:

• applies to text

• affects intrinsic sizing

• Line breaking classes CM and SG must be honored even with line-break: anywhere

Untestable(?):

• behavior of “auto”

This section has partial test coverage.

Missing tests:

• Applies to text

• “Automatic hyphenation opportunities within a word must be ignored if the word contains a conditional hyphen (shy or U+00AD), in favor of the conditional hyphen(s)”

• “However, if, even after breaking at such opportunities, a portion of that word is still too long to fit on one line, an automatic hyphenation opportunity may be used.”

This section has partial coverage.

Missing tests:

• applies to text

• inheritance

• the UA must insert the string according to the typographic conventions of the content language

Likely untestable:

• when the UA truncates the string (which it may not do), it must not truncate part of a typographic character unit.

This section lacks tests.

This section has limited coverage.

Missing tests:

• applies to text

• inherited

• If the third value is missing, it is the same as the second.

• tests of the two-value syntax (but not just syntax tests, check that it has an effect)

• tests of the 3 value syntax with auto in positions other than first (but not just syntax tests, check that it has an effect)

This section lacks tests.

This section has fairly good test coverage.

Missing tests:

• Applies to text

• in the case of auto-phrase, opportunities brought by anywhere only kick in after those from normal

• No test of Animation type

Tests only needed in subsections.

This section has partial test coverage.

Missing tests:

• tests for the < > value

• If (after justification, if any) the inline contents of a line box are too long to fit within it, then the contents are start-aligned: any content that doesn’t fit overflows the line box’s end edge.

• If the UA chooses to adjust the text, then it must ensure that tab stops continue to line up

• “Values other than justify-all or match-parent are assigned to text-align-all and reset text-align-last to auto.”, and being a shorthand in general

This section lacks tests.

This section lacks tests.

This section has fairly good test coverage: all value combinations for text-align / text-align-last are exercised, except for text-align-last: match-parent (which is exercised, but in a more limited way).

Missing tests:

• tests for Animation type

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

Missing tests:

• Applies to text

• no-compress

• ruby

Untestable(?):

• behavior of auto

This section lacks tests.

Missing tests:

• whether a typographic character unit provides a justification opportunity is controlled by the text-justify value of its parent;

• whether a justification opportunity exists between two consecutive typographic character units is determined by the text-justify value of their nearest common ancestor.

• UAs must not break required ligatures or otherwise disable features required to correctly shape complex scripts

• … and maybe more

This section lacks tests. Not sure what is testable though.

This section has basic test coverage.

Missing tests:

• Values of text-align-last other than justify

• A broader range of non-stretchable content that just an empty span with padding

This section lacks automated tests.

This section lacks tests.

This section has basic coverage.

Missing tests:

• not inherited

• animation type

• the contents of descendants that establish independent formatting contexts are skipped.

• works accross block containers within a single formatting context

• interaction with floats

• interaction with indents

Tests only needed in subsections.

This section has limited test coverage.

Missing tests:

• Applies to text

• inherit lengths as absolute

• values may be negative

• computed / resolved value of normal

• should be applied half on each side of the character unless otherwise dictated by typographic tradition.

• doesn’t do anything between words defined by text analysis like in Thai, only on actual word separators

• works on the Ethiopic word space (U+1361), the Aegean word separators (U+10100,U+10101), the Ugaritic word divider (U+1039F), and the Phoenician Word Separator (U+1091F).

• word-spacing and bidi

This section has partial test coverage.

Missing tests:

• Applies to text

• percentage

• Due to issue 1518, some/many tests in this section should be converted from MUST to SHOULD.

• inherit lengths as absolute

• For legacy reasons, a computed letter-spacing of zero yields a resolved value (getComputedStyle() return value) of normal.

• However, ligatures and other font features specified via the low-level font-feature-settings property take precedence over this rule

This section lacks tests. Not sure automated tests are possible.

This section lacks tests.

This section has spotty coverage.

This section does not need direct tests: the definition given here is exercised by ''text-autospace: ideograph-alpha'' and ''text-autospace: ideograph-numeric''.

This section has spotty test coverage.

The following aspects lack tests:

• inheritance

• animation type

• applies to text

• tests for trim-auto, allow-end, auto values

This section has basic test coverage.

The following aspects lack tests:

• The UA must not use the hwid feature or otherwise substitute halfwidth forms as switching to halfwidth glyphs can change the glyph shape which is not acceptable here.

• changing font sizes

This section is mostly definitions, which are tested through their use in other sections, rather than needing tests of their own.

However, there are normative statements, so far untested, notably the classification of fullwidth colon punctuation and fullwidth dot punctuation under either the fullwidth closing punctuation category or the fullwidth middle dot punctuation category.

This section is an example, and doesn’t need tests.

This section lacks tests.

This section has good test coverage.

Tests only needed in subsections.

This section has adequate test coverage.

Test coverage TBD. Partly tested through § 9.2.1 Hanging Punctuation: the hanging-punctuation property partly through § 4.3.2 Phase II: Trimming and Positioning.

This section has spotty test coverage. All values have tests.

Missing tests:

• No test of Animation type.

• Applies to text

• Affects intrinsic sizing

• each value has a test, and checks with some characters, but there isn’t a test for every relevant unicode character

• it is not considered when measuring the line’s contents for […] alignment

• it is not considered when measuring the line’s contents for […] justification

• Non-zero inline-axis borders or padding between a hangable mark and the edge of the line prevent the mark from hanging

• At most one punctuation character may hang at each edge of the line.

• should be treated as ink overflow

This section lacks tests.

Tests probably not needed for this section, as it is exercised through the rest of the specification.

This section lacks tests.

Tests not needed for this section.

Tests not needed for this section: these are definitions, they get tested through their application, not by themselves.

This section lacks tests.

This section has partial test coverage. Each of the various properties that take the content language into account is tested, except tested on text-justification:auto, but probably not testable anyway.

Missing tests:

• if the writing system to specified to be one of the Hant, Hans, Hani, Hanb, or Bopo ISO15924 codes, then the writing system is Chinese.

• if the writing system to specified to be one of the Jpan, Hira ISO15924 codes, then the writing system is Japanese.

• if the writing system to specified to be one of the Kore, Hang, or Jamo ISO15924 codes, then the writing system is Korean.

This section has good test coverage, through the text-transform property.

This section has partial test coverage.

Missing tests:

• If a word or phrase is immediately followed by one or more of the following characters, the user agent must consider them to be part of the preceeding word or phrase

• Punctuation is not a phrase by itself […]

Likely untestable:

• The user agent must not place a word or phrase boundary between characters that compose a single typographic character unit

Tests not needed for this section.

Tests not needed for this section.

Tests not needed for this section.