W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

Re: [comment] XMLHttpRequest Object - Address Extensibility

From: Maciej Stachowiak <mjs@apple.com>
Date: Fri, 21 Apr 2006 14:57:01 -0700
Message-Id: <B1811C3F-A543-4879-A9CB-2B7585A5DF51@apple.com>
Cc: Karl Dubost <karl@w3.org>, "Web APIs WG (public)" <public-webapi@w3.org>
To: Anne van Kesteren <annevk@opera.com>


On Apr 21, 2006, at 12:56 PM, Anne van Kesteren wrote:

>
> On Wed, 12 Apr 2006 08:44:48 +0200, Karl Dubost <karl@w3.org> wrote:
>> Please, Address extensibility.
>
> The new extensibility section currently contains the following text:
>
>  <p>Extensions to the <code>XMLHttpRequest</code> interface are  
> reserved for
>   future work by the Web APIs WG. WGs besides the Web APIs WG may  
> extend the
>   interface, but MUST coordinate that with the Web APIs WG. UAs MAY  
> extend the
>   interface, but MUST prefix the new members using a string  
> specific to the
>   vendor following the <var>Vendor</var><var>Member</var>  scheme.  
> (Normally
>   members follow the <var>member</var> scheme.) Company Foo could  
> introduce a
>   <code>FooFollowRedirect(<var>boolean</var>)</code> method for  
> example.</p>
>  <p>Authors MAY use extension mechanisms specific to the host  
> language, like
>   <code>.prototype</code> in ECMAScript.</p>

Wouldn't this put all existing extensions (and therefore every  
existing implementation) out of compliance?

Regards,
Maciej
Received on Friday, 21 April 2006 21:57:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT