Tag: css

CSS working group is irrelevant

A great example of this is the difference in how the WHATWG got a blog and how the CSS working group set one up. In the WHATWG, the idea was floated for a while, and then one day someone volunteered to run it, and the blog was up and running within hours. Anyone (literally anyone) can post to the WHATWG blog (there’s a moderation step that we added to deal with the spammers, but all it takes now is to get onto IRC and ask for the post you wrote to be published). The CSS working group, on the other hand, has been discussing how to set up a blog, and what the first entry should say, and what tool to use, for over 2 months! Nearly every phone call (the group has weekly teleconferences) for the past 9 weeks has had the blog discussed at some point.

more dragging of feet. i suspect some member companies have an interest in making CSS not too powerful.

YUI Grids CSS

Head over to the Google Homepage. Log In using your Google Account. Make sure you’re at your Personalized Homepage. Take a look at the source CSS file ig.css included on the page. There are a few peculiar lines of code that I recognized from another source, the Yahoo User Interface Grids CSS file.

heh. why not come out and admit it? YUI is one of the few things out of yahoo that don’t suck

CSS skins repository?

If standards conscious designers already follow conventions, then the stage is set. So I decided to look at forty designers’ sites to see what conventions were being used in common page elements like headers and banners, navigation, content and footers. Here’s what I found.

it makes a lot of sense to standardize on common container names like header, content, navigation. this allows to share CSS across sites and create a nice CSS skin repository. bergie, who pointed me to this, seems to agree. maybe OSCOM should set up a set of “recommended div elements” and start a CSS repository that uses them?
2006-10-15: nice. standardized css is something i have long worked for at OSCOM, somewhat in vain.