Do any of you know why when you use a XHTML doctype, the coloured scrollbars turn back to normal? I like the nice coloured look the scrollbars give, but I also like the professional feel of a XHTML doctype.
Thanks in advance.
EDIT: I hated the way I sounded. I won't change the post contents; I was newb then, and many people still are.They must be in the html selector in xhtml
ie.
body, html {
/* scrollbar stuff */
}Thanks Fang! Now my pages can have colored-scrollbar goodness!
Wow, you can use html as a selector? Anything else you can do with it?http://www.quirksmode.org/viewport/experiments.htmlVery useless, but interesting.... hmm.... i wonder what a css filter would do to a html or :root element... hm. Once I can find that page i saved with all the filters ill investigate.Just to note, the reason you must use html as the selector is because, under certain DOCTYPEs (e.g., XHTML 1.0 Strict) that trigger standards-compliance mode, the <body> is no longer the canvas — but <html> is.i thot that html was for the unseen and the body was for the, well, seen. can u explain the reasoning for html becoming the canvas?Because <html> within XHTML is the Root Element and XHTML is an application of XML and a few webmasters myself included serve XHTML as a application of XML.
For example: <!-- m --><a class="postlink" href="http://www.xhtmlcoder.com/beck/">http://www.xhtmlcoder.com/beck/</a><!-- m --> will be served as XML to Opera 7.2x and Mozilla browsers and if I make a typographical code error you'll get a "Yellow Screen of Death" in Mozilla because it then uses a XML Processor and doesn't display any sloppy code...
Thanks in advance.
EDIT: I hated the way I sounded. I won't change the post contents; I was newb then, and many people still are.They must be in the html selector in xhtml
ie.
body, html {
/* scrollbar stuff */
}Thanks Fang! Now my pages can have colored-scrollbar goodness!
Wow, you can use html as a selector? Anything else you can do with it?http://www.quirksmode.org/viewport/experiments.htmlVery useless, but interesting.... hmm.... i wonder what a css filter would do to a html or :root element... hm. Once I can find that page i saved with all the filters ill investigate.Just to note, the reason you must use html as the selector is because, under certain DOCTYPEs (e.g., XHTML 1.0 Strict) that trigger standards-compliance mode, the <body> is no longer the canvas — but <html> is.i thot that html was for the unseen and the body was for the, well, seen. can u explain the reasoning for html becoming the canvas?Because <html> within XHTML is the Root Element and XHTML is an application of XML and a few webmasters myself included serve XHTML as a application of XML.
For example: <!-- m --><a class="postlink" href="http://www.xhtmlcoder.com/beck/">http://www.xhtmlcoder.com/beck/</a><!-- m --> will be served as XML to Opera 7.2x and Mozilla browsers and if I make a typographical code error you'll get a "Yellow Screen of Death" in Mozilla because it then uses a XML Processor and doesn't display any sloppy code...