12 Cross-Browser Compatibility Tools For Designers

Print Article Print Article

12 Cross-Browser Compatibility Tools For Designers

By Web Hosting Help Guy

Unless the entire world magically starts using Firefox overnight, cross-browser compatibility issues are going to be a concern for the foreseeable future. And, since fully half of the people out there are still using some version of the dreaded Internet Explorer, most of your compatibility issues are going to start there. That’s why I’ve spoken with some of the sharpest design minds within earshot of my desk to look to examine 12 of the most useful ways to address those pesky browser issues.

whhg_separator

The CSS Reset

This is one of the most comprehensive (and effective) ways to make sure your website looks good on browsers of all stripes. This small group of CSS rules gets rid of each browser’s built-in defaults and resets them to a consistent baseline. This way, many of the sizing and layout issues you would have had to deal with simply never arise.

MeyerWeb Reset

Validate your HTML and CSS

A common source of browser bugs are a browser’s attempt to interpret code that isn’t written properly – unfortunately, they sometimes get it wrong. By making sure your HTML and CSS are valid (that is, that they use the correct syntax/rules etc), you’re giving yourself a much better chance of not having those quirks pop up in the first place.

W3 HTML Validator

W3 CSS Validator

Conditional Style Sheets for IE

As a designer, you already know this – the bulk of cross-compatibility issues come from the inconsistencies between IE6/7/8 in comparison to other standard browsers like Firefox, Safari, Chrome and Opera. However, you don’t want to start messing with your style sheets to fix IE problems, since by doing so you’ll be creating new problems in browsers that are already rendering correctly. Solution? Use conditionals to load IE-specific style sheets that’ll be loaded (and consequently modify styles) solely for the version of IE you need to target.

IE Style Sheet From CSS Tricks

Getting Down and Dirty With IE Bugs

Some IE bugs, even when you identify them, can be hard to fix. But you’re welcome to try – just promise me that you won’t go it alone. Check out this great article for tips on how to fix the most common bugs you’ll run across:

List of IE Bugs from Smashing Magazine

Viewing Your Website in Multiple Browsers/OS

How can you tell what your website looks like in different browsers without owning 10 computers? You can start by installing the most common browsers on your computer. At least running the latest versions of Firefox, Opera, Safari and IE on your own computer will give you an idea of how your design is performing. To check out more browsers and multiple operating systems, check out these tools:

BrowserShots (great for browsers you might not typically have installed on your machine or alternate operating systems)

Adobe Browser Labs (since it’s now integrating into CS5, this may become a tool of choice for the Adobe core)

BrowsrCamp (see your website how a Mac would see it)

NetRenderer (for quick checks of IE)

Browser Sandbox (you can actually use the browsers – more useful that screen caps at times)

PHP Browser Detection

If you’re a developer and need to do browser detection within your scripts, this tool will do the job:

Browser Detection by TechPatterns

Encouraging Users of IE6 to Switch

IE6 is the bane of many web designer’s existences – again, as a designer, you already know this. But how can we get the rest of the world to know this if we don’t tell them? Here’s a cool add-on from Google that’ll encourage users of the outdated browser to upgrade before viewing your site, and in so doing help the world be a better place.

IE6 Warning by Google

What’s your favorite way to check if your site is working on every browser?

Comments

Mike June 3rd, 2010 at 9:43 pm

I am one of the founders of crossbrowsertesting.com, so I am of course biased. However, I think that one thing that tools like a couple that you listed above lack is the ease of seeing a difference (automated screenshot) combined with the power of interactive testing, debugging and correcting (live sessions). Our service offers this and though the above services are free and ours is not, I don’t think that you’ll find a better value if you are in need of this type of service.

Tedel June 3rd, 2010 at 10:58 pm

I have all major browsers installed. IE8, Firefox, Safari, Opera, Chrome. I don’t design for IE6 any more, I just “dropped the support” and go on.

Russell Bishop June 4th, 2010 at 1:11 am

Thanks for the tips,

I might suggest VMWare with a Windows installation as the #1 feature though. Screenshot services are generally quite slow, and only leave you with a static image from one page of your website, whereas running a virtual machine allows you to gauge the full picture of how your website functions on several browsers.

Web Hosting Help Guy June 4th, 2010 at 11:11 am

Thanks for the great tips, everyone!

Harsha M V June 7th, 2010 at 12:14 pm

awesome list bud

Fadila August 29th, 2010 at 2:26 am

hey guys, I am a web designer and I’d like to share my website with you. It’s a good idea to encourage people to upgrade to the newest version of their browser, I am going to add this feature to my website :)

Stephen February 7th, 2011 at 2:08 am

Sorry to be the raincloud of this group, but for the past couple of days I’ve been trying to get a simple html5 audio tag with reference to an mp3 file working on my site so that it can be played in Google Chrome. It plays fine in Safari, and when I upload the same html file and mp3 file onto my Yahoo Small Business-hosted site, it plays in both Safari and Google Chrome without any problem. For some reason when I have it on my Inmotion-hosted site, it won’t play on Chrome.

Feel free to take a look:

http://www.modernliterati.org/music1.php

In case you’re wondering whether I’ve got a bug in my script, I guarantee you that it’s about as simple as you can get:

Permissions for the mp3 file are set to 777, and permissions for the php file are set to 775.

Chrome users constitute about 25% of my audience, so it’s not an issue that I feel ought to be overlooked.

If anyone has a suggestion regarding a workaround using the HTML audio tag, please let me know!

Stephen February 7th, 2011 at 2:12 am

PS looks like the code that I quoted was stripped from my message. Here it is again without the brackets:

!DOCTYPE HTML
html
head
/head
body
audio controls=”controls”
source src=”song.mp3″ type=”audio/mpeg” /
/audio
/body
/html

Thanks in advance for any advice you might have!

Web Hosting Help Guy February 8th, 2011 at 12:52 pm

Hi Stephen, maybe try changing a part of your source to:

“audio controls
source src=”song.mp3″ type=”audio/mp3″ /”

If it doesn’t work, you may have to adjust some of your MIME type settings differently, which you can contact IMH’s support for help on.

You can also check out this article: http://net.tutsplus.com/tutorials/html-css-techniques/quick-tip-the-html-5-audio-element/ for more tips.

Hope this helps!

steve April 16th, 2011 at 4:26 pm

any thoughts on IE7-js, a.k.a ie7.js the javascript code by google that upgrades an ie6 browser to work like an IE7 or even IE8, or IE9?

http://code.google.com/p/ie7-js/

Web Hosting Help Guy May 3rd, 2011 at 11:41 am

Hi Steve,

Here’s a good resource to look into for that
http://stackoverflow.com/questions/403011/how-do-you-feel-about-including-ie7-js-or-ie8-js-in-your-page.

Leave A Comment

Name *required

Email *not published *required

Website