- From: Anne van Kesteren <annevk@opera.com>
- Date: Mon, 25 Sep 2006 12:06:12 +0200
- To: "Boris Zbarsky" <bzbarsky@mit.edu>
- Cc: "Web APIs WG (public)" <public-webapi@w3.org>
On Sat, 23 Sep 2006 00:19:08 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote: >> It's a host object the apply is undefined in ECMA, so I see no reason >> for the WEB API's WG to define it more than ECMA does. > > Unless you want better interoperability than ECMA provides, of course. > Which I do. Well in that case it seems to be a more broader problem that doesn't just apply to XMLHttpRequest, does it? >> I would encourage you to simply not support apply on such host objects, > > You could just make that part of the XMLHttpRequest spec. Fine by me. > As long as behavior is well-defined. > >> it's far the easiest solution, and avoids the problem you have.. > > It doesn't avoid the general interop problem. It avoids the problem in > my specific implementation, sure. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Monday, 25 September 2006 10:06:27 UTC