What is holding CSS2.1 away from reaching a REC status?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Jan Roland Eriksson

    What is holding CSS2.1 away from reaching a REC status?

    The following URL...

    <http://www.w3.org/TR/CSS21/>

    ....has had the following text in it for a considerable time now.

    "This is a W3C Candidate Recommendation, which means
    the specification has been widely reviewed and W3C
    recommends that it be implemented. It will remain Candidate
    Recommendation at least until 1 September 2004."

    And this following URL contains info that looks like a disaster...

    <http://www.w3.org/Style/CSS/#specs>

    "CSS level 2 revision 1 (“CSS 2.1”) contains all of CSS
    level 1 and adds absolutely positioned elements, automatic
    numbering, page breaks, right to left text and other things.
    At this moment, February 2004, it is a Candidate W3C Recommendation. "

    Are there still any *really serious* outstanding issues to address in
    CSS2.1, or has the W3 "chair" gone away on a _long_time_ vacation that
    would prohibit a REC status to be issued?

    --
    Rex


  • Steve Pugh

    #2
    Re: What is holding CSS2.1 away from reaching a REC status?

    Jan Roland Eriksson wrote:[color=blue]
    >
    > <http://www.w3.org/TR/CSS21/>
    >
    > ...has had the following text in it for a considerable time now.
    >
    > "This is a W3C Candidate Recommendation, which means
    > the specification has been widely reviewed and W3C
    > recommends that it be implemented. It will remain Candidate
    > Recommendation at least until 1 September 2004."[/color]

    And just after that it says:
    "A test suite and a report on implementations will be provided before
    the document becomes a Proposed Recommendation. "

    And when we go to the test suite page
    <url:http://www.w3.org/Style/CSS/Test/> we discover that the test suite
    is still in 'beta'.
    [color=blue]
    > Are there still any *really serious* outstanding issues to address in
    > CSS2.1, or has the W3 "chair" gone away on a _long_time_ vacation[/color]
    that[color=blue]
    > would prohibit a REC status to be issued?[/color]

    It hasn't met the condition regarding a test suite.

    Steve

    Comment

    • Jan Roland Eriksson

      #3
      Re: What is holding CSS2.1 away from reaching a REC status?

      On 3 May 2005 01:37:12 -0700, "Steve Pugh" <steve@pugh.net > wrote:
      [color=blue]
      >Jan Roland Eriksson wrote:[color=green]
      >> <http://www.w3.org/TR/CSS21/>
      >> ...has had the following text in it for a considerable time now.
      >>
      >> "This is a W3C Candidate Recommendation, which means
      >> the specification has been widely reviewed and W3C
      >> recommends that it be implemented. It will remain Candidate
      >> Recommendation at least until 1 September 2004."[/color][/color]
      [color=blue]
      >And just after that it says:
      > "A test suite and a report on implementations will be provided
      > before the document becomes a Proposed Recommendation. "[/color]

      Yea, I know about that part too.
      [color=blue]
      >And when we go to the test suite page[/color]
      [color=blue]
      ><url:http://www.w3.org/Style/CSS/Test/>[/color]
      [color=blue]
      >we discover that the test suite is still in 'beta'.[/color]

      Hmm, makes me wonder since all test cases are last updated on
      "25-Nov-2004 18:33" (and don't ridicule me on this, I do know how it is
      produced)

      But basically; this looks ridiculous to any "layman" who happens to come
      bye for a look at status.
      [color=blue][color=green]
      >> Are there still any *really serious* outstanding issues to
      >> address in CSS2.1 ... that would prohibit a REC status to
      >> be issued?[/color][/color]
      [color=blue]
      >It hasn't met the condition regarding a test suite.[/color]

      And who has been appointed to be the judge of that criteria?

      Personally I fear that the "delay" has been inflicted by some "potent"
      (non)member of W3 as in "hang in there guys, we need more time to make
      Longhorn (and/or IE7) ready for this".

      As far as I can see, there are no more _big_ issues with CSS2.1

      The occasional loudmouth wanting e.g. 67.5989 degree corners on some
      specific menu style can never be shoved off any way.

      It is time now, to move CSS2.1 to the chair for approval.

      --
      Rex


      Comment

      Working...