tech support 8

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Thursday, 15 July 2010

CSS 2.1 Still Not Final

Posted on 09:51 by Unknown

W3CWe all know that CSS3 is not final, nor is HTML5. What you may not know is that the CSS 2.1 specification is also not final.



CSS2 became a W3C recommendation on May 12, 1998, over 12 years ago. Since then the CSS Working Group has been developing CSS Level 2 Revision 1 (CSS 2.1) to correct errors and omissions from the original CSS2 specification. In fact, the CSS2 specification directs people to the CSS 2.1 specification as the de facto current version. CSS 2.1 is a Candidate Recommendation, and has September 8, 2009 referenced as the date of the specification.



The W3C has a slightly confusing progression of a specification before it is considered a "standard." There are essentially four steps:




  1. Working Draft (WD): This is the first time a proposed specification is shown to the public and open for comment.

  2. Candidate Recommendation (CR): Significant features are mostly locked and feedback is requested in how to implement the standard.

  3. Proposed Recommendation (PR): The specification has been submitted to the W3C Advisory Council for approval. Changes at this point are rare.

  4. W3C Recommendation (REC): The specification is final and endorsed by the W3C. This is what the general public considers a final standard.



To clarify, the CSS 2.1 specification is in the second of four stages. For context, the HTML 4 specification was approved on April 24, 1998. The HTML 4.01 specification was approved on December 24, 1999. Between those two versions, little more than a year and a half passed. To give another example, CSS3 is an amalgam of many different modules, some of which are still working drafts, while one (Selectors Level 3) is already a proposed recommendation (third of four steps). What this means is that some aspects of the next level of CSS are already moving along regardless of the status of CSS 2.1



When you look at the names of the editors working on CSS 2.1 (Bert Bos, Tantek Çelik, Ian Hickson, Håkon Wium Lie) and compare them to the names on the CSS Selectors Level 3 proposed recommendation (Tantek Çelik, Elika J. Etemad, Daniel Glazman, Ian Hickson, Peter Linss, John Williams), you'll see some crossover. You may even recognize one of those names (Ian Hickson) as prominent in the WHATWG, working on HTML5.



The CSS Working Group recently (June 30) posted an update on CSS 2.1. Here are some of the salient points:



[G]iven the recent changes in the spec - we resolved a lot of issues some of them pretty complicated - we may have to go back to Last Call Working Draft and then back to [Candidate Recommendation] again. That's not a problem and can be relatively fast.


From that statement, the 2.1 specification may have to slide back a step before it can advance.



The W3C relies on a functional Test Suite before it can submit a specification to the next step, this is their expectation on the timing as a result:



[T]he Test Suite and the [Candidate Recommendation] should be available at same time and that time should be, as planned by the WG, after the summer. That should leave us enough time to reach Proposed Recommendation before the end of the year, as expected.


The Working Group does acknowledge that future CSS specifications hinge on what they are doing here:



[CSS] 2.1 must be released as a Web Standard because that's one of the current cornerstones of the architecture of the World Wide Web. We cannot make the next steps, CSS 3 even module by module, happen without 2.1 before.


I read that as a timeline on the soonest that CSS3 can move ahead as well, which is essentially no sooner than the end of 2010.



Update: October 8, 2010




I have been called out! HTML5 guru and all around odd bird has "referenced" me in his latest blog post:




CSS 2.1 “not ready for use” says journalist



Update: June 7, 2011




13 years on and CSS 2.1 is now an official recommendation. Read what I wrote when that decision cam down: CSS 2.1 is Finally Final



Another Update: October 14, 2011




Alexander Ovsov of Web Geek Science offered to translate this post to Romanian, and my ego could not resist. Go learn Romanian and read his translation:




CSS 2.1 nu este încă definitivă.

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in css, html, standards, W3C, whatwg | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Browser Performance Chart
    Jacob Gube has posted a handy chart over at Six Revisions titled " Performance Comparison of Major Web Browsers ." He tests the c...
  • Google Dashboard: What Google Knows about You
    Google announced a new service/feature today, Google Dashboard . Given all the services Google offers and all the ways you can interact with...
  • Facebook, HTML5, and Mis-Reporting
    My Twitter stream and the headlines of sites across the web yesterday lit up with Facebook's CEO blaming its stock price (failure to mee...
  • The Science of Trust in Social Media
    I am one of those people who always needs to see proof of some assertion, evidence to back up a claim. While I can accept anecdotal evidence...
  • App Store Meta Tags
    Why yes, Dominos, I'd love to tap again to get your real home page to order a pizza when I could have done it right here, below your ove...
  • Speaking at Mom 2.0 in Houston, TX
    I will be in Houston this week to speak at the Mom 2.0 Summit (Feb. 18-20, 2010, Houston, TX). To make it a little easier to describe, here...
  • Codepen Has Handy Sharing Tools for Devs
    There are plenty of online resources for playing around with code right in the browser, no server of your own needed, that you can then shar...
  • History of Eye-Tracking as Research Tool
    If you've ever wondered what eye-tracking is and where it came from, there is a historical breakdown in the article A Brief History of E...
  • Opera: Presto! It's now WebKit
    Opera is replacing its Presto rendering engine with WebKit (Chromium, really, when you factor in the V8 JavaScript rendering engine). Big n...
  • Developer Discusses Dyslexia and Dyscalculia
    Sabrina Dent , a web designer hailing from Ireland, has blogged about her struggle with dyslexia and dyscalculia and web applications today...

Categories

  • accessibility
  • Adobe
  • analytics
  • Apple
  • apps
  • ARIA
  • Bing
  • Blink
  • Brightkite
  • browser
  • Buzz
  • Chrome
  • clients
  • css
  • design
  • Facebook
  • Firefox
  • Flash
  • fonts
  • food
  • Foursquare
  • g11n
  • geolocation
  • globalization
  • Google
  • Gowalla
  • html
  • i18n
  • ICANN
  • infographic
  • Instagram
  • internationalization
  • internet
  • Internet Explorer
  • JavaScript
  • JAWS
  • Klout
  • L10n
  • law
  • localization
  • Lynx
  • Mapquest
  • Microsoft
  • mobile
  • Netscape
  • ning
  • Opera
  • patents
  • picplz
  • Plus
  • print
  • privacy
  • project management
  • QR
  • rant
  • RSS
  • Safari
  • SCVNGR
  • search
  • SEM
  • SEO
  • social media
  • Sony
  • speaking
  • standards
  • SVG
  • touch
  • translation
  • Twitter
  • typefaces
  • usability
  • UX
  • Verizon
  • video
  • W3C
  • WAI
  • WCAG
  • WebKit
  • whatwg
  • Wired
  • WOFF
  • xhtml
  • Yahoo
  • YouTube

Blog Archive

  • ►  2013 (39)
    • ►  December (1)
    • ►  November (7)
    • ►  September (4)
    • ►  July (3)
    • ►  June (2)
    • ►  May (5)
    • ►  April (3)
    • ►  March (6)
    • ►  February (2)
    • ►  January (6)
  • ►  2012 (63)
    • ►  December (2)
    • ►  November (4)
    • ►  October (5)
    • ►  September (5)
    • ►  August (4)
    • ►  July (6)
    • ►  June (7)
    • ►  May (7)
    • ►  April (8)
    • ►  March (5)
    • ►  February (3)
    • ►  January (7)
  • ►  2011 (67)
    • ►  December (5)
    • ►  November (7)
    • ►  October (5)
    • ►  September (4)
    • ►  August (8)
    • ►  July (3)
    • ►  June (8)
    • ►  May (3)
    • ►  April (1)
    • ►  March (6)
    • ►  February (6)
    • ►  January (11)
  • ▼  2010 (100)
    • ►  December (8)
    • ►  November (7)
    • ►  October (5)
    • ►  September (10)
    • ►  August (7)
    • ▼  July (11)
      • Trying Google Font Previewer
      • Unicorn Validator
      • This, the F**k, Is Social Media Now
      • Opera Rep Provides HTML5 Overview
      • W3C Cheat Sheet Now Includes HTML5
      • Working Around CSS3 Hacks
      • CSS 2.1 Still Not Final
      • Methods to Select an HTML5 Element
      • Does Your Browser Really Support HTML5 and CSS3?
      • UX Challenges in Touch Interfaces (at evolt.org)
      • Social Media Day in Buffalo #smdayBUF
    • ►  June (12)
    • ►  May (6)
    • ►  April (8)
    • ►  March (10)
    • ►  February (5)
    • ►  January (11)
  • ►  2009 (51)
    • ►  December (9)
    • ►  November (6)
    • ►  October (21)
    • ►  September (13)
    • ►  August (2)
  • ►  2003 (3)
    • ►  October (1)
    • ►  January (2)
  • ►  2002 (9)
    • ►  December (1)
    • ►  June (3)
    • ►  April (1)
    • ►  March (3)
    • ►  January (1)
  • ►  2001 (1)
    • ►  February (1)
  • ►  2000 (4)
    • ►  October (1)
    • ►  July (1)
    • ►  June (1)
    • ►  January (1)
  • ►  1999 (7)
    • ►  November (1)
    • ►  September (2)
    • ►  August (2)
    • ►  July (1)
    • ►  June (1)
Powered by Blogger.

About Me

Unknown
View my complete profile