ISSUE-70: Should the Widget spec define a mechanism to check for the availability of an API?

api-availability

Should the Widget spec define a mechanism to check for the availability of an API?

State:
CLOSED
Product:
HISTORICAL: Widgets [Bugs and Issues are tracked via Bugzilla https://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebAppsWG]
Raised by:
Marcos Caceres
Opened on:
2008-05-13
Description:
This issue was raised during our 6 May 2008 f2f meeting in Dublin. The basic idea is a Widget would have a mechanism to determine if the widget UA supported, for example, some type of Location API.

See the minutes for the discussion and details:

http://www.w3.org/2008/05/06-waf-minutes.html#item16
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

This issue is closed since the answer to the original question posed by this issue is "Yes". A related issue has been added to the WebApps WG's issues db:

<http://www.w3.org/2008/webapps/track/issues/18>

26 Jun 2008, 15:16:53

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 70.html,v 1.1 2016/01/25 10:26:22 carine Exp $