Re: Recent spec change to XMLHttpRequest default Content-Type

> The specification is still in development. That you considered it stable
> is an error on your side, unfortunately.

Yes. But then there's reality...

Following that argument you could as well completely change the meaning of the
readyState field and expect the rest of the world to happily accept that.

This specification isn't some upfront design that you can wrangle in any way
you like and as long as you like. It is a documentation after the fact. It is
certainly wise to exactly lay down how XMLHttpRequest is supposed to behave.
But introducing serious changes and then pointing at the draft status is just
unrealistic.


Carsten Orthbandt


pixeltamer.net
c/o Carsten Orthbandt
Baumschulenstrasse 102
12437 Berlin
+49 (0) 30 34347690

Received on Friday, 15 June 2007 09:17:56 UTC