Standards based approaches work much more reliably across browsers than non-standards based approaches. If you do need to support multiple browsers (and really you always do, even when you think you don't) the simplest approach is usually to develop in Firefox, validate, make it work in Internet Explorer, and validate again.
Elliotte Rusty Harold<br />Author of <a href="http://cafe.elharo.com/web/refactoring-html/" target="_blank" rel="nofollow">Refactoring HTML</a>
And don't snub Safari. My Apple fan-boyism may be showing, but I think that the iPhone is going to become an important business platform going forward. [ July 16, 2008: Message edited by: Bear Bibeault ]
Nothing like a little personal pain for motivation, eh?
Joined: Nov 03, 2006
Personal pain is wonderful. Who was it that said that some of the best development efforts started out when some developer needed to scratch their own itch? Maybe Eric S. Raymond...
Last week I spent about 50% of my hours fixing data due to bugs in a couple of other peoples' programs. I suggested to my boss that they fix the data errors themselves until they've fixed the bugs
1) personal pain would serve to induce faster bug fixes 2) the pain of fixing data would be on the shoulders of those responsible for creating the problems in the first place
I'm usually not this vindictive, but these data problems are a real pain. I'm happy to fix bugs, but fixing a problem only to see it return every half hour is just too depressing. [ July 18, 2008: Message edited by: Katrina Owen ]