OK, so is the conclusion that XHR is implementable only in HTML5 and should be re-titled "XMLHttpRequest in HTML5" or something similar?
-----Original Message----- From: Jonas Sicking [mailto:jo...@sicking.cc] Sent: Thursday, December 17, 2009 3:14 PM To: Klotz, Leigh Cc: Boris Zbarsky; WebApps WG; Forms WG Subject: Re: XMLHttpRequest Comments from W3C Forms WG As Ian already has mentioned. No one is disputing that most of these things should be factored out of the HTML5 spec. But so far no one has stepped up to that task. Until someone does we'll have to live with the reality that these things are defined in the HTML5 spec and the HTML5 spec alone. / Jonas On Thu, Dec 17, 2009 at 2:40 PM, Klotz, Leigh <leigh.kl...@xerox.com> wrote: > Great! It sounds like more progress is being made on both putting experience > from implementations back into specifications, and in modularizing the XHR > document references, since it will give a better place than HTML5 for > reference. > > Leigh. > > -----Original Message----- > From: Boris Zbarsky [mailto:bzbar...@mit.edu] > Sent: Thursday, December 17, 2009 2:38 PM > To: Klotz, Leigh > Cc: WebApps WG; Forms WG > Subject: Re: XMLHttpRequest Comments from W3C Forms WG > > On 12/17/09 2:22 PM, Klotz, Leigh wrote: >> Thank you for the clarification. Surely then this ought to be fixed >> with an IETF or W3C document describing this fact > > After some pushback, there is in fact such a document being worked on. > It's not quite far enough to reference normatively last I checked.... > >> Is it defined in http://www.w3.org/html/wg/href/draft ? > > Yep. > > -Boris > >
