CSS3

  • 201007 Oct

    W3C Releases Updated Working Draft of CSS3 Text

    by

    Posted in News, W3C

    The W3C have this week released an updated working draft of the CSS3 Text module. Major changes from the previous working draft, released in March 2007, include:

    * White space collapsing rules have been sync’ed with updates to CSS2.1, and the introductory prose rewritten.
    * Resplit ‘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’.
    * Added ‘auto’ value to ‘line-break’, which allows the UA to vary breaking strictness based on the effective line length.
    * Added ‘match-parent’ keyword to ‘text-align’ to address some bidi use cases such as aligning lists.
    * Allow keyword and to be specified jointly for ‘text-align’ to handle degenerate cases.
    * Added ‘trim’ keyword to ‘text-justify’ as a replacement to ‘text-justify-trim’.
    * Removed ‘tibetan’ keyword to ‘text-justify’.
    * Revised ‘text-justify’ section.
    * Added ‘allow-end’ value to ‘punctuation-trim’.
    * Re-added ‘text-autospace’ property, and added new ‘punctuation’ keyword.
    * Added ‘each-line’ keyword to ‘text-indent’.
    * Linked ‘text-shadow’ definition to ‘box-shadow’ definition.
    * Renamed values for ‘hanging-punctuation’ to be clearer; added ‘allow-end’/‘force-end’ distinction.
    * Wrote out ‘text-decoration’ section.
    * Expanded ‘text-emphasis’ controls.
    * Drafted syntax for ‘text-overflow’.
    * Added back ‘text-transform’ with new values for ‘fullwidth’ and ‘large-kana’.

    You can view the full specification here, and as always comments are invited via the www-style mailing list.

    You can skip to the end and leave a response.


  • Comments

    • 01.
      Codekiller says:Comment » October 7th, 2010 at 6:26 pm

      Great update! I’m liking the “start” and “end” values for text-align. :D

    • 02.
      Tony R. says:Comment » October 12th, 2010 at 6:04 pm

       This is great news! :D

      …

      On a side note, I have 2 nitpicks:

      1. The “Add Comments” link at the top of this article didn’t work for me. Running the latest Safari on OS X 10.6 (Snow Leopard).

      2. The post itself is just text. While that might be ironic considering it’s about the CSS text module, I kind of wish it would use markup for an unordered list instead of just asterisks. And I kind of wish that the CSS properties were marked up 

       elements.   
 
…This is a site about Web Standards, after all!  Be the change you want to see, eh?  :D

    • 03.
      Tony R. says:Comment » October 12th, 2010 at 8:54 pm

         YIKES. With no ability to preview my comment it looks like the parser choked on some markup that I thought would be escaped. Ouch!

      Sorry for previous comment SNAFU. Reposting, hopefully readable this time.

      ***

      This is great news! :D

      …

      On a side note, I have 2 nitpicks:

      1. The “Add Comments” link at the top of this article didn’t work for me. Running the latest Safari on OS X 10.6 (Snow Leopard).

      2. The post itself is just text. While that might be ironic considering it’s about the CSS text module, I kind of wish it would use markup for an unordered list instead of just asterisks. And I kind of wish that the CSS properties were marked up with <code> elements, rather than just putting quotes around them.

      …This is a site about Web Standards, after all! Be the change you want to see, eh? :D

    • 04.
      Gaurav M says:Comment » October 13th, 2010 at 8:29 am

       Staying tuned!

    • 05.
      Alison Foxall says:Comment » October 25th, 2010 at 4:41 am

      “* Added back ‘text-transform’ with new values for ‘fullwidth’ and ‘large-kana’.”

      You mean to tell me they originally got rid of text-transform? I must have been living under a rock. 

    • 06.
      ari says:Comment » October 27th, 2010 at 10:17 am

      Is the W3C planning to extend CSS3 support for form elements like select,radio,checkbox,file and scrollbars?

    • 07.
      fantasai says:Comment » November 1st, 2010 at 1:21 pm

      @Alison Foxall Well, what happened was that between the 2003 CR and now, the entire spec has been rewritten. And I rewrote the spec in increments, first by throwing out the entire thing, and then slowly adding sections back in. So that’s what that comment refers to.

Subscribe to our RSS
CATEGORIES
FRIENDS
Meta
TAG CLOUD acid3 advanced layout advanced layout module Animations background border Browsers color css CSS3.info CSS WG csswg developer tools disabled enabled Feedback firefox firefox 3.1 flexible box layout fonts generated content grid positioning HSLA HTML5 ie6 jina bolton jquery media player Multicolumn Layout News Opera Opera Dragonfly presentations RGBA safari Selectors slides SVG text rendering W3C wasp Web Fonts webkit windows

Hosting by:

© 2009-2012 WEBFLUX. All Rights Reserved.