W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2013

Re: [whatwg] <menu> and friends

From: Jan Varga <jan.varga@gmail.com>
Date: Wed, 24 Jul 2013 15:29:53 +0200
Message-ID: <CAB1sDKz7ujqMdM5BJGcmv_n06A5JCu-qCsqFakfujrjN7ndz0w@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: whatwg@whatwg.org, "Tab Atkins Jr." <jackalmage@gmail.com>, Jonas Sicking <jonas@sicking.cc>
On Wed, Jul 24, 2013 at 12:45 AM, Ian Hickson <ian@hixie.ch> wrote:

> If the options are:
>
>  - authors never use the feature
>  - users lose their control over their browser
>  - the feature has a complicated API
>
> ...then we're stuck in a bad place, certainly. But I don't think those are
> the only options; what about these, for instance:
>
>  - authors use the feature anyway, and like that it gives users power
>  - browsers default to showing mainly the author's menuitems, but offer
>    a discoverable way for users to find more options if they need them
>
> Ok, the first of these two might be too optimistic, but the second should
> be workable, no? That's what the spec now suggests. I've added an example
> that shows how this could work:
>
> Before (only the author's commands):
>
> http://www.whatwg.org/specs/web-apps/current-work/images/contextmenu-collapsed.png
>
> After (the user having clicked a disclosure widget):
>
> http://www.whatwg.org/specs/web-apps/current-work/images/contextmenu-expanded.png
>
>
I like it, it's a good compromise.

Jan
Received on Wednesday, 24 July 2013 13:30:22 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:03 UTC