By Kevin Yank

W3C seeks feedback on CSS3

By Kevin Yank

CSS3 has been in the works for years, with so many new features and refinements that the specification had to be broken down into thirty modules. Most of these modules are slated for completion over the next year and a half.

By the roadmap, one of the modules that has the longest way to go is the Backgrounds & Borders module. Responsible for a whole range of enhancements, from multiple background images to image-based borders, this module is responsible for overcoming many of the limitations on visual design that currently exist for CSS applied to semantically-correct (X)HTML code. Still at the working draft stage, the module is slated for completion before the end of the year.

To this end, the W3C has put out a call for CSS-savvy designers to provide feedback on several issues affecting the module. Some of the ideas already proposed for discussion look very useful indeed, so if you’ve got a stake in CSS3 (and let’s face it, every Web designer does), get in there and have your say!


  • I can’t wait for CSS3. Everyone, fire your $0.02 into the w3c so CSS3 is great!

  • yaniv

    Looks GREAT !
    Finally no more photoshop for every little annoying curved border :)

  • Marius Ciotlos

    Looks Great, but wide browser support is FAR AWAY !

  • yes yaniv, looking forward to work on border-radius properties to define shapes of corner :)

  • Dr Livingston

    I too would welcome a lot more flexibility with CSS3 though…

    > Looks Great, but wide browser support is FAR AWAY

    This is the problem, it has always been a problem, and it will continue to be a problem. It’s a problem in 2 stages, one the vendors that are not able for whatever reason to keep up with standards, and secondly it’s a problem because users do not attempt in any way to maintain the latest browser version they use.

    So what is going to happen? Yes, we have to resort to forking and using hacks to comply with a dozen or so browsers over various platforms :(

    But maybe I’m just a skeptic huh??

  • vodkinator

    Yay! Another standard that IE won’t comply to!

  • Its Nice to hear about CSS# but the way CSS2 gets away without making a real impact, makes us concern a lot. Many a times Browsers like MS IE and OS dependencies makes things worse.If resolutions were made , or making mandatory for all the webbrowsers, all the online site to be W3C compliance by the year 2009, I think the issue of CSS3 get solved even faster.

  • velocd

    If CSS3 enables us to be more efficient with our time when designing, because of its improved functionality, yet is going to have long overdue support by IE7 (if not IE8), then the webdesign community should oust IE of its position. We wont know of course people the IE team doesn’t speak out very frequently and accurately about its road plans. We should start acting now.

    The majority of good web developers I know use standards-compliant Mozilla Firefox. Not really because it supports standards, though.

    I don’t know any professional web developers who use IE. IE lacks tabs, utilities and community-provided plugins that enrich the web development process (i.e. these). In addition to poor looking source code, I find those who solely use IE also have very poor interpretation of what W3C even promotes.

    CSS2 allows a lot of cool functionality that eases web designers, like the first-child psuedo class and being able to use attribute selectors (i.e. input[type=”submit”]).

    Yet these are very rarely used, because of IE. We support IE first because it holds most of the market share. Yet I’m not sure what makes us think people wont switch to Mozilla Firefox in a hurry if we created our pages using CSS2 features.

    Anyone I help regarding a computer issue I recommend to Mozilla Firefox, even if it’s an issue completely unrelated to IE. They listen to my compliments of the browser and switch over without hesitation.

    Future W3C standards will make it easier for developers to do their job. We should be developing for standard compliant browsers, like Firefox, and using the available features of CSS2.

    IE7 is on the horizon, and will hopefully support CSS2 to the degree Firefox does now. If it doesn’t, we’ve got brilliant ideas like the IE7 emulator:

    Design your pages for Firefox using CSS2 and for the most part they’ll render ok in IE(6) using that emulator. If your visitors complain about it being glitchy, suggest to them Firefox as the optimal choice for viewing your site and tell them that it’s only glitchy in IE because you use professional advised standards from W3C that IE does not comply with. Stick those Firefox promotional buttons on your home, about or help pages, or in the footer of your site:

    We should be recommending our guests to using the optimal browser for viewing the websites we create. A good webpage deserves to be viewed in a good browser.

    That’s all from me. ;-)

  • Anonymous

    I agree 100 percent with you, but it’s not always possible to promote FireFox on site. Word of mouth helps, and I always give a good view of FireFox but not everyone is even aware of web standards outside the development community.

    The avg person on the street doesn’t even know how a web page is constructed never mind these standards, or what a different FireFox can make to their on line experience.

    It is these people who use the default IE installation that need to be made aware that there is something bigger, better and bolder out there.

    We need an approach that pushes IE off the face of the planet, and we need that approach like yersterday if web standards are to move forward in my view.

  • Pingback: Web Standards Blog » Blog Archive » CSS3 - Backgrounds and Borders Module()

Get the latest in JavaScript, once a week, for free.