Heya Scott > Personally if we wanna go the whole hog in XHTML, i say we all should > wind it up to Strict XHTML.. why.. because we can and we roxors.
Well its not really related to HTML vs. XHTML or Transitional vs. Strict. Standards mode is usually triggered when you put the URL to the .dtd file in the doctype like this: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> Quirks mode is triggered by leaving it out like this: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> This happens regardless of what DTD you use, HTML 4 transitional, HTML 4 strict, XHTML transitional, etc... The idea is that when a browser is in standards mode it tries to do things as per the spec. When its in quirks mode it tries to replicate a bunch of buggy behaviour from the NS4 and IE4 era. >From http://www.alistapart.com/articles/doctype/: "Using an incomplete or outdated DOCTYPEâor no DOCTYPE at allâthrows these same browsers into "Quirks" mode, where the browser assumes you've written old-fashioned, invalid markup and code per the depressing industry norms of the late 1990s. In this setting, the browser will attempt to parse your page in backwardâcompatible fashion, rendering your CSS as it might have looked in IE4, and reverting to a proprietary, browserâspecific DOM. (IE reverts to the IE DOM; Mozilla and Netscape 6 revert to who knows what.)" -- Mark Stanton Gruden Pty Ltd http://www.gruden.com --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
