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

Re: [whatwg] <menu> and friends

From: L. David Baron <dbaron@dbaron.org>
Date: Fri, 4 Jan 2013 19:05:04 -0800
To: Jonas Sicking <jonas@sicking.cc>
Message-ID: <20130105030504.GA11832@crum.dbaron.org>
Cc: WHATWG <whatwg@lists.whatwg.org>, "Tab Atkins Jr." <jackalmage@gmail.com>
On Friday 2013-01-04 16:52 -0800, Jonas Sicking wrote:
> On Fri, Jan 4, 2013 at 3:34 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> > On Mon, Dec 31, 2012 at 12:54 AM, Jonas Sicking <jonas@sicking.cc> wrote:
> >> What I was saying as a browser vendor is that I don't think that
> >> authors are going to use this feature unless it provide the ability to
> >> replace the existing context menu. Or at least almost entirely replace
> >> it.
> >
> > I don't think I can agree with this.  This argument would be more
> > believable if authors currently used pile-of-divs for context menus a
> > lot, but I only rarely actually see it.  I think this is because it's
> > just plain *hard* to do it even half-decently.  The extreme ease with
> > which authors will be able to create high-quality context menus with
> > <menu> will, I think, override a lot of the concerns.
> I feel that I do see this quite often. maps.google.com, Google docs,
> and Zimbra are three examples off the top of my head that I spend a
> lot of time with.

Has anyone asked the authors of these sites if they would have liked
to retain the browser's default context menu items if they had been
able to do so (while simultaneously adding their own items)?


𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                           http://www.mozilla.org/   𝄂
Received on Saturday, 5 January 2013 03:41:51 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:52 UTC