Google as the window, Windows as the door, the Doors as (never mind, this could take a while)

by Michael S. Kaplan, published on 2008/07/16 03:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2008/07/16/8737061.aspx


Someone with the name handan asked me a question in a comment yesterday, a question that reminded me of something.

I think I have mentioned before that most of this blog's traffic comes from Google searches.

Like if you take a post like How does it detect invalid characters? for a moment.

It was from January of 2005.

There are 847 unique referral entries outside of the blog (a few of which have lots of hits, suggesting links), and of that number 764 of them are from various Google pages across different languages (by comparison there were 42 across MSDN, MSN, and Live, most of which came from MSDN Search.

Anyway, when I read the question, I realized that the odds are that handan had probably reached that blog via Google. :-)

I actually wore a Google shirt to work today, it tends to keep people on their toes, a-la-George Carlin, especially when you go to meetings with Search folks!

Anyway, handan's question was:

ie6,7 display javascriot error

invalid characters.

why?

can you tell me ?

tks!

Now obviously to any programming language, the definition of an invalid character is going to be a lot stricter than the loose definition of the one used by code page conversions, since anything that breaks the syntax rules for the language can qualify.

The flaw is not generally in IE in these cases -- it is in the pages themselves with the illegal or non-conformant ECMAScript (aka JScript, aka JavaScript).

The whole thing makes me wonder if I should add a better search to the page here. I tried adding Live Search once, but I couldn't get it to work. Perhaps they are subtly steering me to Google? :-)

 

This blog brought to you by(U+10ee, aka GEORGIAN LETTER XAN)


no comments

go to newer or older post, or back to index or month or day