Markup validation of http://www.google.com
validator.w3.org
Markup validation of http://www.google.com
1–10 of 34 posts
Re: Markup validation of http://www.google.com
#2I would have expected better from google.
Re: Markup validation of http://www.google.com
#3I would have expected better from google.
You're unintentionally hilarious. You know nothing about Google's technological challenges nor the decisions behind the various circumstances where they chose to ignore the standard.
I guarantee you that there are thousands of people working at Google who are:
1. Smarter than you
2. Know more about web standards than you
Seriously, get the hell out of here.
Re: Markup validation of http://www.google.com
#4I would have expected better from google.
You're unintentionally hilarious. You know nothing about Google's technological challenges nor the decisions behind the various circumstances where they chose to ignore the standard. I guarantee you that there are thousands of people working at Google who are: 1. Smarter than you 2. Know more about web standards than you Seriously, get the hell out of here.
Gee, with so many brilliant people working there, I would have expected better from Google.
Re: Markup validation of http://www.google.com
#5Re: Markup validation of http://www.google.com
#6Earlier quoted context omitted.
You're unintentionally hilarious. You know nothing about Google's technological challenges nor the decisions behind the various circumstances where they chose to ignore the standard. I guarantee you that there are thousands of people working at Google who are: 1. Smarter than you 2. Know more about web standards than you Seriously, get the hell out of here.
Gee, with so many brilliant people working there, I would have expected better from Google.
[deleted]
Re: Markup validation of http://www.google.com
#7I read somewhere that they would rather have the page load as fast as possible on all kinds of browsers rather then have a standards compliant slow loading page.
Re: Markup validation of http://www.google.com
#8Google is well aware and proud of that fact. They cut their bandwidth in half by not validating.
I was playing with jQuery in the dev console in Chrome yesterday on the Google homepage and realized that I was writing valid jQuery, but that $("body") simply didn't exist.
Re: Markup validation of http://www.google.com
#9How has this reached the front page :|
Re: Markup validation of http://www.google.com
#10Is my memory failing me or was there indeed the time when google.com had no DOCTYPE?
That makes perfect sense if you are not going to adhere to any standards.
I suppose the reason they have a doctype now is to force browsers into standards compliant rendering mode (it would be quirks otherwise). What baffles me why did they choose HTML5 doctype if they don't care about actually adhering to the spec. They can go with and it will work just fine (any unknown doctype triggers standards compliant mode in browsers) without false claim of being compliant with some actual standard.