- From: Anne van Kesteren <annevk@opera.com>
- Date: Fri, 15 Jun 2007 11:20:10 +0200
- To: "Carsten Orthbandt" <carsten@pixeltamer.net>
- Cc: "Web API WG (public)" <public-webapi@w3.org>
On Fri, 15 Jun 2007 11:17:32 +0200, Carsten Orthbandt <carsten@pixeltamer.net> wrote: >> The specification is still in development. That you considered it stable >> is an error on your side, unfortunately. > > Yes. But then there's reality... The reality required the specification to change. > 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. No you can't. > 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. It's not a serious change. It's how XMLHttpRequest works in the real world. The reason Firefox 3 shows errors in the error console and Firefox 2 does not is because Firefox 2 never reported stuff in the error console for XMLHttpRequest. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Friday, 15 June 2007 09:20:13 UTC