W3C home > Mailing lists > Public > public-webapi@w3.org > April 2008

[DOM 3 Events] Keyboard events feedback

From: Erik Dahlström <ed@opera.com>
Date: Thu, 10 Apr 2008 16:16:09 +0200
To: "public-webapi@w3.org" <public-webapi@w3.org>
Message-ID: <op.t9ee8715gqiacl@gnorps.palace.opera.no>

Hello public-webapi,

This is some feedback based on the current draft of DOM Level 3 Events  
that I got from the team dealing with events etc at Opera:

* Current spec doesn't take the current situation into account so it  
creates just yet another system that implementors have to implement. Why  
specify a brand new "textInput" event instead of specifying "keypress"  
which everyone must support in any case? What is the interaction supposed  
to be between the "textInput" event and the "keypress" event - in what  
order do they fire, do both fire if one is cancelled by the script etc.?

* The really hard part, how to map a pressed key to a key identifier isn't  
specified at all. All there is is "A.1.5 Guidelines for defining key  
identifiers" which is non-normative and bascically says "do something that  
seems logical".

(ED: Guessing that it would be nice if the rationale for this was  
explained clearly in the spec.)

* The javascript code for listening to key events will be unreadable  
without an accompanying unicode list since evt.keyIdentifier will be  
something like "U+XXXX".

Remember that this was based on the last WD of DOM 3 Events, and that even  
if these comments may come off as a bit negative I believe that Opera  
wants to see the keyboard events specified in DOM 3 Events.

Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Thursday, 10 April 2008 14:14:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:26 UTC