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.
I’m at home with the flu at the moment, so taking the opportunity to un-star some items in Google Reader; this post is a link-dump with a little added comment.
A few of them have been in my favourites for a couple of months, so apologies if you’ve seen them already.
Just written a new post on CSS3.info (the first for a long time), on the subject of the progression of a couple of layout modules through the W3C recommendation process. It’s actually a bit more exciting than I’ve just made it sound.
The recent release of the Safari 4 Beta saw a new standards proposal from the Webkit team, for controlling animation using CSS. While there’s still a debate to be had about whether CSS is the right language for this (I still fall on the side that it doesn’t, strictly), I do think their implementation is well handled. I wanted to try it out, so I went back to the earliest form of digital entertainment: Pong!
To great fanfare, The Queen, in the company of Sir Tim Berners-Lee, unveiled the new British Monarchy website today. Unfortunately, what they unveiled was a real dog’s dinner.
Royal.gov.uk highlights the worst elements of the practice of web development; on only the second page I visited it became obvious that the site hasn’t been tested on any browser other than Internet Explorer, and a peek at the source code left me shocked.
Mozilla’s Robert O’Callahan has posted a few hints about new features expected to land in the next version (1.9.2) of the Gecko layout engine.
Allowing use of SVG in <img> and background-image is high on the list, apparently, as are background-size, multiple backgrounds, and possibly text-overflow. These features have already been implemented between Opera and Safari.
I can’t find any information yet as to when Gecko 1.9.2 will land; I think it’s doubtful it will make it into Firefox 3.1, so are we looking at 4.0 or an as yet unannounced 3.2?
Following the recent push by Microsoft and Ascender to revive the EOT format for web fonts, debate has raged over the pros and cons of the two main alternatives: embedding and linking. Richard Rutter came up with the idea to license fonts on a monthly payment basis, with the font being served from the supplier’s server (or a trusted alternative).
I think there are a number of potential problems of practicality with that approach, many of which have been raised in the comments. As a contribution to the debate, I would like to offer the following suggestion: