Note: There are a few cases of duplicates in user autocompletion which are being worked on.

HTML5 Native Context Menu - Usability

UNCONFIRMED
Unassigned

Status

()

Firefox
Menus
UNCONFIRMED
6 years ago
4 years ago

People

(Reporter: Rodney Rehm, Unassigned)

Tracking

8 Branch
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Created attachment 576943 [details]
firefox8-native.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0.1) Gecko/20100101 Firefox/8.0.1
Build ID: 20111120135848

Steps to reproduce:

Implemented an HTML5 context menu


Actual results:

I got an HTML5 context menu. It's lacking some usability, though.


Expected results:

See attached image for side-by-side comparison.

a) Firefox „simplifies“ the menu for images and links. Obviously I don‘t need „save image“ on a text-link, and no „reload page“ on either of them. Why do I get that stuff with html5 context menus?
b) Add some checkbox/radio elements to <menuitem> of said types. Currently you can‘t tell them apart.
c) Think about moving the Fx menu to a sub <menu> of the html5 menu. I‘d argue the html5 stuff is primary and Fx‘s „save image“ a secondary (yet still important and accessible) option.

Updated

6 years ago
Blocks: 617528

Comment 1

4 years ago
There is some discussion about (c) on the W3C bugtracker[1] where I just added a new proposal[2] there which also kind of covers (a). 


[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=12999
[2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=12999#c22

Comment 2

4 years ago
… also, the last example for context menus in the spec[1] shows a solution to (c) which "hides" the default/"native" context menu items behind a disclosure triangle (which is IMO the best solution, and is used on at least Windows and Mac natively). 

[1] http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#context-menus

Updated

4 years ago
See Also: → bug 897102
You need to log in before you can comment on or make changes to this bug.