[Bug 27337] New: For synthetic activation, should the original event still be dispatched?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27337

            Bug ID: 27337
           Summary: For synthetic activation, should the original event
                    still be dispatched?
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: travil@microsoft.com
          Reporter: manishearth@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

"If the instance of the activation trigger is not an event of event type click
(that is, when it does not result from a user's activation of a button or link
using a mouse or equivalent pointing device), the implementation MUST
synthesize and dispatch an event of event type click as one of the default
actions of that activation trigger. The value of the Event.target MUST be set
to the event target (normally, the currently focused element), and the event
MUST simulate a left click (i.e., the MouseEvent.button attribute value MUST be
0, and the MouseEvent.buttons attribute value MUST be 1). Other context
information of such a simulated click event is implementation dependent, but
for historical purposes, the interface for the click event MUST be the
MouseEvent interface, regardless of the actual device used to activate the
element. Preventing the default action of the activation trigger, such as with
the Event.preventDefault(), MUST stop the initiation of the activation
behavior."

This isn't clear as to what we're supposed to do with the original event. 

For example, if the user hits enter on a form control, should we also dispatch
keyboard events for the enter key, or only a mouse click event?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Sunday, 16 November 2014 02:15:57 UTC