|
Easiest development processes.....
1) Code for Safari
2) Check in Firefox (Should be almost no adjustments needed, maybe 1 or 2)
3) Check for IE7 (Should be pretty solid but may need another 2 or 3 adjustments)
4) Check for IE6 (By this time the code should be fairly solid, however there will still be several things that need adjusting.)
5) Check any other browsers you wish.
The reason I code this way is because Safari is exceptionally standards compliant and since Firefox is as well, the two will almost always be the same on either the PC or Mac Platform. Moving to IE you can specifically filter CSS for IE only. This allows you to fix issues just for that browser. If you code for IE then try to fix for Safari/FF you'll find you are fixing a great deal more than if you code the other way around. I leave IE6 until last because, being the piece of junk it is, it often requires the most attention when sorting out compatibility problems and with CSS filters you can spend all the time you need correcting for only that browser.
|