This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26481 - Do we need to dispatch "click" event if trigger is from a keyboard as well?
Summary: Do we need to dispatch "click" event if trigger is from a keyboard as well?
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-31 14:12 UTC by Sanjoy
Modified: 2014-09-08 22:03 UTC (History)
2 users (show)

See Also:


Attachments

Description Sanjoy 2014-07-31 14:12:47 UTC
Here http://www.whatwg.org/specs/web-apps/current-work/#context-menus
The spec says " If the command's Action is defined as firing a click event,
either directly or via the run synthetic click activation steps algorithm, then
the relatedTarget attribute of that click event must be initialised to the
subject passed to this construct and show menu algorithm." 

There is nothing mentioned specific to keyboard event as context menu can be triggered from keyboard as well.

Can someone please clarify if we need to dispatch "click" event if trigger is from a keyboard as well?
Comment 1 Ian 'Hixie' Hickson 2014-07-31 15:29:33 UTC
The 'click' events discussed in that paragraph aren't triggered by any user input. They're triggered by the prose that describes the "Action" of the relevant command. (The Action itself is triggered by the user selecting an item in the menu, but nothing in the spec says what kind of input that should be. It could be mouse, keyboard, touch, voice, telepathy, who knows.)