20:59:24 RRSAgent has joined #webapps 20:59:24 logging to http://www.w3.org/2009/06/24-webapps-irc 20:59:26 RRSAgent, make logs public 20:59:26 Zakim has joined #webapps 20:59:28 Zakim, this will be WAPP 20:59:28 I do not see a conference matching that name scheduled within the next hour, trackbot 20:59:29 Meeting: Web Applications Working Group Teleconference 20:59:29 Date: 24 June 2009 21:00:07 Zakim, this will be DOM3 21:00:07 ok, shepazu; I see IA_WebApps(DOM3)5:00PM scheduled to start now 21:00:18 IA_WebApps(DOM3)5:00PM has now started 21:00:19 +Shepazu 21:02:55 dand has joined #webapps 21:03:11 hey guys 21:03:22 hi, dand 21:03:43 how's it going 21:03:52 is there a www-dom telecon now? or next week? 21:03:58 the chair forgot to send out the agenda, so I'm not sure who's going to show 21:04:38 no probs 21:04:45 should i dial in? or hang out here and wait first 21:04:47 I'm on the line, but if we don't have a few other people show up in the next 10 minutes, we should postpone until next week 21:04:56 ok 21:05:06 well, if you can call in, I can bring you up to speed 21:05:12 Zakim, code 21:05:12 I don't understand 'code', shepazu 21:05:20 Zakim, code? 21:05:20 the conference code is 3663 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), shepazu 21:05:27 trackbot, code? 21:05:27 Sorry, shepazu, I don't understand 'trackbot, code?'. Please refer to http://www.w3.org/2005/06/tracker/irc for help 21:08:28 +??P0 21:08:30 +??P1 21:08:44 Travis has joined #webapps 21:09:04 can't hear you guys too great 21:10:07 Zakim, ??P0 is dand 21:10:07 +dand; got it 21:10:21 Zakim, ??P1 is Travis 21:10:21 +Travis; got it 21:12:04 MSjacob has joined #webapps 21:12:23 zakim, Travis has MSjacob 21:12:23 +MSjacob; got it 21:12:25 http://dev.w3.org/2006/webapi/DOM-Level-3-Events/proposals/ 21:12:38 +??P2 21:12:49 Zakim, ??P2 is me 21:12:49 +smaug; got it 21:15:12 Short telecon today 21:16:52 shepazu: Recap: goal of the different key event flows is to find a harmoneous graph that best for user agents. 21:17:06 Travis: scribenick 21:17:19 scribenick: Travis 21:17:38 ... Not likely to spec (solve) the IME model. 21:18:17 ... Planning to publish the different models as appendices to the spec. 21:19:08 darobin has joined #webapps 21:19:34 ... Key models missing the mutation event points (where they fire) or where the DOM is modified (in user agents without mutation events) 21:19:47 ... Still need to hear from WebKit. 21:21:00 dand: I think Webkit's model is probably pretty close to Trident's 21:21:22 ... I have some people that I could contact. 21:21:22 yep 21:22:20 Topic: IME events from DOM Mailing list 21:22:39 shepazu: Some disccusion on the mailing list regarding IME. 21:25:22 Travis: two problems that they wanted to solve. 21:25:45 ... the composition box appears in random places and can occude important web page elements (like search suggestions) 21:26:15 ... other is that all user agents should implement compositionstart and compositionend events. Though, I'm not sure why? 21:26:58 dand: Not necessarily that those physical events are important, but that they do what you need... 21:27:35 ... only get fired for IME inputs (don't necessarily have to do with key events). 21:27:55 ... In IE you don't get notified of some events... 21:28:09 ... using voice or other you may get spotty notification. 21:29:41 ... Firefox's compositionstart event allows you to change the DOM and place the cursor in a new location, then the actual input will occur in the new location. 21:30:14 ... nice to grap input and contain it to a particular place in the DOM. 21:31:01 ... In general, knowing when the composition finishes is useful because you can respond to user activity when the fully composed string. 21:31:19 http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-TextEvent 21:32:40 annevk has joined #webapps 21:33:14 Travis: Does the textInput event handle these use cases...? 21:34:08 dand: compositionend could be like textInput, but the compositionstart event is still important. 21:36:03 http://www.danilatos.com/event-test/ExperimentTest.html 21:36:36 shepazu: textInput does not say where the textInput came from. Maybe it could (IME, key, voice, etc.)? 21:37:19 ... (random idea) for positioning of the IME candidate window, we could possibly put an X/Y event for where the IME window came up... 21:38:14 dand: Hmm, maybe this could get more complicated... 21:38:46 shepazu: We'll see if implementors want to do that. Don't want to jump into UI necessarily.. 21:44:18 http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-June/020553.html 21:46:23 dand: TSS is the API for IME. Browsers may not support these fully, and could through complications into the mix. 21:46:33 TSF 21:47:15 dand: IMM32 (old one), TSF (new one), others for mac/linux 21:50:16 ( https://bugzilla.mozilla.org/show_bug.cgi?id=88831 ) 21:51:06 Travis: I don't think we should go down the road of trying to spec all of the details of what an IME event model could look like 21:51:25 dand: seems very complicated to purse that and we lack implementation experience. 21:51:58 shepazu: OK. Sounds good. We should spec a minimum of compositionstart/end for IME because that's what browsers have chosen to do. 21:52:42 Topic: Method for asking the UA for what keys have been pressed down. 21:53:06 shepazu: We talked about this last week, and several folks throught there was utility there. 21:53:26 shepazu: That's about it for that topic :) 21:54:02 shepazu: dand can you see about connected us with the WebKit guy for compositionstart/end events? 21:58:36 -Travis 21:58:38 -smaug 21:58:42 -dand 21:58:47 -Shepazu 21:58:48 IA_WebApps(DOM3)5:00PM has ended 21:58:50 Attendees were Shepazu, dand, MSjacob, smaug 21:59:02 trackbot, end telcon 21:59:02 Zakim, list attendees 21:59:02 sorry, trackbot, I don't know what conference this is 21:59:03 RRSAgent, please draft minutes 21:59:03 I have made the request to generate http://www.w3.org/2009/06/24-webapps-minutes.html trackbot 21:59:04 RRSAgent, bye 21:59:04 I see no action items