> From:James Spahr <james at designframe.com> > > > > ahhh... cuz browsers in the future won't support HTML... > > after all, it's so radically different from XHTML and all... > > > > i don't mean to sound snotty, but i do... anyway, if you > > have a DTD, what does it matter? > > There is no reason why a browser can't support all the variations of > xHTML & HTML, if the documents include a DTD. exactly. > IMHO - all documents should be assumed to be HTML 3.2 unless these is > a doctype. Then we can move to xHTML goodness (modules and all) and > not loose support for legacy coded pages dunno 'bout the 3.2 thing... why not 2.0? after all, 3.2 started introducing a lot more 'style' tagging... but that's a whole 'nother discussion... > They key point is - it should not be all or nothing situation - > browsers can (and some do) change behavior based on the DTD. exactly again.