| One of the most difficult parts of designing a | | | | this is a revolutionary discovery, and it doesn't |
| website is trying to target all of the different types | | | | replace conditional comments, but this is a quick trick |
| of browsers on the market. All of them have their | | | | that can get you out of a bind in a hurry, and it's |
| own quirks, and trying to account for all of them is | | | | easier to implement than anything out there. The |
| an ongoing process. At the very least, I try to | | | | inclusion of a single character in a CSS declaration will |
| support the latest versions of all major browsers, | | | | isolate that code to either Internet Explorer 7 and |
| including Internet Explorer, Firefox, Safari, Chrome, | | | | under, or Internet Explorer 6 and under. I almost feel |
| Opera, Konqueror, and Camino. | | | | guilty about how easy this is; here's how it works. |
| Most having different flavors on Windows, Mac, and | | | | #elementName |
| Linux machines. Oh, and lets not forget the latest | | | | { color: #999; /* Shows to all browsers */ |
| platform, mobile. This collection of browsers and | | | | *color: #999; /* An asterisk shows to IE7 and under |
| platforms alone is enough to ruin a website | | | | */ |
| developers day. Luckily there are some good tricks, | | | | _color: #999; /* An underscore shows to IE6 and |
| and if applied correctly can take a lot of the work | | | | under */ } |
| out of this daunting task. | | | | Give it a shot. It really is that simple, and it works |
| I just recently picked up a new trick to add to my | | | | great! |
| arsenal of browser compatibility. Now I wouldn't say | | | | |