Category: css
How Cascading Style Sheets are implemented in current browsers, what we can do with the language, and what to look forward to.
How Cascading Style Sheets are implemented in current browsers, what we can do with the language, and what to look forward to.
When learning CSS I relied heavily on Index Dot Css, a comprehensive guide to CSS support in browsers. It’s still very useful, although sadly not updated since October 2003. After that I turned to W3Schools CSS Reference (when I didn’t have my copy of the CSS Pocket Reference to hand); it’s nicely laid out and fairly comprehensive, although with some curious omissions (no list of selectors?) and no way of telling if it’s ever updated.
Now there’s a new face on the scene; Sitepoint’s CSS Reference is out of Beta, and it looks good; nicely laid out, up-to-date browser support lists, and allows feedback from users. I haven’t used it extensively yet, but it looks pretty impressive at first glance.
Happy New Year to all! After a nice long break over Christmas and the New Year, in which I wrote not a single line of code, I’m now back in the swing of things and looking forward to all the desktop browser goodness to come this year.
I’m pleased to have my first piece of published work on Dev.Opera! The article, Progressive Enhancement with CSS 3: A better experience for modern browsers, is a rewrite of a piece I wrote for CSS3.info last Summer, which explains how to use cutting-edge CSS features to improve the user experience for visitors using modern browsers. I look forward to hearing some feedback on it.
Dev.Opera has some great articles by excellent developers, and I’m proud to be a part of it. I intend to get more works published (both on- and off-line) this year; writing longer articles is a different discipline to writing shorter blog posts, and this has been useful experience. Many thanks to Chris Mills at Opera for his help with it.
There’s an interesting post on warpspire.com at the moment, decrying the speed of implementation for HTML 5 and CSS 3 and suggesting Flash/AIR as a better alternative. I completely disagree with it, but it’s interesting nonetheless. HTML 5 in particular comes in for heavy criticism as it’s perceived that its adoption will take too long.
But, as the title of this post makes clear: you can start using HTML 5 right now!
Well, you can’t really – but with Opera and Safari, you can at least pretend to while you get used to the syntax.
I’ve been doing a bit of thinking recently.
I’ve been thinking about HTML 5 and the new semantic sectioning elements it proposes to introduce: header, footer, section, article, nav and aside.
I’ve also been thinking about the way microformats use data format standards and reserved class and id values to organise content.
Then thinking about this 2005 research into reused class names, which shows that, probably mostly unconsciously, website makers were already using the proposed HTML 5 elements as class names to organise their data.
[We work] with email client developers and the design community to improve web standards support and accessibility in email.
It’s fair to say that a large chunk of the web industry now understands the importance of standards; from browser makers to designer/developers, we’ve taken on board the years of evangelising by early adopters and in turn it informs everything we do (I sincerely hope I’m speaking for the majority here).
But there’s one area of web development where standards break down; where we place elements where they’re not supposed to go, where we (whisper it) use tables for layout. Not because we want to, but because we have to. That area is, of course, HTML emails.