- From: Doug Schepers <schepers@w3.org>
- Date: Thu, 17 Jul 2008 04:24:44 -0400
- To: "public-webapps@w3.org" <public-webapps@w3.org>
Hi, WebApps Fans- The minutes for the DOM3 Events Telcon of 16 July 2008 can be found here: http://www.w3.org/2008/07/16-webapps-minutes.html Or as text below: [1]W3C [1] http://www.w3.org/ - DRAFT - Web Applications Working Group Teleconference 16 Jul 2008 [2]Agenda [2] http://www.w3.org/2008/webapps/wiki/16_Jul_2008 See also: [3]IRC log [3] http://www.w3.org/2008/07/16-webapps-irc Attendees Present [Microsoft], +358.504.86aaaa, Shepazu, smaug, Travis, timeless, aemmons Regrets Carmelo Chair Doug Scribe Travis Contents * [4]Topics 1. [5]key identifiers 2. [6]mouseenter/mouseleave * [7]Summary of Action Items _________________________________________________________ <trackbot> Date: 16 July 2008 Travis will scribe. <scribe> scribenick: Travis key identifiers <shepazu> [8]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events .html [8] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html 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: [9]http://arstechnica.com/reviews/hardware/nokia-n810-review.ars/2 [9] 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, [10]http://www.microsoft.com/globaldev/reference/keyboards.mspx [10] 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 [11]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]. <shepazu> [12]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Event s.html#events-Events-KeyboardEvents-Interfaces [12] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-KeyboardEvents-Interfaces 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 [13]http://www.w3.org/2008/webapps/track/issues/40/edit . [13] 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... mouseenter/mouseleave <smaug> argh <smaug> will be back Travis: mouseenter/mouseleave can be simulated using the existing DOM L3 constructs mouseover/mouseout. ... 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 [14]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 <shepazu> [15]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Event s.html#events-event-DOMCharacterDataModified [15] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-event-DOMCharacterDataModified Adios. <timeless> zakim: +358.504.86aaaa is me <shepazu> don't sweat it :) Summary of Action Items [NEW] ACTION: shepazu to create list of future events to add to a future spec. [recorded in [16]http://www.w3.org/2008/07/16-webapps-minutes.html#action02] [NEW] 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 [17]http://www.w3.org/2008/07/16-webapps-minutes.html#action01] [End of minutes]
Received on Thursday, 17 July 2008 08:25:19 UTC