O’Reilly’s HTML & CSS: The Good Parts by Ben Henick is a new book to educate and aid web professionals in building quality web experiences. A quick disclaimer about this review: I worked on this book as a technical reviewer and the author is a colleague and friend.

This book is primarily for those who have some experience with HTML and CSS and want to refine their skills — but even front-end code ninjas will find some valuable reference material in this book. While the title implies a focus on HTML and CSS, Ben takes the time to touch on a number of related topics, such as the client-server model, creating usable interfaces, image optimization, and web typography — thus giving the reader greater insight on the wider range of knowledge and skills it takes to build a quality web site.

One of my favorite sections of the book is chapter 4, “Developing a Healthy Relationship with Standards.” Ben gives an excellent explanation of the history and benefits of standards adoption and then wraps it up with 10 rules for “standards-friendly” development. If you’re still trying to make the case for adopting standards where you work, definitely check out this chapter.

If you’ve read any of the “Good Parts” books then you know that these books also highlight the “bad parts” and “awful parts” of the subject matter. While Ben gives a good overview of the browser wars as context, he spends a number of pages calling out the various issues with Internet Explorer. (I like to think that I helped tone down some of the harsh criticism he originally wrote by reminding him of how advanced IE6 was at the time of its release.) He goes on to explain the concept of graded browser support (something near and dear to my heart) and hits on a number of seemingly nit-picky but important concepts which standardistas care about.

It’s really amazing how much information Ben packed into this 352-page book — far too much for me to address here. Besides touching on HTML5, there’s a helpful glossary and numerous reference tables. As I’m writing this review, in fact, I’m sticky-noting the book so I can easily find reference information that will help me in my day-to-day work. That said, you can also sit down and read the book cover-to-cover. (Ben’s an incredible writer.)

If you’re looking to enhance your skills, improve the quality of your work, find a better job, or even if you just want to have a backup brain handy, I recommend HTML & CSS: The Good Parts.

• HTML & CSS: The Good Parts
• by Ben Henick
• Published by O’Reilly Media, ISBN-13: 978-0596157609
• Companion web site
• 

Is Internet Explorer 6 an old, outdated, hanger-on of a browser? Yes, absolutely. Does it require the use code hacks in order to achieve semi-parity with more modern browsers? Yes, it does. Should this be such a problem for web professionals? No, it shouldn’t.

Thanks, Tracy Apps!

For a moment, forget about all of IE6′s issues, security, how much you dislike Microsoft, or whatever baggage you’re carrying around. Instead, think about IE6 as an unknown browser — perhaps as a random blip in your browser stats, or maybe as an interesting piece of tech you’ve seen on a blog or at a conference. You don’t know much about that browser or how your site is going to work on it, so what do you? You code it using web standards goodness: you create a base with semantic markup (and any server-side tech for forms), add on design via CSS, then layer on client-side interactivity with JavaScript and Ajax-y goodness — et voilà, you have a lovely, robust web experience.

Now, with some new or unknown browser, you hope for the best. But with IE6, we know what the issues are. If you’re using PNGs with alpha-transparency in your design, you’ll need an alternate solution. If you’re adding horizontal margins to floats, you know you’ll run in to a double-margin bug. If you’re trying to clear floats within a parent, you know you need to set height. You’ll need to plan for handling unsupported CSS selectors. And when it comes to JavaScript, you may not even know what to plan for (unless you spend most of your days working with JS).

But again, you’re a web professional. You know your craft. You know this platform and its issues. (If you don’t, you need to know your craft better. No, I don’t buy “newness” to the field as an excuse — this is still a present concern, so you need to understand it! Why not start with my CSS tips for IE6.) While some venting may be in order, I find the outright hatred for this browser (and other versions of IE, also bashed on a regular basis) to be downright unprofessional. Here’s why:

1. IE is still #1. While recent reports cite that its market share is shrinking, IE (all versions combined) is still the number one browser in use worldwide. The snide comments I’ve seen people make about IE (which I won’t link to) often extend to remarks about IE users, which is just about the uncoolest thing I’ve witnessed. Respect the user, regardless of browser!
2. IE6 use is shrinking. With the growing number of sites proactively messaging that support is being discontinued for IE6, its share should continue to shrink, which will lessen your burden over time. (You do have an actively managed browser support policy, to help you identify when you don’t have to support it any longer, right?) Celebrate that people are upgrading instead of harping on the stragglers.
3. Promote the best experience. Instead of complaining about having to make a fancy widget work perfectly on IE6, engage with the client/product/design team to explain how you can deliver the best possible experience to every user by honoring only what each browser is truly capable of, rather than let one browser hold you back. You now have plenty of real world examples (Google Apps, Digg, Facebook, YouTube, etc.) to back you up on this!
4. Help prepare for the future. Remind those in decision-making roles that the more time you spend looking backwards at the old, the less time you have to prepare for the new. Since I haven’t met a business owner (small, corporate, or otherwise) who doesn’t like “new”, this should snap them back to their primary focus of strategies that save money and provide for the future.
5. Don’t make yourself look like an ass. If I’m one of those poor souls still stuck supporting (or, perhaps worse, using) IE6 and I’m trying to hire someone, do you think I’m going to hire the person who’s been hating on that browser all over the interwebs? Umm, no.

I know folks are going to jump in with all sorts of comments about me not thinking about Ajax-y web apps or super beautiful design-y sites. The thing is, I do work on and continue to lead a team which works on these types of sites and apps, and yes, we’re supporting IE6 in all cases. No, it’s not to pixel perfection. No, the functionality we build for a new browser isn’t 100% replicated. But these sites aren’t as far off as you might think* — and in the cases where I’m using hacks or JS shims to get IE6 into compliance, I also have easy code management techniques for dropping support.

*In fact, very recently, after preparing business and design teams to accept far less functionality in IE6, my team delivered a cool animated design-y thing that worked perfectly in that browser! (It’s not live yet, but I’ll update this when it is.)

So take the time to inform and to educate about browser differences and support strategies. Enthusiastically suggest alternatives to your team. Track your browser metrics and get happy about those numbers changing. Say a small thank you to those at Microsoft who are working to improve IE. Get inside the IE6 user’s head and present their story, not your own tale of woe. If you need help, ask for it.

Seriously, it’ll save you from looking like an ass.