Bug 50555 – implement the HTML5 "context menu" feature (contextmenu attribute)

• Component: WebCore Misc.
• Status: RESOLVED WONTFIX

[sideshowbarker]

In the HTML5 spec, section 4.11.4.3, "Context menus", specifies a mechanism for allowing author-developers to define a custom context menu for a particular element. The mechanism enables author-developers to define the context menu declaratively, through markup, by using a "contextmenu" attribute whose value is the ID of a particular menu element in the same document.

http://dev.w3.org/html5/spec/interactive-elements.html#context-menus

[sideshowbarker]

Mozilla are working on an implementation of this that looks like it will land soonish

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

[Jan Varga]

Actually the basic implementation has already landed.
FYI, the supported syntax differs a bit:

<menu type="context">
  <menuitem label="Foo"></menuitem>
</menu>

if you're interested, we can provide more details ...

[Olli Pettay (:smaug)]

And plenty of spec bugs have been filed to fix menu/command API.

[Antaryami Pandia]

(In reply to comment #2)
> Actually the basic implementation has already landed.
> FYI, the supported syntax differs a bit:
> 
> <menu type="context">
>   <menuitem label="Foo"></menuitem>
> </menu>
> 
> if you're interested, we can provide more details ...

We have started working on html5 menu item (https://bugs.webkit.org/show_bug.cgi?id=58454) and also be working on context menu.

So can you please share the overall architecture/design documents.Also it will be good if the same can be posted as a webkit blog and/or on a webkit-dev list.That way other people can also share thoughts.

[Jan Varga]

Ok, I'll put together some info for you...

The most import thing is that our implementation doesn't use the command API to generate custom context menu items and that we added a new element <menuitem>.

In the meantime you can check out the patch:
https://bug617528.bugzilla.mozilla.org/attachment.cgi?id=551436

[Antaryami Pandia]

(In reply to comment #5)
> Ok, I'll put together some info for you...
> 
> The most import thing is that our implementation doesn't use the command API to generate custom context menu items and that we added a new element <menuitem>.
> 
> In the meantime you can check out the patch:
> https://bug617528.bugzilla.mozilla.org/attachment.cgi?id=551436

Thanks for info.
Is there any plan to push these new element/changes to spec?

[Jan Varga]

(In reply to comment #6)
> Thanks for info.
> Is there any plan to push these new element/changes to spec?

the discussion is still ongoing

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13608

[Jan Varga]

hey, if you're still working on it, could you comment in the w3c <menuitem> bug ?
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13608

[Antaryami Pandia]

of late our priorities has been changed.so I am not actively working on this now.

As for <menuitem> is considered, I feel it's better to know the opinion of larger webkit community.

[Bronislav Klucka]

any news here?

[Elijah El-Haddad]

I'm currently working on an open source Web IDE (Eclipse Orion) and having this feature across all browsers would be very beneficial to us.

Any plans to complete the implementation?

[Ahmad Saleem]

<menuitem> is marked as obsolete: https://html.spec.whatwg.org/multipage/obsolete.html#non-conforming-features

https://github.com/whatwg/html/pull/2742

Blink also dropped it here:

https://chromium.googlesource.com/chromium/src.git/+/e90a0487386316a1e97f69159f20fbe5933cb3b9

Gecko dropped it here:

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

______

I think we can mark this as "RESOLVED WONTFIX". Thanks!

[Ryosuke Niwa]

Yup, won't fix at this point.