Brief books for people who make websites
Dan Cederholm
Contents
chapter 1
Using CSS3 Today 1
chapter 2
Understanding CSS Transitions 15
chapter 3
Hover-Crafting with CSS3 27
chapter 4
Transforming the Message 48
chapter 5
Multiple Backgrounds 75
chapter 6
Enriching Forms 84
chapter 7
Micro Layouts 107
Conclusion 132
Further Reading and Resources 134
References 136
Index 138
About the Author 141
FOREWORD
Websites are not the same as pictures of websites. When one person designs in Photoshop and another converts the design to markup and CSS, the coder must make guesses and assumptions about what the designer intended. This interpretive process is never without friction—unless the coder is Dan Cederholm. When Dan codes other people’s designs, he gets everything right, including the parts the designer got wrong. For instance, Dan inevitably translates a designer’s fixed Photoshop dimensions into code that is flexible, accessible, and bulletproof. (Indeed, Dan coined the phrase “bulletproof web design” while teaching the rest of us how to do it.)
In Dan’s case, flexible never means sloppy. The details always matter. That’s because Dan is not only a brilliant front-end developer and user advocate, he is also a designer to his core. He dreams design, bleeds design, and even gave the world a new way to share design at dribbble.com. Dan is also a born teacher and funny guy whose deadpan delivery makes Steven Wright look giddy by comparison. Dan speaks all over, helping designers improve their craft, and he not only educates, he kills.
And that, my friends, is why we’ve asked him to be our (and your) guide to CSS3. You couldn’t ask for a smarter, more experienced, more design-focused guide or a bigger web standards geek than our man Dan. Enjoy the trip!
—Jeffrey Zeldman
INTRODUCTION
A lot has progressed since the initial pressing of this little green book. All good things! Many of the CSS3 properties discussed now have wider browser support, which means you can feel even more confident putting them to use. Several new properties have emerged. The economy is looking—wait.
In this second edition, I’ve brought everything up to present day. I’ve removed old hacks that are no longer necessary. And I’ve added a chapter at the end of the book on micro layouts. While we wait patiently for a true cross-browser layout system, work carries on. Fortunately, new specifications such as Flexbox and Multi-column Layout are usable today, when applied to smaller components of the overall design. The new chapter explores those options and how they dovetail our existing CSS3 toolbox.
There’s never been a better time to dive into CSS3. I hope you enjoy this updated version of what was a very fun book to write, and I look forward to the myriad ways you’ll creatively use CSS3. Onward!
1 USING CSS3 TODAY
Looking back upon the storied history of CSS, we see some important milestones that have shaped our direction as web designers. These watershed techniques, articles, and events helped us create flexible, accessible websites that we could be proud of both visually as well as under the hood.
You could argue that things began to get interesting back in 2001, when Jeffrey Zeldman wrote “To Hell With Bad Browsers” (bkaprt.com/css3-2/1/), signaling the dawn of the CSS Age. This manifesto encouraged designers to push forward and use CSS for more than just link colors and fonts, leaving behind older, incapable browsers that choked on CSS1. Yes, CSS1.
We spent the next several years discovering and sharing techniques for using CSS to achieve what we wanted for our clients and bosses. It was an exciting time to be experimenting, pushing boundaries, and figuring out complex ways of handling cross-browser rendering issues—all in the name of increased flexibility, improved accessibility, and reduced code.
Somewhere around 2006 or so, the talk about CSS went quiet. Most of the problems we needed to solve had documented solutions. Common browser bugs had multiple workarounds. We created support groups for designers emotionally scarred by inexplicable Internet Explorer bugs. Our hair started to gray. (OK, I’m speaking for myself here.) Most importantly though, the contemporary crop of browsers was relatively stagnant. This period of status quo gave us time to craft reusable approaches and establish best practices, but things got a little, dare I say, boring for the CSS aficionado yearning for better tools.
Thankfully things changed. Browsers began iterating and updating more rapidly (well, some of them anyway). Firefox and Safari not only started to gain market share, they also thrived on a quicker development cycle, adding solid standards support alongside more experimental properties. In many cases, the technologies that these forward-thinking browsers chose to implement were then folded back into draft specifications. In other words, periodically it was the browser vendors that pushed the spec along.
BUT DON’T READ THE SPEC
Ask a roomful of web designers, “Who likes reading specs?” and you might get one person to raise their hand. (If you are that person, I commend you and the free time you apparently have.) Although they serve as important references, I certainly don’t enjoy reading specifications in their entirety, nor do I recommend doing so in order to grasp CSS3 as a whole.
The good news is that CSS3 is actually a series of modules that are designed to be implemented separately and independently from each other. This is a very good thing. This segmented approach has enabled portions of the spec to move faster (or slower) than others, and has encouraged browser vendors to implement the pieces that are further along before the entirety of CSS3 is considered finished.
The W3C (bkaprt.com/css3-2/2/) explains the module approach:
Rather than attempting to shove dozens of updates into a single monolithic specification, it will be much easier and more efficient to be able to update individual pieces of the specification. Modules will enable CSS to be updated in a more timely and precise fashion, thus allowing for a more flexible and timely evolution of the specification as a whole.
The benefit here for us web designers is that along with experimentation and faster release cycle comes the ability to use many CSS3 properties before waiting until they become Candidate Recommendations, perhaps years from now.
Now, by all means, if you enjoy reading specifications, go for it! Naturally there’s a lot to be learned in there—but it’s far more practical to focus on what’s currently implemented and usable today, and those are the bits that we’ll be talking about in the rest of this chapter. Later, we’ll apply those bits in examples throughout the rest of the book.
I’ve always learned more about web design by dissecting examples in the wild rather than reading white papers, and that’s what we’ll stress in the pages that follow.
CSS3 IS FOR EVERYONE
I’ve been hearing this quite a bit from fellow web designers across the globe: “I can’t wait to use CSS3 . . . when it’s supported in all browsers.”
But the truth is large portions of CSS3 are now very well supported in the majority of browsers, and everyone can begin using CSS3 right now. Fortunately you don’t have to think differently or make drastic changes to the way you craft websites in order to do so. How can anyone use CSS3 on any project? By carefully choosing the situations where we apply CSS3, focusing squarely on the experience layer.
