xhmtl/css validation

We need CSS and XHTML advocates. It's so much more flexable! Not to mention that we should all try to validate our pages when making changes.

Here is a link to what I use to validate xhtml (http://www.w3schools.com/). The link is bottom right. I can usually get all the HTML and CSS info I need there as well with examples.

I like to use percentages for my font sizes. Any cavates with px Vs. pt Vs percent you can talk about?

Also the official validator (http://validator.w3.org). And while we're at it, though I'm a hypocrite for going off-topic, Google Adsense is not xhtml, and will invalidate your pages, as will any plugin/hack/JavaScript which uses "document.write()".

My site: "This Page Is Valid XHTML 1.0 Transitional!"

I've never had that experience with google adsense.

Here's my home page validation. http://validator.w3.org/check?uri=http%3A%2F%2Fwww.riderinfo.com

I could be out-of-date, I became a rabid anti-Google critic/skeptic a long time ago, so perhaps the code has changed. Do they still use "document.write()"? Or do they cloak their code in a CDATA section, so that the validator ignores it?

We really should split this thread at post #28: start an "xhmtl/css validation" thread, maybe?

Ok, split.

The adsense code can be viewed on any page it appears on with a code view. It's just setting several variables. That's all ya see. I've never tried to access/read the remote code which is at http://pagead2.googlesyndication.com/pagead/show_ads.js

Ah, they use an IFRAME, and the validator won't parse the contents of a FRAME/IFRAME. So, your page validates, but the Google Adsense script/output is HTML 4.0, not XHTML.

Also, we're serving the pages with the text/html MIME type, not application/xhtml+xml, so while our code, internally, validates as XHTML 1.0 Transitional, the browser itself still sees an "HTML" page, and so doesn't hiccup on the AdSense code.

That doesn't mean the AdSense code is correct, just that the browser doesn't care.

This is a good article on making AdSense work with XHTML (http://keystonewebsites.com/articles/adsense.php).

Amazon uses an iframe too. I bet most do. A necessary evil if you want/need revenue I guess.

IFRAMEs are cool, no problem. But when you have a site/page that is XHTML, and IFRAME content that isn't, that's just sloppy and will lead to problems if you switch the MIME type from html to xml. So, the practice is holding back XHTML acceptance & development.

Revenue/Advertising providers need to create a codepath/version for each major doctype.

Really this just means using DOM methods instead of document.write(), and also using the proper element attributes, for example use "<script type='text/javascript'>" instead of "<SCRIPT Language='Javascript 1.1'>".

It isn't the IFRAME that invalidates the page, it's the "document.write()".