Adding DOCTYPE causes CSS weirdness — OZONE Asylum, home of the Mad Scientists

This page's ID: 21967

Edit Post

Who can edit a post?	The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.

Your User Name:
Your Password:
Login Options:	Remember Me On This Computer

Your Text: Insert Slimies » Insert UBB Code » Close Last Tag \| All Tags UBB Help	...Yes, that's what I mean. On TOP of the hardwired dtd, each browser has his own manner(s) of rendering the actual document, but to parse it, and have an "idea", image in memory, of the documents structure, browsers need the dtd. It may not be stored as a plain text file, it may be encoded, in a binary file or dll, but they need it to know what they're doing, AND it makes updating the browser easier as TP pointed out. Let's make this info useful, I'll try to build a faq to backup my point: http://www.mozilla.org/docs/web-developer/quirks/doctypes.html More proofs: Have a look at the code of the Mozilla internal "Nsparser" class, aka namespace parser: http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/nsParser.cpp Especially this particular line: [code] nsresult rv = NS_NewNavHTMLDTD(&theDTD); [/code] This makes use of an instance of a "NavHTMLDTD", to make a long story short. Basically, the actual display, as I described, starts once the rendering mode has been chosen depending on Doctype declaration, and starts using a stored DTD to compare to the current document. [small](Edited by [internallink=947]InI[/internallink] on 05-29-2004 14:15)[/small] Loading...
Options:	Enable Slimies Enable Linkwords

Edit Post