16816 2012-04-21 20:56:35 +0000 menuitem click and menu show events do not indicate what element triggered these events 2013-04-15 02:19:12 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC other RESOLVED FIXED P2 enhancement --- 17840 1 bugzilla.w3c silviapfeiffer1 eoconnor jan.varga mike public-html-admin public-html-wg-issue-tracking robin silviapfeiffer1 public-html-bugzilla oldest_to_newest 66925 0 bugzilla.w3c 2012-04-21 20:56:35 +0000 I'm noticing that the properties provided via the click event on a menuitem element and the show event on a menu element do not indicate what element was interacted with in order to trigger a context menu to be used. Consequently, one has to use a workaround by adding a listener to the contextmenu event- this does not appear to the most graceful solution. For an implementation of this workaround, see http://pastebin.com/7kS8tu2W My preferred solution would be a property on both events that indicates the element that triggered the context menu to appear. 70151 1 contributor 2012-07-18 07:00:36 +0000 This bug was cloned to create bug 17840 as part of operation convergence. 76512 2 eoconnor 2012-10-17 17:29:04 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: No spec change. Rationale: Let's revisit this in HTML.next. Note that <menu> and <command> are on the list of at-risk features for HTML5. 81776 3 robin 2013-01-21 16:00:41 +0000 Mass move to "HTML WG" 81882 4 robin 2013-01-21 16:03:20 +0000 Mass move to "HTML WG" 86193 5 silviapfeiffer1 2013-04-15 02:19:12 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/f30a842583ab4cad08c14c5141b44c74067d25f8 https://github.com/w3c/html/commit/eb32288824259d5bc48acceff5a3138fcc2aca31 Rationale: Accepted change of WHATWG