Secondly: for most standards bodies, there must be at least one complete implementation before a proposal can gain acceptance. Clearly here things are all backwards: everyone uses ‘text/javascript’ and no-one uses ‘application/javascript’ so it clearly isn’t a proper standard, and should continue to be ignored.

As mentioned previously, every major browser understands text/javascript.

The fact that the standards authors don’t like it is just too bad.

After all this is not only an IE thing.

It is a standards committee versus the real world thing.

Tail wagging the dog here.

Oh, and yes, scripts from Google and company are often horribly broken any ways, irrespective of the enclosing script tags.

As mentioned previously, every major browser understands text/javascript.

The fact that the standards authors don’t like it is just too bad.

After all this is not only an IE thing.

It is a standards committee versus the real world thing.

Tail wagging the dog here.

Oh, and yes, scripts from Google and company are often horribly broken any ways, irrespective of the enclosing script tags.

One more interesting thing, In the article you said:

Google script Alex was embedding…

I think here “Google script” is an important point. I have seen this time and again, scripts from Google are not confirming with the standards. If you will see HTML source for the home page of Google, it doesn’t even contain a DOCTYPE declaration. So this brings to the question:

Why does Google ignore the standards?

Generally you expect high quality work from Google. Or is it just high quality search results and sloppy code?

Pritam Barhate
————————————
WebDesignStudent.net

So… why not use the correct type, and insert the IE one within conditional IE tags below it? (<!–[if IE] etc. sort of stuff)

IE would then read the IE one, and the document would still validate, right?

Logic, are you really going to go to battle for Microsoft and it’s capabilities to follow standards? If so you are a very brave man.

Listen here logic, we’re in the middle of a good old fasioned IE bashing session. Let’s not go and end it just because IE didn’t start the problem.

On a more serious note, I have to agree that this is an annoyance, but it’s minor when compared to the other inconsistencies among browsers. Unfortunately, as the competition among browsers increases, vendors will be more likely to add features that may not be supported by other browsers in order to differentiate themselves.