W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: [widgets] What does it mean to have an unavailable API

From: Marcos Caceres <marcosc@opera.com>
Date: Tue, 09 Jun 2009 01:38:14 +0200
Message-ID: <4A2DA0E6.4050303@opera.com>
To: Anne van Kesteren <annevk@opera.com>
CC: WebApps WG <public-webapps@w3.org>

On 6/8/09 11:20 PM, Anne van Kesteren wrote:
> On Mon, 08 Jun 2009 20:34:14 +0200, Marcos Caceres<marcosc@opera.com>  wrote:
>> I still have no clue what requestFeature() does/means. The again, I
>> have not read the Bondi spec regarding that.
> On Mon, 08 Jun 2009 20:34:19 +0200, Marcos Caceres<marcosc@opera.com>  wrote:
>> Yes, that was the design. If requestFeature() is introduced,<feature>
>> is basically useless.
> Now I'm confused.

hehe, join the club:)

But seriously, requestFeature() is some BONDI thing so we should not be 
discussing it here. Web Apps does not specify this anywhere: It has no 
bearing on the work Web Apps is doing and should not be discussed in the 
context of Widgets or within this working group. It may, however, become 
a topic of discussion for DAP in the future; but, again, it has 
absolutely nothing to do with W3C widgets.
Received on Monday, 8 June 2009 23:38:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:12:54 UTC