[Bug 25448] New: Keyboard Event Types (some correct)

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

            Bug ID: 25448
           Summary: Keyboard Event Types (some correct)
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: travil@microsoft.com
          Reporter: crimsteam@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

Keyboard event tables
(https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#event-type-keydown)
missing some context info:
KeyboardEvent.code
KeyboardEvent.isComposing

=====

Target: Document, Element in above tables and in "5.1.1 List of DOM3 Event
Types" is correct? Any case when Document fits (of course excluding the
untrusted events)? We have this in description for keyboard event:
"... If no suitable element is in focus, the event target will be the root
element."

Writing "root element" you have means "document element"
(http://dom.spec.whatwg.org/#document-element)? 

=====

I noticed that for some keys not all keyboard events are dispatched. Example
(all in Win7):

- F1 firing only keydown event (in Chrome, IE)
- F3 firing only keydown event (in Firefox, IE)
- F6 firing only keydown event (in Chrome, IE)
- F10 firing only keydown event (in Firefox, Chrome)
- F12 firing only keydown event (in IE)
- PrintScreen firing only keyup event (in Firefox, Chrome, IE)

This behavior is to much dependent on the implementation/system/device and will
not be standardized? Information for such cases would be helpful. Now we have
different behaviors, even if the browser do similar actions (like when press F3
or F6 key).

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

Received on Thursday, 24 April 2014 22:45:47 UTC