This document summarizes a presentation about using CSS3 features now rather than waiting for full browser support. It recommends using new CSS3 properties like fonts, shadows, gradients, and animations through various techniques including fallbacks for older browsers. Specific techniques demonstrated include @font-face, box-shadow, rgba, gradients, and Modernizr for feature detection. Examples are given of popular websites that are broken in older browsers like IE6 to argue for progressive enhancement over full backwards compatibility.
15. Browser feature: traditional
The spec writer writes feature
The browser developer implements
The web developer implements
Visitor sees feature
Tuesday 30 November 2010
16. CSS feature: now
The web developer needs feature
Web developer hacks feature into code (with JS)
Visitor sees feature
The browser developers implement the feature (wait a few months)
The spec writers write about it in the spec (wait a few years)
Tuesday 30 November 2010
17. WEB DEV’S
RESPONSIBILITY
Advance the web!
Tuesday 30 November 2010
24. Free alternatives to Typekit:
FontSquirrel Google font directory
Tuesday 30 November 2010
25. Door populariteit Typekit:
• .woff support in Firefox, coming in other browsers
• meer beschikbare fonts voor web embedding
• fonts worden herbekeken voor betere weergave op scherm (e.g.
FF META)
Tuesday 30 November 2010
46. Summary
1. Websites don’t have to look the same in every browser
2. Stop spending 5 hours debugging IE on a 20 hour project
3. Don’t spend your time creating crazy sprites and hacking
functionality into older browsers
4. Use progressively enhanced CSS3 instead :)
Tuesday 30 November 2010