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.
Mozilla have announced the release of Gran Paradiso Alpha 3, the latest step on the road to Firefox 3.
Notable in this release is support for the APNG format, which aims to provide the simple animation style of GIFs, but with the advantage of PNG’s transparency support. Unfortunately, I couldn’t get any of the examples to work.
After the issue of the overhauled CSS3 Text module recently, I wonder if the Fonts module is due for similar treatment? The current working draft states:
The working group believes this draft is stable and it therefore issues a last call for comments, before requesting the status of Candidate Recommendation for the draft. The deadline for comments is 30 August 2002.
Four and a half years ago! That’s a long feedback process!
A tiny but infuriating bug in current versions of Safari/Webkit is the one which treats any character after an apostrophe (or other special character) as the beginning of a new sentence. Not a problem that’s going to crop up many times, except when you use the text-transform declaration to capitalize a sentence.
Take this example:
It’s Apple’s Problem
Safari/Webkit users should see two capital S’s at the end of the first two words. Not the ideal solution. If you’re very concerned about your Safari visitors, you might end up not using this declaration at all.
This bug’s been identified for a long time – as long as Safari’s been available, as far as I know – and is still existent. Fingers crossed it will be gone when Safari 3.0 is launched.
15 CSS Properties You Probably Never Use (but perhaps should).
Most of these aren’t implemented in the IE browsers (do I even need to point that out?), many of them aren’t implemented in at least one of the other popular browsers, some of them are print-only.
Of the few cross-browser screen properties, probably the only one that I don’t use is clip – and honestly, I’ve never had a need to.
The more I use IE7, the more I hate it. Yes, it’s more standards-compliant and feature-rich than IE6; but if the best you can say about your browser is that it’s better than IE6, you’re not starting from a strong position. IE7 is better than IE6 as receiving ten smacks in the head is better than receiving twelve.
The reason I’m annoyed at IE7 today is that I’ve just found out they still haven’t implemented media types on the @import rule. If you’re not sure what this is, it’s a shorthand way to apply stylesheets only to specific media. Say, for example, we want to apply an external stylesheet called print.css which will apply only to printed documents; easy enough, you just do this:
John’s Essential Guide to CSS is a ‘pocket guide’ to the language. There are many out there, but I decided to link to this one because of it’s very first link: Fix Your Site with the Right DOCTYPE.
I cannot stress enough the importance of working to a valid DOCTYPE; it’s good for the web, and it’s good for web developers. I remember the Eureka! moment of discovering how DOCTYPEs work, when all of a sudden cross-browser coding became that much easier. It’s an absolute basic of web development, so if you’re not familiar with how it works then I suggest you read the article forthwith.