W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2011

Re: What is "An API to manage application menus"?

From: <Frederick.Hirsch@nokia.com>
Date: Mon, 6 Jun 2011 17:15:40 +0000
To: <Art.Barstow@nokia.com>
CC: <Frederick.Hirsch@nokia.com>, <public-device-apis@w3.org>
Message-ID: <55154AB1-26CD-48CE-860F-940A39531EE3@nokia.com>

The use case is

1: exposing context menus 2: site specific menus [1], "promoting HTML5 menu to the chrome"

also see for use case and relationship to HTML5 http://paulrouget.com/e/nativecontrols/

	 A webpage should be able to expose native controls to the UA
	 A webpage, if considered as a Web App, should be able to get rid of the URL / Back Forward Tool bar
	 A webpage should be able to expose controls to the context menu

Does someone have details available to help clarify the relationship to HTML5 menu element?

regards, Frederick

Frederick Hirsch

[1] http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/att-0089/minutes-2011-03-14.html#item02

On Jun 6, 2011, at 8:06 AM, ext Arthur Barstow wrote:

> The charter for the proposed Device API WG [1] includes:
> [[
> An API to manage application menus
> ]]
> Where can I find some details about what the WG expects to specify? In particular, are there any use cases, requirements or examples?
> What is the relationship between what DA WG will specify here versus what is in HTML5:
>  http://www.w3.org/TR/html5/interactive-elements.html#the-menu-element
> -Thanks, AB
> [1] http://www.w3.org/2010/11/DeviceAPICharter.html#deliverables
Received on Monday, 6 June 2011 17:16:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:46:04 UTC