diff --git a/css-text-decor-4/Overview.bs b/css-text-decor-4/Overview.bs index 23227081dc7..c78a3109f59 100644 --- a/css-text-decor-4/Overview.bs +++ b/css-text-decor-4/Overview.bs @@ -28,6 +28,57 @@ It has no status at W3C and has not yet been discussed by the CSSWG.
  • a text-line-width property +

    Extentions to L3 features

    + +

    +Text Decoration Line Continuity: the 'text-decoration-skip' property

    + +This specification extends the 'text-decoration-skip' property +present in level 3 +by adding the ''trailing-spaces'' value. + +
    +      Name: text-decoration-skip
    +      Value: ''none'' | [ ''objects'' || [ ''spaces'' | ''trailing-spaces'' ] || ''ink'' || ''edges'' || ''box-decoration'' ]
    +      Initial: objects
    +      Applies to: all elements
    +      Inherited: yes
    +      Percentages: N/A
    +      Media: visual
    +      Computed value: as specified
    +      Animatable: no
    +  
    + + Issue: Add final level 3 content + +
    +
    none
    +
    objects
    +
    spaces
    +
    ink
    +
    edges
    +
    box-decoration +
    + + Issue: Add final level 3 content +
    trailing-spaces
    +
    Skip all spacing, i.e. all characters with the Unicode White_Space property [[UAX44]] + and all word separators, + plus any adjacent 'letter-spacing' or 'word-spacing' + when located then end of the line. +
    + + Issue: Should ''object trailing-spaces'' be the initial value instead of just ''object''? + Should the initial value be auto, + defined so that that it can vary between + ''object'' and ''object trailing-spaces'' + depending on properties like 'white-space', 'word-wrap', 'word-break' etc? + + Issue: Should we have a ''leading-spaces'' value as well? + It looks like ''object leading-spaces'' may be more appropriate than + ''object trailing-spaces'' in right-aligned text, + even though common word processing applications don't do that. +

    Rescued L3 Brainstorming: Ignore For Now

    diff --git a/css-text-decor-4/Overview.html b/css-text-decor-4/Overview.html index 192fdb4feda..46e7cad7812 100644 --- a/css-text-decor-4/Overview.html +++ b/css-text-decor-4/Overview.html @@ -1,312 +1,401 @@ - + - - + - CSS Text Decoration Module Level 4 - - - + CSS Text Decoration Module Level 4 - - - - - - + + + + + + + - + + + -
    + + +
    -

    -

    CSS Text Decoration Module Level 4

    +

    CSS Text Decoration Module Level 4

    -

    Unofficial Proposal Draft, -

    +

    Unofficial Proposal Draft, +

    -
    -
    -
    This version:
    -
    http://dev.w3.org/csswg/css-text-decor-4/
    -
    Latest version:
    -
    http://www.w3.org/TR/css-text-decor-4/
    -
    Feedback:
    -
    www-style@w3.org with subject line “[css-text-decor] … message topic …” (archives)
    -
    Issue Tracking:
    -
    Inline In Spec
    -
    http://www.w3.org/Style/CSS/Tracker/products/10
    -
    Editors:
    -
    -
    fantasai (Invited Expert)
    -
    -
    -
    (Invited Expert)
    -
    -
    -
    +
    +
    +
    This version: +
    http://dev.w3.org/csswg/css-text-decor-4/ +
    Latest version: +
    http://www.w3.org/TR/css-text-decor-4/ +
    Feedback: +
    www-style@w3.org with subject line “[css-text-decor] … message topic …” (archives) +
    Issue Tracking: +
    Inline In Spec +
    http://www.w3.org/Style/CSS/Tracker/products/10 +
    Editors: +
    fantasai (Invited Expert) +
    (Invited Expert) +
    +
    -
    +
    - -
    +
    -

    Abstract

    +

    Abstract

    -
    -

    This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks.

    +
    +

    This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks.

    CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc.
    -

    Status of this document

    +

    Status of this document

    -
    +
    -
    +
    -

    Table of Contents

    +

    Table of Contents

    -
    -
    + +
    + + + + + +

    This is just a place to keep ideas at the moment. It has no status at W3C and has not yet been discussed by the CSSWG.

    -

    1. Things To Include Here

    +

    1. Things To Include Here

    -

    In addition to all of the features in Level 3, a completed initial draft of this module will include:

    +

    In addition to all of the features in Level 3, a completed initial draft of this module will include:

    -
      +
        -
      • text-shadow with spread -
      • -
      • fill/stroke on text -
      • -
      • a text-decoration-offset property -
      • -
      • a text-line-width property -
      • -
      +
    • text-shadow with spread + +
    • fill/stroke on text + +
    • a text-decoration-offset property + +
    • a text-line-width property + +
    + + +

    2. Extentions to L3 features

    + + +

    2.1. +Text Decoration Line Continuity: the text-decoration-skip property

    + + +

    This specification extends the text-decoration-skip property +present in level 3 +by adding the trailing-spaces value.

    + + + + + + + + + + + + + +
    Name: + text-decoration-skip +
    Value: + none | [ objects || [ spaces | trailing-spaces ] || ink || edges || box-decoration ] +
    Initial: + objects +
    Applies to: + all elements +
    Inherited: + yes +
    Percentages: + N/A +
    Media: + visual +
    Computed value: + as specified +
    Animatable: + no
    + + +

    Add final level 3 content

    + + +
    + +
    none + + +
    objects + + +
    spaces + + +
    ink + + +
    edges + + +
    box-decoration + +
    + + +

    Add final level 3 content

    + + +
    trailing-spaces + + +
    Skip all spacing, i.e. all characters with the Unicode White_Space property [UAX44] + and all word separators, + plus any adjacent letter-spacing or word-spacing + when located then end of the line. + +
    -

    2. Rescued L3 Brainstorming: Ignore For Now

    +

    Should object trailing-spaces be the initial value instead of just object? + Should the initial value be auto, + defined so that that it can vary between + object and object trailing-spaces + depending on properties like white-space, word-wrap, word-break etc?

    -

    2.1. +

    Should we have a leading-spaces value as well? + It looks like object leading-spaces may be more appropriate than + object trailing-spaces in right-aligned text, + even though common word processing applications don’t do that.

    + + +

    3. Rescued L3 Brainstorming: Ignore For Now

    + + +

    3.1. Emphasis Mark Skip: the text-emphasis-skip property

    -

    This section is under brainstorming. +

    This section is under brainstorming. It’s also not yet clear if this property is needed quite yet, despite differences in desired behavior among publications.

    - +
    - + - + - - + - + - + - + - - + - + + - - + - + - - + - - + + + + - - + - + - + - + - - + - + - + - + - - + - + - + - + - - + - + - + - + - - + - + - + - - + -
    Name:Name: + - text-emphasis-skiptext-emphasis-skip + -
    Value:Value: + - spaces || + spaces || punctuation || symbols || narrow -
    Initial:Initial: + - spaces -
    spaces -
    Applies to:Applies to: + - all elementsall elements + -
    Inherited:Inherited: + - yesyes + -
    Percentages:Percentages: + - N/AN/A + -
    Media:Media: + - visualvisual + -
    Computed value:Computed value: + - as specifiedas specified + -
    + -

    This property describes for which characters marks are drawn. +

    This property describes for which characters marks are drawn. The values have following meanings:

    -
    +
    + +
    spaces -
    spaces -
    -
    +
    Skip Word separators or characters belonging to the Unicode separator category (Z*). (But note that emphasis marks are drawn for a space that combines with any combining characters.) -
    -
    punctuation -
    -
    + +
    punctuation + +
    Skip punctuation. Punctuation in this definition includes characters belonging to the Unicode Pc, Pd, Ps, Pe, Pi, or Pf categories. It also includes characters where the Unicode category is Po and - the Sentence_Break property [UAX29] of the Unicode database - [UAX44] is ATerm, Close, SContinue, or STerm. + the Sentence_Break property [UAX29] of the Unicode database + [UAX44] is ATerm, Close, SContinue, or STerm. -
    -
    symbols -
    -
    Skip symbols. + +
    symbols + +
    Skip symbols. Symbols in this definition includes characters belonging to the Unicode S* category. It also includes the Unicode Po category that are not defined as punctuation above. -
    -
    narrow -
    -
    Skip characters where the East_Asian_Width property [UAX11] - of the Unicode database [UAX44] is not F (Fullwidth) or W (Wide). -
    -
    + +
    narrow + +
    Skip characters where the East_Asian_Width property [UAX11] + of the Unicode database [UAX44] is not F (Fullwidth) or W (Wide). + +
    -

    Characters belonging to the Unicode classes for control codes +

    Characters belonging to the Unicode classes for control codes and unassigned characters (Cc, Cf, Cn) are skipped regardless of the value of this property.

    -

    This syntax requires UA to implement drawing marks for spaces. +

    This syntax requires UA to implement drawing marks for spaces. Is there any use case for doing so? If not, should we modify the syntax not to allow drawing marks for spaces? @@ -314,15 +403,15 @@

    -

    +

    Conformance

    -

    +

    Document conventions

    -

    Conformance requirements are expressed with a combination of +

    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 @@ -331,31 +420,31 @@

    letters in this specification.

    -

    All of the text of this specification is normative except sections - explicitly marked as non-normative, examples, and notes. [RFC2119]

    +

    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" +

    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.

    - +

    This is an example of an informative example.

    + -
    +
    -

    Informative notes begin with the word "Note" and are set apart from the +

    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.

    +

    Note, this is an informative note.

    -

    Advisements are normative sections styled to evoke special attention and are +

    Advisements are normative sections styled to evoke special attention and are set apart from other normative text with <strong class="advisement">, like this: @@ -364,41 +453,41 @@

    -

    +

    Conformance classes

    -

    Conformance to this specification +

    Conformance to this specification is defined for three conformance classes:

    -
    +
    -
    style sheet -
    -
    A CSS +
    style sheet + +
    A CSS style sheet. -
    -
    renderer -
    -
    A UA + +
    renderer + +
    A UA that interprets the semantics of a style sheet and renders documents that use them. -
    -
    authoring tool -
    -
    A UA + +
    authoring tool + +
    A UA that writes a style sheet. -
    -
    + +
    -

    A style sheet is conformant to this specification +

    A style sheet is conformant to this specification if all of its statements that use syntax defined in this module are valid according to the generic CSS grammar and the individual grammars of each feature defined in this module.

    -

    A renderer is conformant to this specification +

    A renderer is conformant to this specification if, in addition to interpreting the style sheet as defined by the appropriate specifications, it supports all the features defined by this specification by parsing them correctly @@ -408,18 +497,18 @@

    +

    Partial implementations

    -

    So that authors can exploit the forward-compatible parsing rules to +

    So that authors can exploit the forward-compatible parsing rules to assign fallback values, CSS renderers must treat as invalid (and ignore as appropriate) any at-rules, properties, property values, keywords, @@ -431,16 +520,16 @@

    be ignored.

    -

    +

    Experimental implementations

    -

    To avoid clashes with future CSS features, the CSS2.1 specification +

    To avoid clashes with future CSS features, the CSS2.1 specification reserves a prefixed syntax for proprietary and experimental extensions to CSS.

    -

    Prior to a specification reaching the Candidate Recommendation stage +

    Prior to a specification reaching the Candidate Recommendation stage in the W3C process, all implementations of a CSS feature are considered experimental. The CSS Working Group recommends that implementations use a vendor-prefixed syntax for such features, including those in @@ -449,17 +538,17 @@

    -

    +

    Non-experimental implementations

    -

    Once a specification reaches the Candidate Recommendation stage, +

    Once a specification reaches the Candidate Recommendation stage, non-experimental implementations are possible, and implementors should release an unprefixed implementation of any CR-level feature they can demonstrate to be correctly implemented according to spec.

    -

    To establish and maintain the interoperability of CSS across +

    To establish and maintain the interoperability of CSS across implementations, the CSS Working Group requests that non-experimental CSS renderers submit an implementation report (and, if necessary, the testcases used for that implementation report) to the W3C before @@ -468,7 +557,7 @@

    Working Group.

    -

    Further information on submitting testcases and implementation reports +

    Further information on submitting testcases and implementation reports can be found from on the CSS Working Group’s website at http://www.w3.org/Style/CSS/Test/. Questions should be directed to the @@ -478,68 +567,122 @@

    -

    References

    -

    Normative References

    -
    -
    [UAX11]
    -
    Asmus Freytag. East Asian Width. 23 March 2001. Unicode Standard Annex #11. URL: http://www.unicode.org/unicode/reports/tr11/tr11-8.html
    -
    [UAX29]
    -
    Mark Davis. Text Boundaries. 25 March 2005. Unicode Standard Annex #29. URL: http://www.unicode.org/unicode/reports/tr29/tr29-9.html
    -
    [UAX44]
    -
    Mark Davis; Ken Whistler. Unicode Character Database. 25 September 2013. URL: http://www.unicode.org/reports/tr44/
    -
    [rfc2119]
    -
    S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119
    -
    -

    Index

    -
      -
    • narrow, 2.1
    • -
    • punctuation, 2.1
    • -
    • spaces, 2.1
    • -
    • symbols, 2.1
    • -
    • text-emphasis-skip, 2.1
    • +

      Index

      +

      Terms defined by this specification

      +
        +
      • box-decoration, 2.1 +
      • edges, 2.1 +
      • ink, 2.1 +
      • narrow, 3.1 +
      • none, 2.1 +
      • objects, 2.1 +
      • punctuation, 3.1 +
      • spaces +
          +
        • value for text-decoration-skip, 2.1 +
        • definition of, 3.1
        -

        Property Index

        - - - - - - - - - - - - - - - - -
        NameValueInitialApplies toInh.%agesMediaComputed value
        text-emphasis-skipspaces || +
      • symbols, 3.1 +
      • text-decoration-skip, 2.1 +
      • text-emphasis-skip, 3.1 +
      • trailing-spaces, 2.1 + +

        Terms defined by reference

        + +

        References

        +

        Normative References

        +
        +
        [UAX11] +
        Asmus Freytag. East Asian Width. 23 March 2001. Unicode Standard Annex #11. URL: http://www.unicode.org/unicode/reports/tr11/tr11-8.html +
        [UAX29] +
        Mark Davis. Text Boundaries. 25 March 2005. Unicode Standard Annex #29. URL: http://www.unicode.org/unicode/reports/tr29/tr29-9.html +
        [UAX44] +
        Mark Davis; Ken Whistler. Unicode Character Database. 25 September 2013. URL: http://www.unicode.org/reports/tr44/ +
        [CSS-TEXT-3] +
        Elika Etemad; Koji Ishii. CSS Text Module Level 3. 10 October 2013. LCWD. URL: http://www.w3.org/TR/css-text-3/ +
        [CSS-VALUES-3] +
        CSS Values and Units Module Level 3 URL: http://www.w3.org/TR/css3-values/ +
        [RFC2119] +
        S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119 +
        +

        Property Index

        + + + + + + + - - - - - - - - -
        Name + Value + Initial + Applies to + Inh. + %ages + Media + Animatable + Computed value + Computed value +
        text-decoration-skip + none | [ objects || [ spaces | trailing-spaces ] || ink || edges || box-decoration ] + objects + all elements + yes + N/A + visual + no + as specified + +
        text-emphasis-skip + spaces || punctuation || symbols || - narrowspacesall elementsyesN/Avisualas specified
        -

        Issues Index

        -
        -
        This is just a place to keep ideas at the moment. + narrow +
      • spaces + all elements + yes + N/A + visual + + + as specified +
        +

        Issues Index

        +
        +
        This is just a place to keep ideas at the moment. It has no status at W3C and has not yet been discussed by the CSSWG.
        -
        This section is under brainstorming. +
        Add final level 3 content
        +
        Add final level 3 content
        +
        Should object trailing-spaces be the initial value instead of just object? + Should the initial value be auto, + defined so that that it can vary between + object and object trailing-spaces + depending on properties like white-space, word-wrap, word-break etc?
        +
        Should we have a leading-spaces value as well? + It looks like object leading-spaces may be more appropriate than + object trailing-spaces in right-aligned text, + even though common word processing applications don’t do that.
        +
        This section is under brainstorming. It’s also not yet clear if this property is needed quite yet, despite differences in desired behavior among publications.
        -
        This syntax requires UA to implement drawing marks for spaces. +
        This syntax requires UA to implement drawing marks for spaces. Is there any use case for doing so? If not, should we modify the syntax not to allow drawing marks for spaces?
        -
        - +
        + \ No newline at end of file