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

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

From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Date: Tue, 7 Jun 2011 11:10:46 +0300
CC: public-device-apis WG <public-device-apis@w3.org>
Message-ID: <AD388641-FE96-4B94-AC79-C4F80D1BA400@nokia.com>
To: Art Barstow <Art.Barstow@nokia.com>, "ext Frederick.Hirsch@nokia.com" <Frederick.Hirsch@nokia.com>
Hi,

On 6.6.2011, at 20.15, ext Frederick.Hirsch@nokia.com wrote:

[...]

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

> On Jun 6, 2011, at 8:06 AM, ext Arthur Barstow wrote:
> 
>> 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


Some experiments which could *potentially* provide inspiration for the work:

* As part of the experiment (http://paulrouget.com/e/nativecontrols/), Paul proposes a way to extend the HTML5 <menu> as follows:

[[

And I think the menu specification could help. I doesn't fit perfectly my needs. But here is a way to implement this idea:

* <menu type=application> is a menu accessible from the UA menu bar

* A <html> attribute would hide the native toolbar. The page would be in charge of creating a menu.

* <menu type=context> is menu that should be injected into the native context menu
type=toolbar could be used to override the native toolbar, but website already have toolbars (think twitter, facebook). I don't see any clean ways to use, in a progressive-enhancement manner, this toolbar. I prefer an attribute.

type=application is not part of the specification.

]]

* IE9 does something similar with Pinned Sites, but does not reuse HTML5 <menu>:

  http://msdn.microsoft.com/en-us/library/gg131029

* A Mozilla Bugzilla entry related to Pinned Sites implementation has some ideas as well:

  https://bugzilla.mozilla.org/show_bug.cgi?id=605222

In the past there has been some (very little) discussion in this WG around extending the <menu> similarly to Paul's experiment, under the umbrella of "User Interaction API":

  http://lists.w3.org/Archives/Public/public-device-apis/2009Oct/0207.html

Here's Robin's executive summary on that one for busy readers:

  http://lists.w3.org/Archives/Public/public-device-apis/2011Feb/0032.html

(User Interaction API is being split into more concrete components in the new Charter, and one part is "An API to manage application menus".)

-Anssi
Received on Tuesday, 7 June 2011 08:08:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:21 GMT