[Webkit-unassigned] [Bug 49904] [GTK] Add a signal to allow applications to handle its own context menu

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Dec 14 07:58:15 PST 2010


Martin Robinson <mrobinson at webkit.org> changed:

           What    |Removed                     |Added
                 CC|                            |mrobinson at webkit.org

--- Comment #9 from Martin Robinson <mrobinson at webkit.org>  2010-12-14 07:58:15 PST ---
The context menu signal + setting is already far too complex. I'm not a fan of adding another signal entirely. This patch is very close to handling every use case we need for context menus. 

The changes that make sense to me:
1. Have the signal carry a GList of default menu items. Users can modify the list to modify what the default signal handler uses for the menu.
2. Deprecate the existing context menu setting and signal.
3. Pass the actual DOM node instead of the hit test result. The DOM node carries more useful information and makes sense even for keyboard activation.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list