Copyright © 2007 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This CSS3 module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, text decoration and text transformation.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This CSS module has been produced as a combined effort of the W3C Internationalization Activity, and the Style Activity and is maintained by the CSS Working Group. It also includes contributions made by participants in the XSL Working Group (members only).
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This Text module and a separate (upcoming) Writing Modes module replace and obsolete the May 2003 CSS3 Text Module Candidate Recommendation. Since this is a thorough overhaul of the previous CR, a list of changes has been provided.
Feedback on this draft should be posted to the (archived) public mailing list www-style@w3.org (see instructions) with [css3-text] in the subject line. You are strongly encouraged to complain if you see something stupid in this draft. The editors will do their best to respond to all feedback.
If you have implemented properties from the May 2003 CSS3 Text CR please let us know so we can take that into account as we redraft the spec. You can post to www-style (public), post to the CSS WG mailing list (Member-restricted), or email fantasai directly (personal).
The following features are at risk and may be cut from the spec during
its CR period: the ‘text-outline
’ property, the ‘unrestricted
’ value of ‘text-wrap
’
text-decoration-line
’ property
text-decoration-color
’ property
text-decoration-style
’ property
text-decoration
’ property
text-decoration-skip
’ property
text-underline-position
’ property
text-shadow
’ property
text-outline
’
property
[document here]
Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification. All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
Examples in this specification are introduced with the words “for
example” or are set apart from the normative text with
class="example"
, like this:
This is an example of an informative example.
Informative notes begin with the word “Note” and are set apart from
the normative text with class="note"
, like this:
Note, this is an informative note.
Conformance to CSS Text Level 3 is defined for three classes:
A style sheet is conformant to CSS Text Level 3 if all of its declarations that use properties defined in this module have values that are valid according to the generic CSS grammar and the individual grammars of each property as given in this module.
A renderer is conformant to CSS Text Level 3 if, in addition to interpreting the style sheet as defined by the appropriate specifications, it supports all the properties defined by CSS Text Level 3 by parsing them correctly and rendering the document accordingly. However the inability of a UA to correctly render a document due to limitations of the device does not make the UA non-conformant. (For example, a UA is not required to render color on a monochrome monitor.)
An authoring tool is conformant to CSS Text Level 3 if it writes syntactically correct style sheets, according to the generic CSS grammar and the individual grammars of each property in this module.
UAs must treat as invalid any properties or values they do not support. Experimental implementations of a feature should support only a vendor-prefixed syntax for the property/value.
text-transform
’ propertyName: | text-transform |
---|---|
Value: | none | capitalize | uppercase | lowercase | fullwidth | large-kana |
Initial: | none |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property transforms text for the styling purpose. Values have the following meanings:
none
capitalize
uppercase
lowercase
fullwidth
should try fallback if the glyph is missing. should it also check fullwidth variants before falling back to next font?
large-kana
need to work on interoperability with OpenType and CSS3 Fonts font-variant:ruby
Although limited, the case mapping process has some language dependencies. Some well known examples are Turkish and Greek. If the content language is known then any such language-specific rules must be used.
The case mapping rules for the character repertoire specified by the Unicode Standard can be found on the Unicode Consortium Web site. [UNICODE] Only characters belonging to bicameral scripts are affected.
The definition of fullwidth and halfwidth forms can be found on the Unicode consortium web site at [UAX11].
The following example converts the ASCII characters in abbreviations in Japanese to their fullwidth variants so that they lay out and line break like ideographs:
abbr:lang(ja) { text-transform: fullwidth; }
The source text of a document often contains formatting that is not relevant to the final rendering: for example, breaking the source into segments (lines) for ease of editing or adding white space characters such as tabs and spaces to indent the source code. CSS white space processing allows the author to control interpretation of such formatting: to preserve or collapse it away when rendering the document.
Segments in the document source can be separated by a carriage return (U+000D), a linefeed (U+000A) or both (U+000D U+000A), or by some other mechanism that identifies the beginning and end of document segments, such as the SGML RECORD-START and RECORD-END tokens. If no segmentation rules are specified for the document language, each line feed (U+000A), carriage return (U+000D) and CRLF sequence (U+000D U+000A) in the text is considered a segment break. (This default rule also applies to generated content.) In CSS, each such segment break is treated as a single line feed character (U+000A).
White space processing in CSS interprets white space characters for rendering: it has no effect on the underlying document data. In the context of CSS, the document white space set is defined to be any space characters (Unicode value U+0020), tab characters (U+0009), and line feeds (U+000A).
Note that the document parser may have not only normalized segment breaks, but also collapsed other space characters or otherwise processed white space according to markup rules. Because CSS processing occurs after the parsing stage, it is not possible to restore these characters for styling. Therefore, some of the behavior specified below can be affected by these limitations and may be user agent dependent.
Control characters other than U+0009 (tab), U+000A (line feed), U+0020 (space), and U+202x (bidi formatting characters) are treated as characters to render in the same way as any normal character. Copied from CSS2.1 but this has got to be wrong.
white-space-collapsing
’ propertyThis section is still under discussion and may change in future drafts.
Name: | white-space-collapsing |
---|---|
Value: | collapse | discard | [ [preserve | preserve-breaks] && trim-inner ] |
Initial: | collapse |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value |
Rename to white-space-trim or white-space-adjust?
white-space-collapsing has an ‘ing
’ and is confusing with XSL
This property declares whether and how white space inside the element is collapsed. Values have the following meanings, which must be interpreted according to the white space processing rules:
collapse
preserve
preserve-breaks
collapse
’, but preserves segment breaks as forced
line breaks.
discard
trim-inner
For each inline (including anonymous inlines), white space characters are handled as follows, ignoring bidi formatting characters as if they were not there:
If ‘white-space-collapsing
’ is set to
‘collapse
’ or ‘preserve-breaks
’, white space characters are
considered collapsible and are processed by
performing the following steps:
white-space-collapsing
’ is not
‘preserve-breaks
’, line feed
characters are transformed for rendering according to the line break transformation rules.
If ‘white-space-collapsing
’ is set to
‘preserve
’, any sequence of
spaces (U+0020) unbroken by an element boundary is treated as a sequence
of non-breaking spaces. However, a line breaking opportunity exists at
the end of the sequence.
If ‘white-space-collapsing
’ is set to
‘discard
’, the first white space
character in every white space sequence is converted to a zero width
non-joiner (U+200C) and the rest of the sequence is removed.
Then, the entire block is rendered. Inlines are laid out, taking bidi
reordering into account, and wrapping as specified by the ‘text-wrap
’ property.
As each line is laid out,
text-wrap
’ set to ‘normal
’ or ‘suppress
’ the UA may visually collapse them.
Consider the following markup fragment, taking special note of spaces (with varied backgrounds and borders for emphasis and identification):
<ltr>A <rtl> B </rtl> C</ltr>
where the <ltr>
element represents a left-to-right
embedding and the <rtl>
element represents a
right-to-left embedding. If the ‘white-space-collapsing
’ property is set
to ‘collapse
’, the above
processing model would result in the following:
This would leave two spaces, one after the A in the left-to-right embedding level, and one after the B in the right-to-left embedding level. This is then ordered according to the Unicode bidirectional algorithm, with the end result being:
A BC
Note that there are two spaces between A and B, and none between B and C. This is best avoided by putting spaces outside the element instead of just inside the opening and closing tags and, where practical, by relying on implicit bidirectionality instead of explicit embedding levels.
When line feeds are collapsible, they are either transformed into a space (U+0020) or removed depending on the script context before and after the line break.
The script context is determined by the Unicode-given script value [UAX24] of the first character that side of the line feed. However, characters such as punctuation that belong to the COMMON and INHERITED scripts are ignored in this check; the next character is examined instead. The UA must not examine characters outside the block and may limit its examination to as few as four characters on each side of the line feed. If the check fails to find an acceptable script value (i.e. it has hit the check limits), then the script context is neutral.
Note that the white space processing rules have already removed any tabs and spaces after the line feed before these checks take place.
IE removes line feed not only between two Hiragana but also Hiragana and fullwidth alphabets. Firefox, Opera, and Safari does not remove line breaks even between two Hiragana. Should fullwidth Latin be considered in this rule?
text-autospace
’ property is set to add extra
spaces for the combination of the character before the line feed and
after, then the line break is removed.
Any feedback on this behavior is appreciated. Now that we have text-autospace property, it makes sense to favor it than inserting spaces. However, we also want to preserve backward compatibility as much as possible. That is the reason why the line feed should be removed only if text-autospace inserts spaces instead.
Comments on how well this would work in practice would be very much appreciated, particularly from people who work with Thai and similar scripts.
white-space
’ propertyName: | white-space |
---|---|
Value: | normal | pre | nowrap | pre-wrap | pre-line |
Initial: | not defined for shorthand properties |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | see individual properties |
The ‘white-space
’ property is a shorthand for
the ‘white-space-collapsing
’ and ‘text-wrap
’
properties. Not all combinations are represented. Values have the
following meanings:
normal
white-space-collapsing
’ to ‘collapse
’ and ‘text-wrap
’ to
‘normal
’
pre
white-space-collapsing
’ to ‘preserve
’ and ‘text-wrap
’ to
‘none
’
nowrap
white-space-collapsing
’ to ‘collapse
’ and ‘text-wrap
’ to
‘none
’
pre-wrap
white-space-collapsing
’ to ‘preserve
’ and ‘text-wrap
’ to
‘normal
’
pre-line
white-space-collapsing
’ to ‘preserve-breaks
’ and ‘text-wrap
’ to
‘normal
’
The following informative table summarizes the behavior of various
‘white-space
’ values:
New Lines | Spaces and Tabs | Text Wrapping | |
---|---|---|---|
normal | Collapse | Collapse | Wrap |
pre | Preserve | Preserve | No wrap |
nowrap | Collapse | Collapse | No wrap |
pre-wrap | Preserve | Preserve | Wrap |
pre-line | Preserve | Collapse | Wrap |
For most scripts, in the absence of hyphenation a line break occurs only at word boundaries. Many writing systems use spaces or punctuation to explicitly separate words, and line break opportunities can be identified by these characters. Scripts such as Thai, Lao, and Khmer, however, do not use spaces or punctuation to separate words. Although the zero width space (U+200B) can be used as an explicit word delimiter in these scripts, this practice is not common. As a result, a lexical resource is needed to correctly identify break points in such texts.
In several other writing systems, (including Chinese, Japanese, Yi, and sometimes also Korean) a line break opportunities are based on syllable boundaries, not words. In these systems a line can break anywhere except between certain character combinations. Additionally the level of strictness in these restrictions can vary with the typesetting style.
CSS does not fully define where line breaking opportunities occur, however some controls are provided to distinguish common variations.
Floated and absolutely-positioned elements do not introduce a line breaking opportunity. The line breaking behavior of a replaced element is equivalent to that of a Latin character.
There is a question of what the default line breaking of Korean should be, and whether dictionary-based breaking is needed for typical layout (e.g. novels).
It is not clear whether this section handles Southeast Asian scripts well. Additionally, some guidance should be provided on how to break or not break Southeast Asian in the absence of a dictionary.
line-break
’ propertyThis property specifies line break opportunities for CJK scripts.
CSS distinguishes between three levels of strictness in the rules for implicit line breaking in CJK text. The precise set of rules in effect for the strict and loose levels is up to the UA and should follow language conventions. However, this specification does recommend that:
Information on line breaking conventions can be found in [JIS4051] for Japanese, [ZHMARK] for Chinese, and [?] for Korean, and in [UAX14] for all scripts in Unicode.
Any guidance for appropriate references here would be much appreciated.
Name: | line-break |
---|---|
Value: | auto | newspaper | normal | strict | keep-all |
Initial: | auto |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value |
This property specifies what set of line breaking restrictions are in effect within the element. Values have the following meanings:
auto
newspaper
normal
strict
normal
’.
keep-all
word-break
’ propertyThis property specifies line break opportunities for non-CJK scripts.
Name: | word-break |
---|---|
Value: | normal | break-all | hyphenate |
Initial: | normal |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value |
normal
break-all
hyphenate
This value is proposed to replace ‘hyphenate
’ property currently defined in Generated
Content for Paged Media draft. Note there are other values in the
editor's draft, which could be added as ‘word-break: hyphenate-all
’ and ‘word-break: none
’...
When shaping scripts such as Arabic are allowed to break within words
due to ‘break-all
’ or hyphenation,
the characters must still be shaped as if the word were not broken.
Text wrapping is controlled by the ‘text-wrap
’ and ‘word-wrap
’
properties:
text-wrap
’ propertyName: | text-wrap |
---|---|
Value: | normal | unrestricted | none | suppress |
Initial: | normal |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value |
This property specifies the mode for text wrapping. Possible values:
normal
none
unrestricted
suppress
normal
’.
Regardless of the ‘text-wrap
’ value, lines always break at
forced breaks: for all values, line-breaking behavior defined for the BK,
CR, LF, CM NL, and SG line breaking classes in [UAX14] must be honored.
When ‘text-wrap
’ is set to ‘normal
’ or ‘suppress
’, UAs that allow breaks at
punctuation other than spaces should prioritize breakpoints. For example,
if breaks after slashes have a lower priority than spaces, the sequence
"check /etc" will never break between the ‘/
’ and the ‘e
’. The UA may use the width of the containing
block, the text's language, and other factors in assigning priorities. As
long as care is taken to avoid such awkward breaks, allowing breaks at
appropriate punctuation other than spaces is recommended, as it results in
more even-looking margins, particularly in narrow measures.
text-wrap: suppress
’ in presenting a
footerThe priority of breakpoints can be set to reflect the intended grouping of text.
Given the rules
footer { text-wrap: suppress; /* inherits to all descendants */ }
and the following markup:
<footer> <venue>27th Internationalization and Unicode Conference</venue> • <date>April 7, 2005</date> • <place>Berlin, Germany</place> </footer>
In a narrow window the footer could be broken as
27th Internationalization and Unicode Conference • April 7, 2005 • Berlin, Germany
or in a narrower window as
27th Internationalization and Unicode Conference • April 7, 2005 • Berlin, Germany
but not as
27th Internationalization and Unicode Conference • April 7, 2005 • Berlin, Germany
word-wrap
’ propertyName: | word-wrap |
---|---|
Value: | normal | break-word |
Initial: | normal |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value |
This property specifies whether the UA may break within a word to
prevent overflow when an otherwise-unbreakable string is too long to fit
within the line box. It only has an effect when ‘text-wrap
’ is
either ‘normal
’ or ‘suppress
’. Possible values:
normal
break-word
If Korean is set to keep-all, and the word doesn't fit,
should it break anyway? Do we need an ‘auto
’ value here for scripts where it's OK to
break even if it's not ideal vs. scripts (like Latin) where breaking in
the middle of a word is wrong?
text-align
’ propertyName: | text-align |
---|---|
Value: | [start | end | left | right | center | justify | match-parent ] || <string> |
Initial: | start |
Applies to: | block containers |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value, except for ‘match-parent ’ (see prose)
|
This property describes how inline contents of a block are horizontally aligned if the contents do not completely fill the line box. Values have the following meanings:
start
end
left
left
’ aligns to
the edge of the line box that would be the start edge for left-to-right
text.
right
right
’ aligns to
the edge of the line box that would be the end edge for left-to-right
text.
center
justify
text-justify
’ property.
<string>
text-align
’
will align (see the section on horizontal
alignment in a column for details and an example).
match-parent
inherit
’ except that an inherited value of
‘start
’ or ‘end
’ is calculated against its parent's
‘direction
’ value and results in
a computed value of either ‘left
’
or ‘right
’.
A block of text is a stack of line boxes. In
the case of ‘start
’, ‘end
’, ‘left
’, ‘right
’ and ‘center
’, this property specifies how the
inline boxes within each line box align within the line box: alignment is
not with respect to the viewport or
containing block. In the case of ‘justify
’, the UA may stretch the inline boxes
in addition to adjusting their positions. (See also the ‘text-justify
’, ‘letter-spacing
’ and ‘word-spacing
’.)
A keyword value may be specified in conjunction with the <string>
value; if it is not given, it defaults to ‘end
’. This value is used when <string>
alignment is applied to boxes that are not table cells, when the alignment
character appears more than once, and when the text wraps to multiple
lines. Also, if the column is wide enough that the string value alone does
not determine the alignment of its <string>-aligned contents, the
fallback value of the first cell in the column with a <string>
alignment is used to determine the aligned contents' alignment within the
column. Use this value also to determine alignment wrt
the axis instead of using the "character directionality", which is not
defined for punctuation...
text-align-last
’ propertyName: | text-align-last |
---|---|
Value: | start | end | left | right | center | justify |
Initial: | start |
Applies to: | block containers |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value |
This property describes how the last line of a block or a line right
before a forced line break is aligned when ‘text-align
’ is set to ‘justify
’. Values have the same meaning as for
‘text-align
’.
text-justify
’ propertyName: | text-justify |
---|---|
Value: | auto | [ trim || [ inter-word | inter-ideograph | inter-cluster | distribute | kashida ] ] |
Initial: | auto |
Applies to: | block containers and, optionally, inline elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value |
This property selects the justification method used when ‘text-align
’ is set to ‘justify
’. The
property applies to block containers, but the UA may (but is not required
to) also support it on inline elements. It takes the following values:
auto
One possible algorithm is to determine the behavior based
on the language of the paragraph: the UA can then choose appropriate
value for the language, like ‘trim
inter-ideograph
’ for CJK, or ‘inter-word
’ for English. Another possibility is
to use a justification method that is a universal compromise for all
scripts, e.g. the ‘distribute
’ method
with discrete scripts dropped to second priority.
inter-word
inter-ideograph
inter-cluster
distribute
text-align-last
’ property.
kashida
trim
auto
’).
When justifying text, the user agent takes the remaining space between
the ends of a line's contents and the edges of its line box, and
distributes that space throughout its contents so that the contents
exactly fill the line box. If the ‘letter-spacing
’ and ‘word-spacing
’
property values allow it, the user agent may also distribute negative
space, putting more content on the line than would otherwise fit under
normal spacing conditions. The exact justification algorithm is
UA-dependent; however, CSS provides some general guidelines which should
be followed when any justification method other than ‘auto
’ is specified.
Justification affects different types of writing systems in different ways. For justification purposes, characters are grouped as follows:
Where do scripts like Tamil fit in?
The UA may enable or break optional ligatures or use other font features such as alternate glyphs to help justify the text under any method. This behavior is not defined by CSS.
CSS defines expansion opportunities as points where the justification algorithm may alter spacing within the text. These expansion opportunities fall into priority levels as defined by the justification method. Within a line, higher priority expansion opportunities should be expanded or compressed to their limits before lower priority expansion opportunities are adjusted. (Expansion and compression limits are given by the letter-spacing and word-spacing properties.
How any remaining space is distributed once all expansion opportunities
reach their limits is up to the UA. If the inline contents of a line
cannot be stretched to the full width of the line box, then they must be
aligned as specified by the ‘text-align-last
’ property (or as
‘start
’ if ‘text-align-last
’ is ‘justify
’).
The expansion opportunity priorities for values of ‘text-justify
’
are given in the table below. Space must be distributed evenly among all
types of expansion opportunities in a given prioritization group, but may
vary within a line due to changes in the font or letter-spacing and
word-spacing values. The different types of expansion opportunities are
defined as follows:
word-spacing
’.
I'm not sure grapheme clusters are the right unit to use for some of these complex scripts...
method: | inter-word | inter-ideograph | distribute | inter-cluster | kashida | auto | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
priority: | 1st | 2nd | 1st | 2nd | 1st | 2nd | 1st | 2nd | 1st | 2nd | 3rd | 1st | 2nd |
spaces | • | • | • | • | • | ¿? | |||||||
block | • | • | • | • | • | ¿? | |||||||
clustered | • | • | • | • | • | ¿? | |||||||
cursive | • | • | • | • | • | ¿? | |||||||
discrete | • | • | • | • | • | ¿? | |||||||
connected | |||||||||||||
punctuation | • | • | • | ??? | ??? | • | ¿? | ¿? |
The ‘auto
’ column defined
above is informative.
Japanese is one of the language that prefers compression to expansion on justification. JIS X-4051 [JIS4051] defines how a text formatter can justify Japanese text. Here is one example of the interpretation of JIS X-4051 with slight modification.
word-spacing
’ property, or up to 1/4em.
text-autospace
’ property up to 1/8em.
word-spacing
’ property, or up to 1/2em.
text-autospace
’ property up to 1/2em.
The next two properties refer to the <spacing-limit> value type, which is defined as follows:
<spacing-limit>
normal
text-justify
’ property, the element's
language, and other factors.
<length> or <percentage>
word-spacing
’ propertyName: | word-spacing |
---|---|
Value: | <spacing-limit> {1,3} |
Initial: | normal |
Applies to: | all elements |
Inherited: | yes |
Percentages: | refers to width of space (U+0020) glyph |
Media: | visual |
Computed value: | ‘normal ’ or computed value
or percentage
|
This property specifies the minimum, maximum, and optimal spacing
between words. If only one value is specified, then it represents the
optimal spacing and the minimum and maximum are both ‘normal
’. If two values are specified, then the
first represents both the optimal spacing and the minimum spacing, and the
second represents the maximum spacing. If three values are specified, they
represent the optimum, minimum, and maximum respectively.
If the value of the optimum or maximum spacing is less than the value of the minimum spacing, then its used value is the minimum spacing. If the optimum spacing is greater than the maximum spacing then its used value is the maximum spacing. (This substitution occurs after inheritance.)
In the absence of justification the optimal spacing must be used. The
text justification process may alter the spacing from its optimum (see the
‘text-justify
’ property, above) but must
not violate the minimum spacing limit and should also avoid exceeding the
maximum.
Spacing is applied to each word-separator character left in the text after the white space processing rules have been applied and should be applied half on each side of the character. This is correct for Ethiopian and doesn't matter for invisible spaces, but is it correct for Tibetan? Most publications seem to add space after the tsek mark during justification. Word-separator characters include the space (U+0020), the no-break space (U+00A0), the Ethiopic word space (U+1361), the Aegean word separators (U+10100,U+10101), the Ugaritic word divider (U+1039F), and the Tibetan tsek (U+0F0B, U+0F0C). Is this list correct? If there are no word-separator characters, or if the 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. General punctuation and fixed-width spaces (such as U+3000 and U+2000 through U+200A) are not considered word-separators.
letter-spacing
’ propertyName: | letter-spacing |
---|---|
Value: | <spacing-limit>{1,3} |
Initial: | normal |
Applies to: | all elements |
Inherited: | yes |
Percentages: | refers to width of space (U+0020) glyph |
Media: | visual |
Computed value: | ‘normal ’ or computed value
or percentage
|
This property specifies the minimum, maximum, and optimal spacing between grapheme clusters. If only one value is specified, then it represents all three values. If two values are specified, then the first represents both the optimal spacing and the minimum spacing, and the second represents the maximum spacing. If three values are specified, they represent the optimum, minimum, and maximum respectively.
If the value of the optimum or maximum spacing is less than the value of the minimum spacing, then its used value is the minimum spacing. If the optimum spacing is greater than the maximum spacing then its used value is the maximum spacing. (This substitution occurs after inheritance.)
In the absence of justification the optimal spacing must be used. The
text justification process may alter the spacing from its optimum (see the
‘text-justify
’ property, above) but must
not violate the minimum spacing limit and should also avoid exceeding the
maximum. Letter-spacing is applied in addition to any word-spacing.
‘normal
’ optimum letter-spacing is
typically zero.
A grapheme cluster is what a language user considers to be a character or a basic unit of the script. The term is described in detail in the Unicode Technical Report: Text Boundaries [UAX29]. This specification relies on the default (not tailored) rules only.
Letter-spacing must not be applied at the beginning or at the end of a line. At element boundaries, the letter spacing is given by and rendered within the innermost element that contains the boundary.
For example, given the markup
<P>a<LS>b<Z>cd</Z><Y>ef</Y></LS>g</P>
and the style sheet
LS { letter-spacing: 1em; } Z { letter-spacing: 0.3em; } Y { letter-spacing: 0.4em; }
the spacing would be
a[0]b[1em]c[0.3em]d[1em]e[0.4em]f[0]g
UAs may apply letter-spacing to cursive scripts. In this case, UAs should extend the space between disjoint graphemes as specified above and extend the visible connection between cursively connected graphemes by the same amount (rather than leaving a gap). The UA may use glyph substitution or other font capabilities to spread out the letters. If the UA cannot expand a cursive script without breaking the cursive connections, it should not apply letter-spacing between grapheme clusters of that script at all.
When the resulting space between two characters is not the same as the default space, user agents should not use optional ligatures.
punctuation-trim
’ propertyName: | punctuation-trim |
---|---|
Value: | none | [start || [ end | allow-end ] || adjacent] |
Initial: | none |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value |
This property determines whether or not a fullwidth punctuation character should be trimmed (kerned) if it appears at the start or end of a line, or adjacent to another fullwidth punctuation character. Values are defined as follows:
add description for what to do if the font has kerning pair defined. add description for what to do if the character is not 1em. classes and Unicode code point should be re-reviewed.
The following example table lists the punctuation pairs affected by the
‘adjacent
’ value. It uses
halfwidth equivalents to approximate the trimming effect.
Combination | Sample Pair | Looks Like |
---|---|---|
Opening—Opening | 〔+( | 〔( |
Middle Dot—Opening | ・+( | ・( |
Closing—Opening | 〕+( | 〕( |
Ideographic Space—Opening | +( | ( |
Closing—Closing | )+〕 | )〕 |
Closing—Middle Dot | )+・ | )・ |
Closing—Ideographic Space | )+ | ) |
In the context of this property the following definitions apply:
Ps
) that belongs to the CJK Symbols and Punctuation
block (U+3000–U+303F) or is categorized as East Asian Fullwidth
(F) by [UAX11].
Also includes LEFT SINGLE QUOTATION MARK (U+2018) and LEFT DOUBLE
QUOTATION MARK (U+201C). When trimmed, the left (for horizontal text) or
top (for vertical text) half is kerned.
Pe
) that belongs to the CJK Symbols and Punctuation
block (U+3000–U+303F) or is categorized as East Asian Fullwidth
(F) by [UAX11].
Also includes RIGHT SINGLE QUOTATION MARK (U+2019) and RIGHT DOUBLE
QUOTATION MARK (U+201D). May also include fullwidth colon punctuation
and/or fullwidth dot punctuation (see below). When trimmed, the right
(for horizontal text) or bottom (for vertical text) half is kerned.
Fullwidth opening and closing punctuation must not be trimmed if the glyph is not actually fullwidth. A fullwidth glyph is one that has the same advance width as a typical Han character in the same font.
Whether fullwidth colon punctuation and fullwidth dot punctuation should be considered fullwidth closing punctuation or fullwidth middle dot punctuation depends on where in the glyph's box the punctuation is drawn. If the punctuation is centered, then it should be considered middle dot punctuation. If the punctuation is drawn to one side (left in horizontal text, top in vertical text) and the other half is therefore blank then the punctuation should be considered closing punctuation and trimmed accordingly.
The UA must classify fullwidth colon punctuation and fullwidth dot punctuation under either the fullwidth closing punctuation category or the fullwidth middle dot punctuation category as appropriate. The UA may rely on language conventions and the layout orientation (horizontal vs. vertical), and/or font information to determine this categorization. The UA may also add additional characters to any category as appropriate.
The following informative table summarizes language conventions for classifying fullwidth colon and dot punctuation:
colon punctuation | dot punctuation | |
---|---|---|
Simplified Chinese (horizontal) | closing | closing |
Simplified Chinese (vertical) | closing | closing |
Traditional Chinese | middle dot | middle dot |
Korean | middle dot | closing |
Japanese | middle dot | closing |
Note, that for Chinese fonts at least, the author observes that the standard convention is often not followed.
text-autospace
’ propertyName: | text-autospace |
---|---|
Value: | none | [ ideograph-numeric || ideograph-alpha || ideograph-space || ideograph-parenthesis ] |
Initial: | none |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | specified value |
When a run of non-ideographic or numeric characters appears inside of ideographic text, a certain amount of space is often preferred on both sides of the non-ideographic text to separate it from the surrounding ideographic glyphs. This property controls the creation of that space when rendering the text. That added width does not correspond to the insertion of additional space characters, but instead to the width increment of existing glyphs.
(A commonly used algorithm for determining this behavior is specified in JIS X-4051 [JIS4051].)
This property is additive with the ‘word-spacing
’ and ‘letter-spacing
’ [CSS21] properties. That is, the
amount of spacing contributed by the ‘letter-spacing
’ setting (if any) is added
to the spacing created by ‘text-autospace
’. The same applies
to ‘word-spacing
’.
The space added can be compressed or expanded during the justification
process as specified in the ‘text-justify
’ property.
This property applies only to the same inline element context, and can apply across elements if in the same inline element context.
Values have the following meanings:
none
ideograph-numeric
ideograph-alpha
ideograph-space
ideograph-parenthesis
punctuation
We are considering to cut ideograph-space and ideograph-parenthesis as these two, unlike others, are to fix errors in the document and are not purposed for styling. ideograph-parenthesis can also make text-justify: trim harder and more complex.
It was requested to add a value for doubling the space after periods.
Ideograph letters in this definitions includes the following characters.
text-indent
’ propertyName: | text-indent |
---|---|
Value: | [ <length> | <percentage> ] && [ hanging || each-line ]? |
Initial: | 0 |
Applies to: | block containers |
Inherited: | yes |
Percentages: | refers to width of containing block |
Media: | visual |
Computed value: | the percentage as specified or the absolute length |
This property specifies the indentation applied to lines of inline
content in a block. The indent is treated as a margin applied to the start
edge of the line box. Unless otherwise specified via the ‘each-line
’ and/or
‘hanging
’
keywords, only lines that are the first
formatted line of an element. For example, the first line of an
anonymous block box is only affected if it is the first child of its
parent element.
Values have the following meanings:
each-line
hanging
If ‘text-align
’ is ‘start
’ and ‘text-indent
’
is ‘5em
’ in left-to-right text with no
floats present, then first line of text will start 5em into the block:
Since CSS1 it has been possible to indent the first line of a block element using the 'text-indent' property.
Note that since the ‘text-indent
’ property inherits, when
specified on a block element, it will affect descendant inline-block
elements. For this reason, it is often wise to specify ‘text-indent: 0
’ on elements that are specified
‘display: inline-block
’.
hanging-punctuation
’ propertyName: | hanging-punctuation |
---|---|
Value: | none | [ first || last || [ allow-end | force-end ] ] |
Initial: | none |
Applies to: | block containers |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property determines whether a punctuation mark, if one is present, may be placed outside the line box at the start or at the end of a full line of text. Values have the following meanings:
first
last
allow-end
force-end
In all cases only one punctuation character may hang outside the edge of the line.
Need to work on the description. Add Unicode character
classes. Cover indentation as well. Check for Western use-cases. Add
hyphens
value?
Sync this against CSS2.1.
The following properties describe line decorations that are added to the
content of an element. When specified on an inline element, such
decoration affects all the boxes generated by that element; for all other
elements, the decorations are propagated to an anonymous inline box that
wraps all the in-flow inline children of the element, and to any
block-level in-flow descendants. They are not, however, further propagated
to floating and absolutely positioned descendants, nor to the contents of
inline-table
and inline-block
descendants. The value of the text-decoration-line
property on descendant elements therefore cannot have any effect on the
decoration of the ancestor; to skip descendants, use the text-decoration-skip
property.
By default underlines, overlines, and line-throughs are applied only to
text (including white space, letter spacing, and word spacing): margins,
borders, and padding are skipped. Elements containing no text, such as
images, are likewise not decorated. The text-decoration-skip
property can be used to modify this behavior, for example allowing inline
replaced elements to be underlined or requiring that white space be
skipped.
In determining the position and thickness of text decoration lines, user agents may consider the font sizes and dominant baselines of descendants, but for a given element's decoration must use the same baseline and thickness on each line. Relatively positioning a descendant moves all text decorations affecting it along with the descendant's text; it does not affect calculation of the decoration's initial position on that line. The color and line style of decorations must remain the same on all decorations applied by a given element, even if descendant elements have different color or line style values.
The following figure shows the averaging for underline:
In the three fragments of underlined text, the underline is drawn consecutively lower and thicker as the ratio of large text to small text increases.
In the following style sheet and document fragment:
blockquote { text-decoration: underline; color: blue; }
em { display: block; }
cite { color: fuchsia; }
<blockquote>
<p>
<span>
Help, help!
<em> I am under a hat! </em>
<cite> —GwieF </cite>
</span>
</p>
</blockquote>
...the underlining for the blockquote element is propagated to an
anonymous inline element that surrounds the span element, causing the
text "Help, help!" to be blue, with the blue underlining from the
anonymous inline underneath it, the color being taken from the blockquote
element. The <em>text</em>
in the em block is
also underlined, as it is in an in-flow block to which the underline is
propagated. The final line of text is fuchsia, but the underline
underneath it is still the blue underline from the anonymous inline
element.
This diagram shows the boxes involved in the example above. The rounded aqua line represents the anonymous inline element wrapping the inline contents of the paragraph element, the rounded blue line represents the span element, and the orange lines represent the blocks.
text-decoration-line
’ propertyName: | text-decoration-line |
---|---|
Value: | none | [ underline || overline || line-through ] |
Initial: | none |
Applies to: | all elements |
Inherited: | no (but see prose) |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
Specifies what line decorations, if any, are added to the element. Values have the following meanings:
text-decoration-color
’ propertyName: | text-decoration-color |
---|---|
Value: | <color> |
Initial: | currentColor |
Applies to: | all elements |
Inherited: | no |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property specifies the color of text decoration (underlines
overlines, and line-throughs) set on the element with text-decoration-line
.
text-decoration-style
’ propertyName: | text-decoration-style |
---|---|
Value: | solid | double | dotted | dashed | wave |
Initial: | solid |
Applies to: | all elements |
Inherited: | no |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property specifies the style of the line(s) drawn for text decoration specified on the element. Values have the same meaning as for the border-style properties [CSS3BG].
text-decoration
’ propertyName: | text-decoration |
---|---|
Value: | <text-decoration-line> || <text-decoration-color> || <text-decoration-style> || blink |
Initial: | none |
Applies to: | all elements |
Inherited: | no |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property is a shorthand for setting text-decoration-line
, text-decoration-color
, and
text-decoration-style
in one declaration. Omitted values are set to their initial values. A text-decoration
declaration that
omits both the text-decoration-color
and
text-decoration-style
values is backwards-compatible with CSS Levels 1 and 2.
If the blink
keyword is specified the text blinks
(alternates between visible and invisible). Conforming user agents may
simply not blink the text. Note that not blinking the text is one
technique to satisfy checkpoint
3.3 of WAI-UAAG.
The following example underlines unvisited links with a solid blue underline in CSS1 and CSS2 UAs and a navy dotted underline in CSS3 UAs.
:link {
color: blue;
text-decoration: underline;
text-decoration: navy dotted underline; /* Ignored in CSS1/CSS2 UAs */
}
text-decoration-skip
’ propertyName: | text-decoration-skip |
---|---|
Value: | none | [ images || spaces || ink || all ] |
Initial: | images |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property specifies what parts of the element's content any text decoration affecting the element must skip over. It controls all text decoration lines drawn by the element and also any text decoration lines drawn by its ancestors. Values have the following meanings:
Do we need a value that doesn't skip margins and padding?
Note that this property inherits and that descendant elements can have a
different setting. Therefore a child of an element with
text-decoration-skip: all
can cause its grandparent's
underline to be drawn by specifying text-decoration-skip:
none
.
text-underline-position
’ propertyName: | text-underline-position |
---|---|
Value: | auto | under | alphabetic | over |
Initial: | auto |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property sets the position of an underline specified on the same element: it does not affect underlines specified by ancestor elements. The can appear either "over" or "under" the run of text in relation to its baseline orientation. This property is typically used in vertical writing contexts such as in Japanese documents where it often desired to have the underline appear "over" (to the right of) the affected run of text. Values have the following meanings:
alphabetic
. In vertical line layout, if the language is
set to Japanese or Korean, the underline should be aligned as for
over
. this suggestion needs some
refinement
East Asian documents traditionally use small symbols next to each glyph to emphasize a run of text. For example:
Accent emphasis (shown in blue for clarity) applied to Japanese text
text-emphasis-style
’ propertyName: | text-emphasis-style |
---|---|
Value: | none | [ [ filled | open ] || [ dot | circle | double-circle | triangle | sesame ] ] | <string> |
Initial: | none |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | ‘none ’, a pair of keywords
representing the shape and fill, or a string
|
This property applies emphasis marks to the element's text. Values have the following meanings:
none
filled
open
dot
•
’, and the open dot is U+25E6 ‘◦
’.
circle
●
’, and the open circle is U+25CB
‘○
’.
double-circle
◉
’, and the open double-circle
is U+25CE ‘◎
’.
triangle
▲
’, and the open triangle is U+25B3
‘△
’.
sesame
﹅
’, and the open sesame is U+FE46
‘﹆
’.
<string>
If a shape keyword is specified but neither of ‘filled
’ nor ‘open
’ is specified, ‘filled
’ is assumed. If only ‘filled
’ or 'open is specified, the shape
keyword computes to ‘dot
’ in
horizontal writing mode and ‘sesame
’ in vertical writing mode.
The marks should be drawn using the element's font settings with its size scaled down to 50%. UA should fall back to an appropriate font if the glyph is missing in the font. The marks may instead be synthesized by the UA.
This rendering scheme is based on ruby algorithm and the one used in Japanese printing industries. But the size of glyphs varies so much that this may result in inconsistent and/or bad visuals. If you have any feedback on this, it's appreciated.
The marks are drawn once for each grapheme cluster. However, emphasis marks are not drawn for a grapheme cluster consisting of:
text-emphasis-color
’ propertyName: | text-emphasis-color |
---|---|
Value: | <color> |
Initial: | currentcolor |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property describes the foreground color of the emphasis marks.
text-emphasis
’ propertyName: | text-emphasis |
---|---|
Value: | ‘<text-emphasis-style> ’
|| ‘<text-emphasis-color> ’
|
Initial: | see individual properties |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | see individual properties |
This property is a shorthand for setting text-emphasis-style
and text-emphasis-color
in one
declaration. Omitted values are set to their initial values.
Note that ‘text-emphasis-position
’ is not reset in
this shorthand. This is because typically the shape and color vary, but
the position is consistent for a particular language throughout the
document. Therefore the position should inherit independently.
text-emphasis-position
’ propertyName: | text-emphasis-position |
---|---|
Value: | over | under |
Initial: | over Is this the right default? |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property describes where emphasis marks are drawn at. The values have following meanings:
over
under
Emphasis marks are drawn exactly as if each grapheme cluster was
assigned the mark as its ruby annotation text with the ruby position given
by ‘text-emphasis-position
’ and the ruby
alignment as centered.
The effect of emphasis marks on the line height is the same as for ruby text.
The values ‘over
’
and ‘under
’ are chosen over
‘before
’ and ‘after
’ here because in Mongolian, baseline is
not alined with the block progression.
Steve Zilles points out that these values may not make much
sense if vertical text is laid out so that horizontal scripts' glyph tops
point left. An alternative set of values could be [ top | bottom ]
&& [ left | right ]
, with the appropriate value used for the
current writing mode. This also makes it simple for PRC Chinese text to
specify the correct behavior in the UA style sheet.
Note, the preferred position of emphasis marks depends on the language.
In Japanese for example, the preferred position is ‘over
’. In Chinese used in the PRC, on the
other hand, the preferred position is ‘under
’. The informative table below
summarizes the preferred emphasis mark position for Chinese and Japanese:
Language | Preferred mark position | Illustration | ||
---|---|---|---|---|
Horizontal | Vertical | |||
Japanese | over | over | | |
Mongolian | over? | over | ||
Chinese (Traditional) | over | over | ||
Chinese (Simplified) | under | over | |
text-shadow
’ propertyName: | text-shadow |
---|---|
Value: | none | [<shadow>, ] * <shadow> |
Initial: | none |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | a color plus three absolute <length>s |
This property accepts a comma-separated list of shadow effects to be
applied to the text of the element. <shadow> is the same as defined for the
‘box-shadow
’ property except that
the ‘inset
’ keyword is not allowed.
Should shadows be clipped to the glyph edges, like
‘box-shadow
’ is clipped to the box
edges, or should it be painted completely underneath the text. (This makes
a difference when the text is partially transparent.)
The shadow is applied to all of the element's text as well as any text decoration applied to it. Would it be better to apply shadows together with text decoration: i.e. a descendant of an underlined element doesn't apply shadow to its underline, but the underlining element, if it has shadows, would apply it to the underline of all text it underlines. When a text outline is specified, the shadow shadows the outlined shape rather than the glyph shape.
The shadow effects are applied front-to-back: the first shadow is on top. The shadows may thus overlay each other, but they never overlay the text itself. Shadow effects do not alter the size of a box, but may extend beyond its boundaries. The shadow must be painted immediately behind the element's text (in front of its background). UAs should avoid painting text shadows over text in adjacent elements belonging to the same stack level and stacking context.
The painting order of shadows defined here is the opposite of that defined in the 1998 CSS2 Recommendation.
The text-shadow
property
applies to both the ::first-line
and
::first-letter
pseudo-elements.
text-outline
’ propertyName: | text-outline |
---|---|
Value: | none | [ <color> <length> <length>? | <length> <length>? <color> ] |
Initial: | none |
Applies to: | all elements |
Inherited: | yes |
Percentages: | N/A |
Media: | visual |
Computed value: | a color plus two absolute <length>s |
This property specifies a text outline where the first length represents
the outline's thickness and the second represents an optional blur radius.
The outline never overlays the text itself. Its shape is the same as that
obtained by applying text shadows in every radial direction, i.e. all text
shadows whose offsets satisfy the equation x2 +
y2 = thickness2
. The blur radius is treated
the same as for ‘text-shadow
’.
The Timed-Text WG had suggestions for some keywords (text-outline: normal|heavy|light;) as well as a <length> thickness. Should these be added? How would they be defined? (Maybe use (thin|medium|thick) as in border-width?)
A color value must be specified before or after the length values of the outline effect. The color value will be used as the color of the outline.
Implementations may ignore the blur radius when text outline is combined with a text shadow.
text-overflow
’ propertyName: | text-overflow |
---|---|
Value: | clip | ellipsis | <string> |
Initial: | clip |
Applies to: | block containers |
Inherited: | no |
Percentages: | N/A |
Media: | visual |
Computed value: | as specified |
This property specifies the behavior when text overflows containing element. Values have the following meanings:
clip
ellipsis
<string>
Much of the text has been rewritten or severely revised, so all changes will not be listed here. Highlights include:
line-break
’ and ‘word-break-*
’ properties have been reorganized
and redesigned as ‘line-break
’ and ‘word-break
’ property.
wrap-option
’ property has been replaced
by the ‘text-wrap
’ and ‘word-break
’ property.
auto
’ value to
‘line-break
’, which allows the UA to vary
breaking strictness based on the effective line length.
linefeed-treatment
’, ‘white-space-treatment
’, and ‘all-space-treatment
’ properties have been
replaced by the ‘white-space-collapsing
’ property.
min-font-size
’ and ‘max-font-size
’ properties have been
delegated to the next revision of the CSS3 Fonts module.
text-align
’ property's vertical text
behavior for the ‘left
’ and
‘right
’ values to be relative to
LTR text rather than relative to the beginning of the line stack.
match-parent
’ keyword
to ‘text-align
’ to address some bidi use
cases such as aligning lists.
text-align
’ to
handle degenerate cases.
size
’ value has been
removed from the ‘text-align-last
’ property.
newspaper
’ value for ‘text-justify
’ has been dropped in favor
of using minimum and maximum limits set on the ‘word-spacing
’ and ‘letter-spacing
’ properties to guide
justification.
trim
’ keyword to ‘text-justify
’
as a replacement to ‘text-justify-trim
’.
tibetan
’ keyword to
‘text-justify
’.
word-spacing
’ and ‘letter-spacing
’ now take percentage
values.
text-wrap
’ property's ‘suppress
’ value allows authors to suppress
text wrapping within an element with respect to its surrounding text
without forbidding correctly-restricted breaks when they are
needed.
linefeed-treatment
’ property has been
removed because style sheets should not be expected to adapt to the
source code formatting style.
text-justify-trim
’ has been dropped in
favor of the ‘trim
’ keyword for the
‘text-justify
’ property.
end
’ and ‘allow-end
’ value to ‘punctuation-trim
’.
kerning-mode: contextual
’ has been replaced
with ‘punctuation-trim:
adjacent
’. Any further controls for kerning will likely
be delegated to the Fonts module.
punctuation
’ keyword to
‘text-autospace
’ property.
text-shadow
’ property now inherits, which
makes more sense and is consistent with recent implementation. The
default color is now UA-specified, which is more reasonable than
defaulting to the current text color. The definition now also mentions
that it applies to text decoration and makes a few minor clarifications.
text-outline
’ property has been added in
response to feedback
from the Timed-Text WG and Ada Chan. Its design derives from a discussion
of requirements within the CSS Working Group.
text-emphasis-*
’ properties have been added to
replace the ‘font-emphasis
’ property from the CSS3
Fonts module.
text-indent
’ has been replaced with the
precise text sent
in by Ian Hickson and fantasai on 8 March 2003 (minus
the ‘text-align
’ dependence rules).
each-line
’ keyword to ‘text-indent
’.
hanging-punctuation
’ property has been
redesigned with several combinable values instead of ‘start
’, ‘end
’,
and ‘both
’ to eliminate the script and
language dependencies.
text-overflow
’ properties have been
compressed into one property and given a much more precise specified
behavior.
fullwidth
’ and ‘large-kana
’ to ‘text-transform
’ property.
Sections relating to bidirectional and vertical text layout will be moved to a separate Writing Modes module. These features may change greatly from the last revision, but they have not been dropped. The vertical text feature, for example, will likely be based on the methods described in Unicode Technical Note #22.
The text-script property has been dropped, since it does not belong in the style layer.
Controls over kerning have been moved to the CSS Fonts Module.
The line grid properties have been removed. There is currently no plan to add them back, although a document grid feature may be added to future CSS modules.
Major changes include:
word-break
’ into ‘line-break
’ and
‘word-break
’ controls, affecting CJK and
non-CJK scripts respectively. This is very close to IE's implementation
(hence the somewhat confusing names), with the exception that
‘keep-all
’ functionality, which
affects CJK scripts, was moved from ‘word-break
’ to ‘line-break
’.
auto
’ value to
‘line-break
’, which allows the UA to vary
breaking strictness based on the effective line length.
match-parent
’ keyword
to ‘text-align
’ to address some bidi use
cases such as aligning lists.
text-align
’ to
handle degenerate cases.
trim
’ keyword to ‘text-justify
’
as a replacement to ‘text-justify-trim
’.
tibetan
’ keyword to
‘text-justify
’.
text-justify
’ section.
allow-end
’ value to
‘punctuation-trim
’.
text-autospace
’ property, and added new
‘punctuation
’ keyword.
each-line
’ keyword to ‘text-indent
’.
text-shadow
’ definition to ‘box-shadow
’ definition.
hanging-punctuation
’ to be clearer; added
‘allow-end
’/‘force-end
’ distinction.
text-decoration
’ section.
text-emphasis
’ controls.
text-overflow
’.
text-transform
’ with new values for
‘fullwidth
’ and ‘large-kana
’.
This specification would not have been possible without the help from: Ayman Aldahleh, Bert Bos, Tantek Çelik, Stephen Deach, Martin Dürst, Laurie Anna Edlund, Ben Errez, Yaniv Feinberg, Arye Gittelman, Ian Hickson, Martin Heijdra, Richard Ishida, Koji Ishii, Masayasu Ishikawa, Michael Jochimsen, Eric LeVine, Ambrose Li, Chris Lilley, Shinyu Murakami, Paul Nelson, Chris Pratley, Marcin Sawicki, Arnold Schrijver, Rahul Sonnad, Michel Suignard, Takao Suzuki, Frank Tang, Chris Thrasher, Etan Wexler, Chris Wilson, Masafumi Yabe and Steve Zilles.
Property | Values | Initial | Applies to | Inh. | Percentages | Media |
---|---|---|---|---|---|---|
hanging-punctuation | none | [ first || last || [ allow-end | force-end ] ] | none | block containers | yes | N/A | visual |
letter-spacing | <spacing-limit>{1,3} | normal | all elements | yes | refers to width of space (U+0020) glyph | visual |
line-break | auto | newspaper | normal | strict | keep-all | auto | all elements | yes | N/A | visual |
punctuation-trim | none | [start || [ end | allow-end ] || adjacent] | none | all elements | yes | N/A | visual |
text-align | [start | end | left | right | center | justify | match-parent ] || <string> | start | block containers | yes | N/A | visual |
text-align-last | start | end | left | right | center | justify | start | block containers | yes | N/A | visual |
text-autospace | none | [ ideograph-numeric || ideograph-alpha || ideograph-space || ideograph-parenthesis ] | none | all elements | yes | N/A | visual |
text-decoration | <text-decoration-line> || <text-decoration-color> || <text-decoration-style> || blink | none | all elements | no | N/A | visual |
text-decoration-color | <color> | currentColor | all elements | no | N/A | visual |
text-decoration-line | none | [ underline || overline || line-through ] | none | all elements | no (but see prose) | N/A | visual |
text-decoration-skip | none | [ images || spaces || ink || all ] | images | all elements | yes | N/A | visual |
text-decoration-style | solid | double | dotted | dashed | wave | solid | all elements | no | N/A | visual |
text-emphasis | ‘<text-emphasis-style>’ || ‘<text-emphasis-color>’ | see individual properties | all elements | yes | N/A | visual |
text-emphasis-color | <color> | currentcolor | all elements | yes | N/A | visual |
text-emphasis-position | over | under | over Is this the right default? | all elements | yes | N/A | visual |
text-emphasis-style | none | [ [ filled | open ] || [ dot | circle | double-circle | triangle | sesame ] ] | <string> | none | all elements | yes | N/A | visual |
text-indent | [ <length> | <percentage> ] && [ hanging || each-line ]? | 0 | block containers | yes | refers to width of containing block | visual |
text-justify | auto | [ trim || [ inter-word | inter-ideograph | inter-cluster | distribute | kashida ] ] | auto | block containers and, optionally, inline elements | yes | N/A | visual |
text-outline | none | [ <color> <length> <length>? | <length> <length>? <color> ] | none | all elements | yes | N/A | visual |
text-overflow | clip | ellipsis | <string> | clip | block containers | no | N/A | visual |
text-shadow | none | [<shadow>, ] * <shadow> | none | all elements | yes | N/A | visual |
text-transform | none | capitalize | uppercase | lowercase | fullwidth | large-kana | none | all elements | yes | N/A | visual |
text-underline-position | auto | under | alphabetic | over | auto | all elements | yes | N/A | visual |
text-wrap | normal | unrestricted | none | suppress | normal | all elements | yes | N/A | visual |
white-space | normal | pre | nowrap | pre-wrap | pre-line | not defined for shorthand properties | all elements | yes | N/A | visual |
white-space-collapsing | collapse | discard | [ [preserve | preserve-breaks] && trim-inner ] | collapse | all elements | yes | N/A | visual |
word-break | normal | break-all | hyphenate | normal | all elements | yes | N/A | visual |
word-spacing | <spacing-limit> {1,3} | normal | all elements | yes | refers to width of space (U+0020) glyph | visual |
word-wrap | normal | break-word | normal | all elements | yes | N/A | visual |
This section is informative, and is to help UA developers to implement default stylesheet, but UA developers are free to ignore or change.
/* make list items align together */
li { text-align: match-parent; }
/* disable inheritance of text-emphasis marks to ruby text:
emphasis marks should only apply to base text */
rt { text-emphasis: none; }
:root:lang(zh-Hans) {
/* default emphasis mark position is 'under' for Chinese (Simplified) */
text-emphasis-position: under;
}
If you find any issues, recommendations to add, or corrections, please send the information to www-style@w3.org with [css3-text] in the subject line.