Why not just get the browser companies to implement the
specifications properly so that interoperability issues cease
to be an issue?
Like, what the Web Standards group tries to do?
But, it's a little more complicated than that. If you've followed along
with Dave Hyatt's blog back when Safari first launch and/or read the
Firefox/Camino dev blogs, you'll read about how certain parts in the
W3's spec are just very vague. And from this vagueness in the spec,
you'll also see some very interesting arguments and different
interpretations between the browser developers on what *they* think the
spec means on a particular rule and why the other guy's implementation
engine ain't exactly trivial... Take a look at a nightly Safari build
and note all the test case files in that sucka...