Re: XMLHttpRequest readystatechange events
On Sun, 23 Apr 2006 23:08:53 +0200, Robin Berjon [EMAIL PROTECTED] wrote: At the moment, Gecko allows adding a single onreadystatechange listener that's notified of changes in readyState. We would like to add the ability to add such listeners via addEventListener; the event name would be readystatechange. So basically this would amount to supporting EventTarget on XHR, right? This has been discussed several times by the WG, and while we like the idea it's pretty much a v2 thing. So why is that? It's not like we can move the current specification that fast to W3C Recommendation. It's also that if we don't do it now v2 isn't so much about cleaning up anymore... rather more reverse engineering. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/
Re: XMLHttpRequest readystatechange events
Hi Boris, On Apr 23, 2006, at 20:51, Boris Zbarsky wrote: At the moment, Gecko allows adding a single onreadystatechange listener that's notified of changes in readyState. We would like to add the ability to add such listeners via addEventListener; the event name would be readystatechange. So basically this would amount to supporting EventTarget on XHR, right? This has been discussed several times by the WG, and while we like the idea it's pretty much a v2 thing. Does this seem acceptable? If not, are there counter-proposals? Same answer as in the previous mail :) -- Robin Berjon Senior Research Scientist Expway, http://expway.com/
