Re: Proposal: addKeyListener and removeKeyListener Methods

This seems like a neat idea for DOM4 Events. For DOM3, shouldn't we be  
holding off on new features at this point? This spec has been delayed  
many years now, and I'd really like it if we could advance it to Last  
Call soon. Adding new features works against that. Let's get into the  
shipping mindset.


On Sep 12, 2009, at 1:36 PM, Doug Schepers wrote:

> Hi, DOM3 Events fans-
> Since DOM3 Events now has a more robust (and standardized) keyboard  
> event model, it seemed appropriate to consider more closely how it  
> might be used.  As an input device, the keyboard is particularly  
> complicated, with many keys having dedicated functionality.  To some  
> degree, I addressed this in the description of default actions of  
> the 'keydown' event [1], but there have been many times where I  
> wished to listen only to specific keys.  It's easy enough to filter  
> out the keys using the "if...else" or "switch" statements in the  
> event handler, but it would be nice to attach different listeners to  
> different keys to dispatch to different event handlers.
> Thus, I've tentatively added a proposal for new 'addKeyListener' and  
> 'removeKeyListener' methods to the Event interface, which you can  
> review and comment on in the latest draft. [2]
> I'm open to suggestions to improve this idea, and obviously it  
> depends on implementers' willingness to include it, but I would  
> personally like some mechanism to do this.
> [1]
> [2]
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG and WebApps WGs

Received on Sunday, 13 September 2009 21:32:15 UTC