Web Standards, JavaScript, and Kittens

Menu

Book Review: The Cross Browser Handbook

Last night I finished reading The Cross Browser Handbook by Daniel Herken and I thought I’d share some thoughts on it. The book is available in PDF form only and costs 29 dollars. He also offers a more expensive version that includes the code templates and workshops.
At a high level, the book discusses:

Rendering engines, DOCTYPE, and compatibility modes

HTML

CSS

JavaScript

Cross-browser testing

I found the beginning of the book to be extremely interesting. I had somewhat of a haphazard understanding of rendering engines and DOCTYPE before, but I think Herken did a great job of explaining the details and demonstrating the differences. He also gives what could be one of the best examples of why stuff like this matters. (I won’t ruin it, but if you run an online business than you will find his real life experience in this area quite shocking.)

The meat of the book, the three sections on HTML, CSS, and JavaScript, are not full explanations of these technologies. As the book is only 120 pages long that wouldn’t be enough to cover one of these topics.

Rather, Herken gives a very brief explanation of features (for example, box-shadow, geolocation, etc), a description of where browsers are in terms of support for that feature, and finally, a list of possible workarounds. This by itself is not new. For example, I can find support information at CanIUse.com, but the combination of a quick explanation, support, and workaround, I thought was very well done. You can quickly get an idea of what this particular thing does and how well it’s going to work in your supported browsers. My only concern here is updates. Before purchasing this book I’d ask the author if updates will be free. (I’d imagine yes, but I’d check…)

The final section on testing was quite informative. Of the seven tools he described I had heard of a grand total of one of them before. Another section that was particularly informative was the coverage of JavaScript compatibility issues with IE. In some cases I was shocked at how bad IE did things.

All in all, I think the book is worth your money. I did see a few more typos than normal (I don’t think I’ve read a book yet without a typo or two) which may be due to English not being his native language, but it wasn’t anything too bad.

There was one thing he said that I thought was misguided:

Only if you absolutely have to write your own JavaScript code you should do so!

But as my readers know, this topic is something I’ve been sharing recently on this blog and I know I’m in the minority. At the end of the day, I’ll use jQuery, but I truly feel like we need to start writing more vanilla JavaScript if we ever hope to improve our skills.

Post navigation

Sponsors

The Author

I'm Raymond Camden, a developer advocate for IBM. My primary focus is on MobileFirst, hybrid mobile development, and client-side technologies. If you would like me to speak to your group, just drop me a line.