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: Mon, 8 Jun 2009 20:34:13 +0200
Message-ID: <b21a10670906081134v191df700uc883978c9d10605@mail.gmail.com>
To: Henri Sivonen <marcosscaceres@gmail.com>
Cc: public-webapps <public-webapps@w3.org>
2009/6/2 Henri Sivonen <hsivonen@iki.fi>:
>>
>> Ok. I see what you mean. Widget.hasFeature has slightly different semantics (in widgets, it means "did that feature I requested load and become available?"
>
> Which brings up the issue that it's unclear what it means for an API to have latent support but not having been activated with <feature>.
>

Again, excuse my ignorance, but what does  "latent support" mean?

> If a widget UA has an implementation for window.frob() and frob() requires <feature> activation, what should happen when frob() hasn't been activated with <feature>? Should there be no function object for frob()? Or should it be there but throw upon calling? Or something else.
>

Not there.

> Please specify this.

Right, I think this needs to be specified in the A&E spec but not in packaging.

-- 
Marcos Caceres
http://datadriven.com.au
Received on Monday, 8 June 2009 18:34:50 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT