W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2010

Agenda: DOM3 Events Telcon, 28 June 2010

From: Doug Schepers <schepers@w3.org>
Date: Tue, 27 Jul 2010 15:39:38 -0400
Message-ID: <4C4F35FA.2070009@w3.org>
To: "www-dom@w3.org" <www-dom@w3.org>
Hi, DOM3 Events Folks-

We will be holding the next DOM3 Events telcon on Wednesday, 28 June 
2010, at 18:00-19:30 UTC. [1]  Please adjust for your local time [2].

We meet on both phone and IRC.

   Number: Zakim Bridge +1.617.761.6200, +, or 
           conference code: 3663 ("DOM3")
   IRC channel: #webapps on irc.w3.org:6665 (that's port 6665, not the 
   Duration: 1.5 hours

Here is the proposed agenda:
* splitting out keycode/charcode table

* Composition Events
The spec should make it clear that mutations must be bounded between
compositionstart and compositionend events.
Fire textInput before every change.

* Key and KeyName
I assume the intention of event.key as specified is to be able to 
distinguish any key on the keyboard by their input or key name. Here's a 
question that was concerning me: say one uses a keyboard definition that 
maps certain keys to multiple characters. For example, if keys are 
configured to insert strings like "Up", "Down", "Left", "Right", "End", 
"Esc", "Home".. It seems to me that event.key would be set to the 
corresponding string and there would be no way in our API to distinguish 
such a key press from pressing the actual up/down/left/right arrow, end, 
esc or home keys.

Is that intentional?

(FWIW, personally I think it would be nicer to have event.key and 
event.keyName rather than trying to conflate the two into one property. 
Don't remember if I already suggested that and it was rejected.)

* add input/keyboard locale to text and keyboard events

[1] http://www.w3.org/Guide/1998/08/teleconference-calendar#s_3755

-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Tuesday, 27 July 2010 19:39:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:16 UTC