There are only a few browsers that need to be tested, since some of them have a common rendering mechanism ( Gecko or Webkit ). Without explaining what or why, here is current wisdom (2009):
- Build your site using Firefox or Opera (on any platform). BTW Opera uses its own engine Presto;
- Test depending on what you did not use.
- Validate (X) HTML and CSS (important!).
- Test it in> = IE7 and pay attention to glitches, if any.
- Use conditional comments in separate style sheets for each version of IE - never use CSS hacks as they will become obsolete.
- Test in IE and 7, if you want, and do the same, or use conditional comments to ask users to (politely) update their version of IE.
- Test in Safari (Webkit).
- Do not test in Chrome, you already have a proxy (Webkit)!
- Do not test in IE for Mac - the percentage is too low and it is no longer being updated.
Finally, try enlarging the text in Firefox, Opera, IE, and Safari. Opera also has a manual emulation mode for mobile phones.
You will now be covered (theatrical conjecture) 99.9% of your browser settings. If you are on OS X or Linux, you can run Windows in a virtual environment such as Parallels or Wine . Apparently, Wine also has a Windows binary, but I could not find it. Caution: you need to make sure your virtual environment allows IE to read conditional comments.
In practice, I find that if the site has valid code and works in Firefox, Safari and Opera, then IE7 will probably be all right. The only version of HTML / CSS is IE ' haslayout '. If you don't have browsers, BrowserStack is a great online testing service.
Finally, if you use Javascript, you will need to go through a similar process, the problem is that as a rapidly developing area, newer versions of some browsers handle Javascript in more and more efficient ways, so functions in older versions can break or fail quietly.
Dave evert
source share