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: Anne van Kesteren <annevk@opera.com>
Date: Tue, 09 Jun 2009 11:58:34 +0200
To: marcosc@opera.com
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.uu84nwio64w2qv@annevk-t60>
On Tue, 09 Jun 2009 11:32:49 +0200, Marcos Caceres <marcosc@opera.com> wrote:
> Like I said, as far as WebApps is concerned requestFeature() does not
> exists. What I meant was the requestFeature() undermines <feature>
> without addressing the security issues.

I'm getting more and more confused. You claim you do not understand requestFeature(). You claim requestFeature() makes <feature> useless. You claim requestFeature() is irrelevant with respect to <feature>. And now you claim requestFeature() is less secure than <feature>.

I do not get at all the feeling that this feature is ready for standardization.

Anne van Kesteren
Received on Tuesday, 9 June 2009 09:59:14 UTC

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