W3C home > Mailing lists > Public > www-style@w3.org > September 2008

[css3-gcpm] new editor's draft; page lists, page floats, text-replace

From: Håkon Wium Lie <howcome@opera.com>
Date: Wed, 3 Sep 2008 16:49:07 +0200
Message-ID: <18622.41955.971743.992027@opera.com>
To: www-style@w3.org

Based on discussions on this list [1] and at the recent CSS WF
face-to-face meeting [2], I've published a new Editor's Draft of CSS3
GCPM:

  http://dev.w3.org/csswg/css3-gcpm/

There are changes in three main areas:

  - page lists: I think we've found a syntax that fulfills all four
    use cases [3], while having minimal impact on the syntax as
    described in CSS2. The two changes are:

      - the 'page' property is changed from inherited to non-inherited

      - setting a single named page on the 'page' property will lead
        to page breaks before and after the element.


  - page floats: the 'float' property is extended so that it accepts
    more keywords and a comma-separated list of values. E.g., this
    code:

        float: none, top next page;

    will result in the element floating to the next page, but only if
    it doesn't fit on the current page.

  - text-replace: there was a debate at the F2f whether (a) this
    funcionality should be offered as part of CSS, or (b) if it can be
    expressed in a different way. Here is one possible solution:

       *:text("Soviet Union") { content: "Russia" }

    which, potentiall, could be even mover powerful:

       *:text("Soviet Union") { content: "Russia"; color: red }

[1] http://lists.w3.org/Archives/Public/www-style/2008Aug/0136.html
[2] http://krijnhoetmer.nl/irc-logs/css/20080821
[3] http://lists.w3.org/Archives/Public/www-style/2008Aug/0157.html

Cheers,

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Wednesday, 3 September 2008 14:49:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:12 GMT