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: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Tue, 2 Jun 2009 16:20:04 +0200
To: Henri Sivonen <hsivonen@iki.fi>, public-webapps <public-webapps@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C0A26ED903D@OBEEX01.obe.access-company.com>
>>Should there be no function object for
>>frob()? Or should it be there but throw upon calling? Or something else.
There should be no function object in that case.

Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanclik@access-company.com

-----Original Message-----
From: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of Henri Sivonen
Sent: Tuesday, June 02, 2009 2:52 PM
To: public-webapps
Subject: [widgets] What does it mean to have an unavailable API

> 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>.

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.

Please specify this.

Henri Sivonen


Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda


This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.
Received on Tuesday, 2 June 2009 14:21:02 UTC

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