11th January 2011
The internet would be a much simpler place if everybody used the same browser (Firefox would be my choice, Chrome maybe if I was pushed), but as different companies vie for supremecy the gap only ever seems to get bigger. Whilst picking between lots of cool features is great in terms of fun and choice for the user, for web designers and developers it can cause problems.
People often get the terms cross browser and multiple browser compatible confused. For a website or application to be truly cross browser compatible it would have to function across ALL browsers, not just the principle cohort of IE, Firefox, Chrome, Opera and Safari. However to be multiple browser compatible only suggests it functions across more than one browser. Whilst it would be great to aim for everything on the web to be cross browser compatible, in reality you have your work cut out simply coding for the most popular and widely used.
It used to be I’d install a variety of browsers on my machine and test any site I was building in all of them before launch, but these days that approach just doesn’t cut it. For a start, it doesn’t help much when you want to see how something looks or functions in two versions of the same browser. Now I use Adobe BrowserLab, which comes built in with Dreamweaver CS5, to render my sites as they would appear in a multitude of different browsers as I’m actually designing and coding them. Whilst no tool is entirely accurate, it does give a good indiciation. There are also a variety of online tools that can help (I have only listed free options):
You should expect your designer to have an awareness of compatibility issues, but if you’re going to be working on it yourself then below are a few tips: