18:03:08 RRSAgent has joined #webapps 18:03:08 logging to http://www.w3.org/2010/04/07-webapps-irc 18:03:10 RRSAgent, make logs public 18:03:10 Zakim has joined #webapps 18:03:12 Zakim, this will be DOM3 18:03:12 ok, trackbot; I see IA_WebApps(DOM3)2:00PM scheduled to start 3 minutes ago 18:03:13 Meeting: Web Applications Working Group Teleconference 18:03:13 Date: 07 April 2010 18:03:24 Zakim, call shepazu 18:03:24 ok, shepazu; the call is being made 18:03:25 IA_WebApps(DOM3)2:00PM has now started 18:03:26 +Shepazu 18:04:01 +??P2 18:04:51 Zakim, ??P2 is Olli_Pettay 18:04:51 +Olli_Pettay; got it 18:05:11 https://bugzilla.mozilla.org/show_bug.cgi?id=556493 18:06:01 -Shepazu 18:06:04 Zakim, call shepazu 18:06:04 ok, shepazu; the call is being made 18:06:05 +Shepazu 18:07:10 +[Microsoft] 18:07:36 Travis has joined #webapps 18:09:20 Travis: https://bugzilla.mozilla.org/show_bug.cgi?id=556493 18:09:49 Scribe: Travis 18:09:53 ScribeNick: Travis 18:09:59 Topic: Click issue 18:12:46 smaug: if mousedown happens in different node then the mouseup event, then the click event does not fire. 18:12:53 ... This is underspecified today. 18:13:17 ... One of the nodes (the mousedown) is a textnode. 18:14:29 shepazu: From accessibility point-of-view, not firing click can be problemantic, especially if there is considerable mouse shaking/movement. 18:16:36 http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-mouseevent-event-order 18:17:05 The bug reproduction is here: https://bug556493.bugzilla.mozilla.org/attachment.cgi?id=436452 18:22:05 shepazu: We can add an example to section 5.2.3.2 under the click event to clarify the sentence "The click event may be preceded by the mousedown and mouseup events on the same element" 18:22:35 Travis: IE8 and 9 do not manifest this bug. 18:23:09 Action: shepazu to add an example to section 5.2.3.2 under the click event to clarify the sentence "The click event may be preceded by the mousedown and mouseup events on the same element" 18:23:10 Created ACTION-516 - Add an example to section 5.2.3.2 under the click event to clarify the sentence "The click event may be preceded by the mousedown and mouseup events on the same element" [on Doug Schepers - due 2010-04-14]. 18:23:36 shepazu: Everyone in agreement then? 18:23:39 smaug: Yes. 18:23:45 Travis: Yes. 18:24:13 Topic: i18n 18:24:16 http://lists.w3.org/Archives/Public/www-dom/2010JanMar/0051.html 18:26:52 Travis: I agree with the points 2-4 in full. 18:27:17 smaug: Yes, I also agree with those. 18:27:25 ... What are the other comments? 18:31:04 Travis: Does this impact DocumentEvent:convertKeyValue? 18:39:57 shepazu: Not directly, but I was hoping for some review on this from i18n... 18:41:57 ... convertKeyValue is generic; it takes any string (e.g, "U+571", "{", etc.) and converts to any of the four output key types. 18:42:24 ... It has utility, but DOM Events may not be the right time/place for this API. 18:43:08 ... Example, could provide "DEL" and it would spit out the delete character key (in unicode or some other format). 18:43:57 Travis: From a testing perspective, this might be hard to effectively test because of the large class of inputs/outputs. 18:44:11 shepazu: I think I will go ahead and drop this API from the spec. 18:44:52 Resolution: Drop convertKeyValue from DOM Events 18:45:02 Topic: DOM Views 18:45:05 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9336 18:46:09 Lachy has joined #webapps 18:47:08 Travis: This seems to center around our UIEvent having a "view" property 18:47:39 http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113/views.html 18:48:02 shepazu: Implementors implement the view as a Window. 18:49:11 smaug, there has been some talk about moving vm-i (view mode interface from Widgets 1.0) to CSSOM, so maybe the viewMode property should be moved to DOM-Level-2-Views? 18:50:20 kenneth: move something to DOM-Level-2-Views? 18:50:32 that is a very old spec 18:50:45 is there a newer spec for dom views? 18:50:53 no 18:51:07 shepazu: In the glossary (section 2) the definition of defaultView seems very adaquate and addresses the concept of window as we read in the feedback. 18:53:10 smaug, ah there is the http://www.w3.org/TR/DOM-Level-3-Views/ 18:55:10 kenneth: I doubt anyone has worked on that Note for ages 18:55:11 Action: smaug Ask for rationale on UIEvent "view" property feedback and send to www-dom and public-html 18:55:11 Created ACTION-517 - Ask for rationale on UIEvent "view" property feedback and send to www-dom and public-html [on Olli Pettay - due 2010-04-14]. 19:09:00 http://limi.net/articles/resource-packages 19:13:04 trackbot, end telcon 19:13:04 Zakim, list attendees 19:13:04 As of this point the attendees have been Shepazu, Olli_Pettay, [Microsoft] 19:13:05 RRSAgent, please draft minutes 19:13:05 I have made the request to generate http://www.w3.org/2010/04/07-webapps-minutes.html trackbot 19:13:06 RRSAgent, bye 19:13:06 I see 2 open action items saved in http://www.w3.org/2010/04/07-webapps-actions.rdf : 19:13:06 ACTION: shepazu to add an example to section 5.2.3.2 under the click event to clarify the sentence "The click event may be preceded by the mousedown and mouseup events on the same element" [1] 19:13:06 recorded in http://www.w3.org/2010/04/07-webapps-irc#T18-23-09 19:13:06 ACTION: smaug Ask for rationale on UIEvent "view" property feedback and send to www-dom and public-html [2] 19:13:06 recorded in http://www.w3.org/2010/04/07-webapps-irc#T18-55-11