/irc-logs / w3c / #webapps / 2011-05-11 / end

Options:

  1. # Session Start: Wed May 11 00:00:00 2011
  2. # Session Ident: #webapps
  3. # [00:29] * Joins: MikeSmith_ (MikeSmith@114.48.58.241)
  4. # [00:31] * Quits: MikeSmith (MikeSmith@114.48.141.190) (Ping timeout)
  5. # [00:31] * MikeSmith_ is now known as MikeSmith
  6. # [01:10] * Joins: homata (homata@113.34.70.146)
  7. # [01:12] * Joins: davidb (davidb@74.13.1.225)
  8. # [01:14] * Joins: homata_ (homata@58.158.182.50)
  9. # [01:15] * Quits: homata (homata@113.34.70.146) (Ping timeout)
  10. # [01:25] * Quits: davidb (davidb@74.13.1.225) (Quit: davidb)
  11. # [02:14] * Quits: sicking (chatzilla@63.245.220.240) (Ping timeout)
  12. # [02:59] * Joins: homata__ (homata_@58.158.182.50)
  13. # [03:12] * Quits: homata__ (homata_@58.158.182.50) (Client exited)
  14. # [03:15] * Joins: davidb (davidb@74.13.1.225)
  15. # [03:31] * Quits: homata_ (homata@58.158.182.50) (Ping timeout)
  16. # [03:39] * Joins: homata_ (homata_@58.158.182.50)
  17. # [03:46] * Quits: shepazu (schepers@128.30.52.169) (Quit: Core Breach)
  18. # [04:49] * Quits: davidb (davidb@74.13.1.225) (Quit: davidb)
  19. # [05:31] * Quits: karl (karlcow@128.30.54.58) (Client exited)
  20. # [05:32] * Joins: karl (karlcow@128.30.54.58)
  21. # [05:48] * Quits: MikeSmith (MikeSmith@114.48.58.241) (Quit: MikeSmith)
  22. # [06:32] * Joins: shepazu (schepers@128.30.52.169)
  23. # [07:06] * heycam is now known as heycam|away
  24. # [07:25] * Joins: homata (homata@58.158.182.50)
  25. # [07:44] * Joins: MikeSmith (MikeSmith@111.188.80.19)
  26. # [07:53] * Joins: smaug (chatzilla@82.181.139.127)
  27. # [08:02] * Quits: MikeSmith (MikeSmith@111.188.80.19) (Quit: MikeSmith)
  28. # [08:08] * Joins: MikeSmith (MikeSmith@111.188.80.19)
  29. # [08:09] * heycam|away is now known as heycam
  30. # [08:45] * Quits: MikeSmith (MikeSmith@111.188.80.19) (Ping timeout)
  31. # [08:55] * Joins: MikeSmith (MikeSmith@114.48.235.173)
  32. # [09:01] * heycam is now known as heycam|away
  33. # [09:03] * Quits: Lachy (Lachlan@84.215.59.50) (Quit: Leaving)
  34. # [09:03] * Joins: Lachy (Lachlan@84.215.59.50)
  35. # [09:09] * Joins: sicking (chatzilla@98.210.155.80)
  36. # [09:31] * Quits: sicking (chatzilla@98.210.155.80) (Ping timeout)
  37. # [09:36] * Quits: dveditz (dveditz@63.249.106.47) (Quit: dveditz)
  38. # [09:42] * Quits: MikeSmith (MikeSmith@114.48.235.173) (Quit: MikeSmith)
  39. # [10:47] * heycam|away is now known as heycam
  40. # [10:58] * Quits: guignome (guignome@129.6.58.226) (Ping timeout)
  41. # [11:29] * Joins: guignome (guignome@129.6.58.226)
  42. # [11:45] * Quits: Lachy (Lachlan@84.215.59.50) (Quit: This computer has gone to sleep)
  43. # [11:57] * Joins: Lachy (Lachlan@213.236.208.22)
  44. # [12:26] * Quits: smaug (chatzilla@82.181.139.127) (Ping timeout)
  45. # [12:29] * Joins: rogerk (Adium@96.237.170.36)
  46. # [12:31] * Quits: Lachy (Lachlan@213.236.208.22) (Quit: Leaving)
  47. # [12:31] * Joins: Lachy (Lachlan@213.236.208.22)
  48. # [12:35] * Quits: homata_ (homata_@58.158.182.50) (Client exited)
  49. # [12:45] * Joins: MikeSmith (MikeSmith@1.112.22.192)
  50. # [13:38] * Joins: ArtB (ArtB@192.100.124.218)
  51. # [13:47] * heycam is now known as heycam|away
  52. # [14:04] * Quits: homata (homata@58.158.182.50) (Quit: Leaving...)
  53. # [14:22] * Joins: davidb (davidb@66.207.206.180)
  54. # [14:34] * Quits: rogerk (Adium@96.237.170.36) (Quit: Leaving.)
  55. # [15:42] * Quits: ArtB (ArtB@192.100.124.218) (Quit: Leaving.)
  56. # [15:43] * Joins: ArtB (ArtB@192.100.124.218)
  57. # [15:45] * ArtB changes topic to 'WebApps WG; this channel is logged @ http://krijnhoetmer.nl/irc-logs/'
  58. # [15:55] * Joins: darobin (robinb@82.224.27.116)
  59. # [15:56] * Parts: darobin (robinb@82.224.27.116)
  60. # [15:58] * Joins: rogerk (Adium@96.237.170.36)
  61. # [17:13] * Joins: Martijnc (Martijnc@84.192.44.100)
  62. # [17:14] * Joins: Martijnc_ (Martijnc@84.192.44.100)
  63. # [17:14] * Quits: Martijnc (Martijnc@84.192.44.100) (Connection reset by peer)
  64. # [17:14] * Martijnc_ is now known as Martijnc
  65. # [17:27] * Quits: Martijnc (Martijnc@84.192.44.100) (Ping timeout)
  66. # [17:28] * Joins: sicking (chatzilla@98.210.155.80)
  67. # [17:38] * Joins: smaug (chatzilla@91.154.41.202)
  68. # [17:38] * Joins: Martijnc (Martijnc@84.192.44.100)
  69. # [17:45] * Quits: sicking (chatzilla@98.210.155.80) (Ping timeout)
  70. # [17:51] * Quits: Lachy (Lachlan@213.236.208.22) (Quit: This computer has gone to sleep)
  71. # [17:53] <shepazu> ISSUE-137?
  72. # [17:53] * trackbot getting information on ISSUE-137
  73. # [17:53] <trackbot> ISSUE-137 -- Should keypress events fire when using an IME? -- raised
  74. # [17:53] <trackbot> http://www.w3.org/2008/webapps/track/issues/137
  75. # [17:53] <shepazu> ISSUE-142?
  76. # [17:53] * trackbot getting information on ISSUE-142
  77. # [17:53] <trackbot> ISSUE-142 -- one keydown might fire multiple keypress/textInput events -- raised
  78. # [17:53] <trackbot> http://www.w3.org/2008/webapps/track/issues/142
  79. # [18:44] * Joins: MikeSmith_ (MikeSmith@1.112.162.14)
  80. # [18:46] * Quits: MikeSmith (MikeSmith@1.112.22.192) (Ping timeout)
  81. # [18:46] * MikeSmith_ is now known as MikeSmith
  82. # [19:10] * Joins: jrossi (jrossi@131.107.0.117)
  83. # [19:11] <jrossi> shepazu: are you going to be able to complete those last to issues?
  84. # [19:11] <jrossi> 2*
  85. # [19:11] <shepazu> jrossi: working on them right now
  86. # [19:12] <shepazu> for issue-137, I'm just going to change keypress to say it doesn't fire when using an IME
  87. # [19:12] <jrossi> I don't believe that's true for most implementations
  88. # [19:13] <shepazu> jrossi: oh?
  89. # [19:13] <shepazu> jrossi, smaug, want to have a quick coordination call?
  90. # [19:13] <jrossi> fine by me
  91. # [19:14] <smaug> keypress *may* fire when using IME
  92. # [19:14] <shepazu> ah, ok
  93. # [19:14] <shepazu> trackbot, start telcon
  94. # [19:14] * trackbot is preparing a teleconference
  95. # [19:14] * Joins: RRSAgent (rrs-loggee@128.30.52.169)
  96. # [19:14] <RRSAgent> logging to http://www.w3.org/2011/05/11-webapps-irc
  97. # [19:14] <trackbot> RRSAgent, make logs public
  98. # [19:14] <RRSAgent> I have made the request, trackbot
  99. # [19:14] * Joins: Zakim (rrs-bridgg@128.30.52.169)
  100. # [19:14] <trackbot> Zakim, this will be DOM3
  101. # [19:14] <Zakim> ok, trackbot; I see IA_WebApps(DOM3)2:00PM scheduled to start in 49 minutes
  102. # [19:14] <trackbot> Meeting: Web Applications Working Group Teleconference
  103. # [19:14] <trackbot> Date: 11 May 2011
  104. # [19:14] <shepazu> zakim, room for 3?
  105. # [19:14] <Zakim> ok, shepazu; conference Team_(webapps)17:11Z scheduled with code 26632 (CONF2) for 60 minutes until 1811Z
  106. # [19:15] <Zakim> Team_(webapps)17:11Z has now started
  107. # [19:15] <Zakim> +Doug_Schepers
  108. # [19:15] <Zakim> +[Microsoft]
  109. # [19:15] <smaug> let's see if the connection is good enough
  110. # [19:15] * Joins: sicking (chatzilla@63.245.220.240)
  111. # [19:16] <Zakim> +??P4
  112. # [19:16] <smaug> Zakim, ??P4 is Olli_Pettay
  113. # [19:16] <Zakim> +Olli_Pettay; got it
  114. # [19:17] <jrossi> scribenick: jrossi
  115. # [19:17] <shepazu> Topic: ISSUE-137
  116. # [19:17] <jrossi> smaug: it *may* fire for IME
  117. # [19:18] <jrossi> jrossi: yes, seems implementation specific. IE9 doesn't seem to fire at all.
  118. # [19:18] <jrossi> shepazu: let's add spec text stating that
  119. # [19:20] <jrossi> resolution: add text to keypress that states this event may not fire for IME input, depending on platform/implementation
  120. # [19:20] <shepazu> Topic: legacy key events
  121. # [19:20] <shepazu> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#KeyboardEvent-supplemental-interface
  122. # [19:21] <jrossi> jrossi: yes, I'm fine with this with the new spec text
  123. # [19:21] <jrossi> shepazu: I also felt it OK to use WebIDL here since it's non-normative
  124. # [19:21] <jrossi> jrossi: agree
  125. # [19:21] <jrossi> smaug: yes, that's fine
  126. # [19:21] <jrossi> resultion: keep it as is
  127. # [19:22] <jrossi> Topic: ISSUE-142?
  128. # [19:22] <shepazu> Topic: ISSUE-142
  129. # [19:22] <jrossi> ISSUE-142?
  130. # [19:22] * trackbot getting information on ISSUE-142
  131. # [19:22] <trackbot> ISSUE-142 -- one keydown might fire multiple keypress/textInput events -- raised
  132. # [19:22] <trackbot> http://www.w3.org/2008/webapps/track/issues/142
  133. # [19:27] <jrossi> shepazu: maybe test this with a macro
  134. # [19:28] <jrossi> jrossi: testing with CTRL+V, we get one textinput
  135. # [19:28] <jrossi> jrossi: are there dead keys that are macros of multiple characters?
  136. # [19:28] <jrossi> shepazu: don't see many results from a search for these
  137. # [19:29] <jrossi> shepazu: I think it should result in only a single textinput event
  138. # [19:29] <jrossi> jrossi: I'm fine with Hallvord's suggested spec text with the caveat that IE may be broken in some unknown cases. But we probably wouldn't value those scenarios highly and would treat them as bugs.
  139. # [19:30] <jrossi> smaug: I'm fine with this. We should ask him for clarification though.
  140. # [19:30] <jrossi> shepazu: I'll follow up with Hallvord to confirm.
  141. # [19:31] <jrossi> resolution: shepazu will discuss the effect of keypress for multiple characters, but won't change the spec pending some evidence from hallvord
  142. # [19:32] <shepazu> Topic: onclick after removing element from document during onmouseup
  143. # [19:32] <shepazu> http://lists.w3.org/Archives/Public/www-dom/2011JanMar/0052.html
  144. # [19:33] <shepazu> http://lists.w3.org/Archives/Public/www-dom/2011AprJun/thread.html#msg58
  145. # [19:33] <jrossi> issue-180?
  146. # [19:33] * trackbot getting information on ISSUE-180
  147. # [19:33] <trackbot> ISSUE-180 -- onclick after removing element from document during onmouseup -- raised
  148. # [19:33] <trackbot> http://www.w3.org/2008/webapps/track/issues/180
  149. # [19:35] <shepazu> https://bugs.webkit.org/show_bug.cgi?id=60600
  150. # [19:36] <jrossi> jrossi: IE9 matches Gecko in that we don't fire click events or perform the activation when the element is removed from the document during mouseup
  151. # [19:37] <jrossi> jrossi: I don't believe it's desirable (or potentially safe) to activate links which have been removed from the document
  152. # [19:37] <jrossi> smaug: yes, I agree
  153. # [19:40] <jrossi> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-mouseevent-event-order
  154. # [19:40] <jrossi> smaug: it should probably go in 5.2.3.2 Mouse Event Order
  155. # [19:40] <jrossi> jrossi: agrees
  156. # [19:42] <jrossi> <a href="http://www.google.com" id="test">test</a>
  157. # [19:42] <jrossi> <script>
  158. # [19:42] <jrossi> var elem = document.getElementById("test");
  159. # [19:42] <jrossi> elem.addEventListener("mousedown", function(e) {
  160. # [19:42] <jrossi> alert('mousedown');
  161. # [19:42] <jrossi> elem.parentNode.removeChild(elem);
  162. # [19:42] <jrossi> }, false);
  163. # [19:42] <jrossi> elem.addEventListener("mouseup",function(e){ alert('mouseup');},false);
  164. # [19:42] <jrossi> elem.addEventListener("click",function(e){ alert('click');},false);
  165. # [19:42] <jrossi> </script>
  166. # [19:43] <jrossi> jrossi: this doesn't apply specifically to click, if you remove the element at any point in the sequence then the rest of the sequence is aborted
  167. # [19:43] <shepazu> "If an element is removed from the DOM between mousedown and mouseup, no events will be dispatched for mouseup, click, or subsequent activation events."
  168. # [19:48] <shepazu> "A mouseup event may still be dispatched on a different element, depending upon the speed of a 'click' event in the environment."
  169. # [19:49] <shepazu> "If an element is removed from the DOM between mousedown and mouseup, no events will be dispatched for mouseup, click, or subsequent activation events for that element. A mouseup event will still be dispatched on a different element."
  170. # [19:50] <jrossi> "If an element is removed from the DOM during the dispatch of mousedown and mouseup, no events will be dispatched for mouseup, click, or subsequent activation events for that element. A mouseup event will still be dispatched on a different element."
  171. # [19:50] <jrossi> "If an element is removed from the DOM between mousedown or mouseup, no events will be dispatched for mouseup, click, or subsequent activation events for that element. A mouseup event will still be dispatched on a different element."
  172. # [19:51] <jrossi> "If an element is removed from the DOM dispatch mousedown or mouseup, no events will be dispatched for mouseup, click, or subsequent activation events for that element. A mouseup event will still be dispatched on a different element."
  173. # [19:51] <shepazu> "If an element is removed from the DOM during the dispatch of a mousedown event, no events for that element will be dispatched for mouseup, click, or subsequent activation events. A mouseup event will still be dispatched on a different element."
  174. # [19:53] <jrossi> "If an element is removed from the DOM during the mouse events sequence, the remaining events of the sequence will not be fired at that element."
  175. # [19:53] <jrossi> resolution: add something to the effect of what jrossi typed
  176. # [19:54] <smaug> http://lists.w3.org/Archives/Public/www-dom/2011AprJun/0025.html
  177. # [19:57] <shepazu> topic: WebApps-ISSUE-178?
  178. # [19:57] <shepazu> WebApps-ISSUE-178?
  179. # [19:57] <jrossi> issue-178?
  180. # [19:57] * trackbot getting information on ISSUE-178
  181. # [19:57] <trackbot> ISSUE-178 -- Implementations and DOM Core allow empty string and null event types -- pending review
  182. # [19:57] <trackbot> http://www.w3.org/2008/webapps/track/issues/178
  183. # [19:59] <jrossi> jrossi: my recent change removed the requirement that initializing an event with a type of empty string or null should throw an exception
  184. # [19:59] <jrossi> jrossi: no implementation did that, and there's not really a great reason to
  185. # [19:59] <smaug> WDC http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-eventtarget-dispatchevent
  186. # [19:59] <jrossi> jrossi: jonas proposed that empty string not be allowed and instead be the indicator that an event object has yet to be initialized
  187. # [20:00] <jrossi> jrossi: I replied saying that I didn't think there was any reason type was the correct place to expose such an API. And at any rate, my change lays the ground work for another spec (such as DOM Core) to spec how such an API (to detect whether an object has been initialized) would work.
  188. # [20:01] <jrossi> jrossi: but that it seems like feature creep to add that to D3E at this point
  189. # [20:03] <jrossi> smaug: it's not the cleanest way to expose such an API
  190. # [20:04] <jrossi> shepazu: not a very intuitive way of exposing it, seems like a hack
  191. # [20:04] <jrossi> jrossi: agree
  192. # [20:05] <jrossi> resolution: spec is fine as is
  193. # [20:07] <jrossi> action: shepazu to clean out "issues" marked up in spec text
  194. # [20:07] * trackbot noticed an ACTION. Trying to create it.
  195. # [20:07] * RRSAgent records action 1
  196. # [20:07] <trackbot> Created ACTION-624 - Clean out "issues" marked up in spec text [on Doug Schepers - due 2011-05-18].
  197. # [20:07] <shepazu> Topic: http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-type-DOMActivate
  198. # [20:07] <shepazu> Topic: strange DOMACtivate wording
  199. # [20:07] <shepazu> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-type-DOMActivate
  200. # [20:11] <shepazu> http://www.w3.org/TR/DOM-Level-2-Events/events.html
  201. # [20:15] <jrossi> <a href="http://www.google.com" id="test">test</a>
  202. # [20:15] <jrossi> <script>
  203. # [20:15] <jrossi> var elem = document.getElementById("test");
  204. # [20:15] <jrossi> elem.addEventListener("DOMActivate", function(e) {
  205. # [20:15] <jrossi> console.log(e.detail);
  206. # [20:15] <jrossi> e.preventDefault();
  207. # [20:15] <jrossi> }, false);
  208. # [20:15] <jrossi> </script>
  209. # [20:16] <jrossi> jrossi: don't see a detail property in FF for DOMActivate anyway
  210. # [20:22] <jrossi> topic: Next Steps
  211. # [20:22] <jrossi> shepazu: I can close out these issues we discussed today
  212. # [20:23] <jrossi> jrossi: then will you send mail to Art and the WG list to ask for a CfC?
  213. # [20:23] <jrossi> shepazu: sure
  214. # [20:23] <jrossi> topic: DOM Core
  215. # [20:25] <jrossi> shepazu: are there any outstanding descrpancies between DOM Core and D3E?
  216. # [20:25] <jrossi> jrossi: not that I'm aware of
  217. # [20:25] <jrossi> jrossi: we covered those last week (and then rehashed one issue today)
  218. # [20:25] <jrossi> shepazu: smaug, you checked this?
  219. # [20:26] <jrossi> smaug: yes, we fixed these issues (dispatch through non DOM trees, emptystring/null event types, keeping EventException). I'm not aware of any others.
  220. # [20:28] <jrossi> shepazu: then I'll withdraw my objection to publication of DOM4 Core
  221. # [20:28] <Zakim> -[Microsoft]
  222. # [20:28] <Zakim> -Olli_Pettay
  223. # [20:29] <Zakim> -Doug_Schepers
  224. # [20:29] <Zakim> Team_(webapps)17:11Z has ended
  225. # [20:29] <Zakim> Attendees were Doug_Schepers, [Microsoft], Olli_Pettay
  226. # [20:37] * Quits: Martijnc (Martijnc@84.192.44.100) (Quit: Martijnc)
  227. # [20:53] <shepazu> trackbot, end telcon?
  228. # [20:53] <trackbot> Sorry, shepazu, I don't understand 'trackbot, end telcon?'. Please refer to http://www.w3.org/2005/06/tracker/irc for help
  229. # [20:53] <shepazu> tracbot, end telcon
  230. # [20:54] <shepazu> trackbot, end telcon
  231. # [20:54] * trackbot is ending a teleconference
  232. # [20:54] <trackbot> Zakim, list attendees
  233. # [20:54] <Zakim> sorry, trackbot, I don't know what conference this is
  234. # [20:54] <trackbot> RRSAgent, please draft minutes
  235. # [20:54] <RRSAgent> I have made the request to generate http://www.w3.org/2011/05/11-webapps-minutes.html trackbot
  236. # [20:54] <trackbot> RRSAgent, bye
  237. # [20:54] <RRSAgent> I see 1 open action item saved in http://www.w3.org/2011/05/11-webapps-actions.rdf :
  238. # [20:54] <RRSAgent> ACTION: shepazu to clean out "issues" marked up in spec text [1]
  239. # [20:54] <RRSAgent> recorded in http://www.w3.org/2011/05/11-webapps-irc#T18-03-58
  240. # [20:54] * Parts: RRSAgent (rrs-loggee@128.30.52.169)
  241. # [21:43] * Quits: ArtB (ArtB@192.100.124.218) (Quit: Leaving.)
  242. # [21:48] * Quits: davidb (davidb@66.207.206.180) (Quit: davidb)
  243. # [22:20] * Quits: rogerk (Adium@96.237.170.36) (Client exited)
  244. # [22:23] * heycam|away is now known as heycam
  245. # [22:25] * Joins: rogerk (Adium@96.237.170.36)
  246. # [22:32] * heycam is now known as heycam|away
  247. # [22:44] * Quits: rogerk (Adium@96.237.170.36) (Quit: Leaving.)
  248. # [22:50] * heycam|away is now known as heycam
  249. # [22:55] * heycam is now known as heycam|away
  250. # [22:55] * heycam|away is now known as heycam
  251. # [23:11] <shepazu> issue-180?
  252. # [23:11] * trackbot getting information on ISSUE-180
  253. # [23:11] <trackbot> ISSUE-180 -- onclick after removing element from document during onmouseup -- raised
  254. # [23:11] <trackbot> http://www.w3.org/2008/webapps/track/issues/180
  255. # [23:13] * Zakim excuses himself; his presence no longer seems to be needed
  256. # [23:13] * Parts: Zakim (rrs-bridgg@128.30.52.169)
  257. # [23:29] * Joins: arun (arun@66.108.51.176)
  258. # [23:29] <arun> Hi dom!
  259. # [23:30] <arun> You've made some WebIDL changes to FileAPI. Thanks. I'm trying to merge out some conflicts
  260. # [23:52] * Quits: Marcos (Adium@84.215.169.13) (Quit: Leaving.)
  261. # Session Close: Thu May 12 00:00:00 2011

The end :)