See also: IRC log
<trackbot> Date: 16 July 2008
Travis will scribe.
<scribe> scribenick: Travis
shepazu: Looking at the latest
draft of DOM L3 Events
... using Geek alt. style, can see the testable assertions.
... now looking at changes in Appendix A.1.5
... The goal of key identifiers (I want feedback here): identify the key value as it is currently configured (key mapping + modifier keys, etc.)
<timeless> for reference, the n810 keyboard: http://arstechnica.com/reviews/hardware/nokia-n810-review.ars/2
shepazu: again: would like to identify what the current output of the key will be.
Travis: Could we walk through an example?
shepazu: Q key example.
... Press "1" key --> key identifier as "1"
... Press <shift>+"1" key --> key identifier as "!"
<timeless> for reference, http://www.microsoft.com/globaldev/reference/keyboards.mspx
shepazu: for "[" there's a unicode value (U+005B), a named value "LeftSquareBracket", and a character value "["
Travis: To make things simpler, could provide seperate accessors for key char, key name, key unicode.
<scribe> ACTION: shepazu to define either three new attributes for keyIdentifierChar, keyIdentifierName, and keyIdentifierUnicode (or an object that contains them and has stringification magic) [recorded in http://www.w3.org/2008/07/16-webapps-minutes.html#action01]
<trackbot> Created ACTION-14 - Define either three new attributes for keyIdentifierChar, keyIdentifierName, and keyIdentifierUnicode (or an object that contains them and has stringification magic) [on Doug Schepers - due 2008-07-23].
Issue: If accessKeys are a key scenario, might want to define an AccessKeyEvent for a future specification of DOM Events.
<trackbot> Created ISSUE-40 - If accessKeys are a key scenario, might want to define an AccessKeyEvent for a future specification of DOM Events. ; please complete additional details at http://www.w3.org/2008/webapps/track/issues/40/edit .
shepazu: IME (input method
editors) are still and open issue (Working on this...)
... Also, trying to get this spec to last call in 1 to 1-1/2 months. Trying hard to resolve open issues...
<smaug> will be back
Travis: mouseenter/mouseleave can
be simulated using the existing DOM L3 constructs
... the value-add is in the convenience that these events offer for certain scenarios.
(Most of these scenarios involved tracking the mouse pointer around the visual layout of the web page (versus a document-tree navigation model)
scribe: In the interest of closing on DOM L3 events, may want to consider this for a future version of the spec.
Resolution: Defer mouseenter/mouseleave for a later version of DOM Events.
shepazu: As a convenience method this is definately worth investigating...
<scribe> ACTION: shepazu to create list of future events to add to a future spec. [recorded in http://www.w3.org/2008/07/16-webapps-minutes.html#action02]
<trackbot> Created ACTION-15 - Create list of future events to add to a future spec. [on Doug Schepers - due 2008-07-23].
(multiple input, accessKey, mouseenter/leave
shepazu: Any other issues to bring up, or are we done?
<smaug> so great
<smaug> Sorry, the WLAN here @summer cottage just went down
<timeless> zakim: +358.504.86aaaa is me
<shepazu> don't sweat it :)
This is scribe.perl Revision: 1.133 of Date: 2008/01/18 18:48:51 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: Travis Inferring Scribes: Travis Default Present: [Microsoft], +358.504.86aaaa, Shepazu, smaug, Travis, timeless, aemmons Present: [Microsoft] +358.504.86aaaa Shepazu smaug Travis timeless aemmons Regrets: Carmelo Agenda: http://www.w3.org/2008/webapps/wiki/16_Jul_2008 Found Date: 16 Jul 2008 Guessing minutes URL: http://www.w3.org/2008/07/16-webapps-minutes.html People with action items: shepazu[End of scribe.perl diagnostic output]