16:02:32 RRSAgent has joined #pointerevents 16:02:32 logging to http://www.w3.org/2012/12/04-pointerevents-irc 16:02:36 Zakim, nick smaug is Olli_Pettay 16:02:36 ok, smaug, I now associate you with Olli_Pettay 16:02:40 RRSAgent, make logs Public 16:02:48 Scribe: Art 16:02:52 +[Microsoft] 16:02:53 ScribeNick: ArtB 16:02:55 + +1.519.513.aacc 16:03:04 Agenda: http://lists.w3.org/Archives/Public/public-pointer-events/2012OctDec/0077.html 16:03:09 Date: 4 December 2012 16:03:13 Chair: Art 16:03:19 Meeting: Pointer Events WG Voice Conference 16:03:22 hmm, is it possible to teach Zakim to bind certain nick always to the right person 16:03:56 +Doug_Schepers 16:04:09 Present: Art_Barstow, Olli_Pettay, Jacob_Rossi, Rick_Byers, Asir_Vedamuthu, Scott_González, Doug_Schepers 16:04:24 mbrubeck: ping 16:04:38 Topic: Getting started 16:04:44 AB: need a scribe (cheat sheet ) 16:04:49 Present+ Matt_Brubeck 16:05:25 +??P20 16:05:46 RB: I can take it today but want someone else to help in the future 16:05:52 AB: thanks Rick 16:05:59 ScribeNick: rbyers 16:06:03 Scribe+ Rick 16:06:44 Jacob: we should rotate scribe according the bugs 16:07:17 Agenda: http://lists.w3.org/Archives/Public/public-pointer-events/2012OctDec/0077.html 16:08:07 Topic: announcements? 16:08:23 Topic: CfC to publish first public working draft 16:08:44 Art: proposal is to go ahead and publish it 16:08:56 ... but Jacob is free to update the doc, eg. to reflect any decisions made today 16:08:59 ... any objections? 16:09:02 None 16:09:14 RESOLUTION: the group agrees to publish a FPWD of Pointer Events 16:09:27 ACTION: Jacob prepare a FPWD and notify Art when it is ready (see http://www.w3.org/wiki/Webapps/SpecEditing) 16:09:27 Created ACTION-6 - Prepare a FPWD and notify Art when it is ready (see http://www.w3.org/wiki/Webapps/SpecEditing) [on Jacob Rossi - due 2012-12-11]. 16:10:31 Art: guess is doc will be published a week from today, or ... 16:10:43 Art: last date to publish this year is Dec 13 16:10:55 Asir has joined #pointerevents 16:11:22 Jacob: is there a CfC period? 16:11:33 Art: No, resolution is good enough for you to start 16:11:41 Jacob: Think I can get it in sometime this week 16:12:38 ACTION: barstow send Transition Request for FPWD of Pointer Events 16:12:39 Created ACTION-7 - Send Transition Request for FPWD of Pointer Events [on Arthur Barstow - due 2012-12-11]. 16:13:01 Topic: bugs 16:14:37 Jacob: for new bugs, suggest we wait for some discussion on the list 16:15:05 Topic: bug 20107 - Pointer events should indicate stylus eraser/inversion 16:15:17 —> https://www.w3.org/Bugs/Public/show_bug.cgi?id=20107 16:15:40 Jacob: current spec doesn't expose erase, valid feedback. 16:15:55 ... default guess: another value for the button property 16:17:20 Rick: how is the button identified? 16:17:42 Jacob: suggest we use the identifier from the USB HID 16:18:38 http://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#chorded-button-interactions 16:18:55 ... suggest appending to this table a button #5% 16:19:22 ... will send mail with suggested button name 16:19:28 ... if everyone agrees, will change the spec 16:20:16 Topic: Bug 20108 - Extend pointer events to support raw trackpad data 16:20:22 —> https://www.w3.org/Bugs/Public/show_bug.cgi?id=20108 16:20:31 correction 16:20:43 Topic: Bug 20108 - Clarify pointer capture behavior 16:21:36 Jacob: what's missing from the spec are some additional things IE10 does for the capture APIs: 16:21:44 ... see bug for details 16:23:20 Jacob: #1 - should it be possible to capture when buttons=0? 16:23:49 zakim, who is speaking? 16:24:02 rbyers, listening for 10 seconds I heard sound from the following: +1.770.402.aabb (9%), Olli_Pettay (84%) 16:24:16 Olli: may need other mechanism for UA to release pointer capture 16:24:33 ... gecko is fairly strict in it's set capture implementation 16:24:39 ... probably more so than IE 16:25:10 Jacob: sounds like we need some allowances for UAs to choose to release capture at other times 16:25:15 Olli: Agree 16:25:29 Jacob: in IE10, it also differs between Win7 and Win8 16:25:37 ... I will think through some spec text to give more freedom 16:26:28 Jacob: to clarify, IE10 only has preview on Win7 that doesn't support pointer events. 16:27:25 Jacob: #4 from bug: pointer events aren't dispatched to elements not in the document 16:28:06 ... believe this is consistent with most types of events 16:28:48 Rick: touch events is very different - always capture to the node where they started, even once removed from the document 16:29:41 Jacob: prefer not to allow events for detached element 16:29:43 Rick: agree 16:30:01 Jacob: #5: compat mouse events are also redirected to captured element 16:30:17 ... to be consistent with where pointer events 16:30:35 ... hearing no opposition, should we add them? 16:31:18 Olli: should we limited capturing to a single document? 16:31:58 Jacob: I have looked into those multi-iframe scenarios. 16:32:29 ... you're not going to get access to the dom, but you will get co-ordinate data 16:32:37 ... agree we need to be very careful. 16:32:45 ... if we come up with a specific issue, we can open a bug to add a restrictioon 16:32:51 Olli: ok 16:33:43 RESOLUTION: Will add the additional pointer capture conditions to the spec 16:34:05 Topic: 20109 - Permitted values for pressure https://www.w3.org/Bugs/Public/show_bug.cgi?id=20109 16:34:25 —> http://lists.w3.org/Archives/Public/public-pointer-events/2012OctDec/0018.html 16:34:36 http://www.usb.org/developers/devclass_docs/Hut1_12v2.pdf 16:35:04 Jacob: Input APIs in Windows are largely designed around this USB spec 16:35:31 ... defines two different ways of looking at pressure, as discussed on the list 16:36:22 ... uses both relative (0..127) and absolute (physical units) forms of pressure 16:37:11 ... get the point that a more capable pen should be able to provide higher than normal values 16:37:31 ... think we should either keep it as is, or switch to physical units 16:37:54 Olli: clear we can't report some random value that has no meaning 16:38:27 q+ 16:38:37 q- later 16:40:51 Rick: probably only conforming behavior on Android is to truncate above 1.0 16:41:04 Jacob: want the property to be interoperable and mean the same thing 16:41:45 +[Microsoft.a] 16:42:02 sorry I got dropped and reconnected 16:43:01 Rick: key question is if we have only one anchor, should we anchor against the maximum value or some subjective indication of 'norma' pressure 16:43:22 Jacob: related issue: how to report no support for pressure 16:43:33 q+ to talk about simulated pressure on touch pads 16:43:46 ... currently we report 0 16:44:16 Matt: would be nice for applicatons to have one code path for pressure sensitive and non-pressure sensitive devices 16:44:38 ... using 0 means the app must handle the two cases seperately 16:45:00 Jacob: we want this to be device agnostic - don't want to become a device properties spec 16:45:22 Jacob/Matt/Rick: agree we should simulate reasonable pressure 16:46:02 Jacob: in particular, if device does not support pressure, value should be 0 when not in active button state, and 1 when it is 16:47:55 RESOLUTION: if device does not support pressure, value should be 0 when not in active button state, and 1 when it is 16:48:27 Jacob: OK, what about max vs. normal? 16:48:48 Art: could rely on implementation feedback 16:49:01 Rick: evidence for using 'normal' is not strong 16:49:21 RESOLUTION: Keep pressure range as speced, but listen for implementation feedback 16:50:24 shepazu: Can emulate pressure via surface area 16:50:40 shepazu: should we account for this? 16:51:33 Jacob: a UA could do this, and web site wouldn't notice. So would be hard to call this not compliant 16:51:58 shepazu: should we mention this as a note? 16:52:12 -??P20 16:52:26 -[Microsoft] 16:53:04 Jacob: don't want to go too far in specifying device behavior here 16:53:15 ACTION: barstow add doug's use case about varying touch pressure to v.next list 16:53:15 Created ACTION-8 - Add doug's use case about varying touch pressure to v.next list [on Arthur Barstow - due 2012-12-11]. 16:54:13 Topic: 20111 - Define compatibility mapping for touch events https://www.w3.org/Bugs/Public/show_bug.cgi?id=20111 16:57:47 Art: any objects to touch-events mapping being done in webevents WG instead of pointer events wG? 16:57:49 None 16:58:13 s/objects/objections 16:58:45 RESOLUTION: Touch-event mapping is out of scope for pointer events WG, will be handled by web events WG instead 16:59:15 ACTION: barstow work with Doug and Rick on defining Touch Events mapping in the Web Events WG 16:59:15 Created ACTION-9 - Work with Doug and Rick on defining Touch Events mapping in the Web Events WG [on Arthur Barstow - due 2012-12-11]. 16:59:40 Topic: 20112 - pointerenter and pointerleave events https://www.w3.org/Bugs/Public/show_bug.cgi?id=20112 16:59:53 Jacob: no opposition to adding to the spec, assuming it's the same definition as for mouse 17:00:00 Art: any objections? 17:00:37 RESOLUTION: Add pointeenter and pointerleave to spec using the same model as mouseenter and mouseleave 17:00:43 Art: extend to 90 minutes? 17:01:24 Rick:Jacob: hope/expect we won't have 90 minutes worth of bugs to discuss 17:01:31 Doug: would have conflict 17:01:55 Jacob: suggest we leave as is for at least December, and if we're building up a backlog we can revisit in new year 17:02:13 ... if we're active on the mailing list then we can cover more there 17:02:39 Topic: Pointer Events and Click; thread 17:02:53 Art: seems to have resolved, follow-up on list 17:02:58 Topic: any other business 17:03:05 Art: will have meeting next week, Doug will chair 17:03:49 Rick: I may not be able to make it next week 17:03:53 Doug: I will keep track 17:03:56 -Doug_Schepers 17:04:06 ... and let the list know if there's a meeting next week 17:04:09 -Matt_Brubeck 17:05:14 Jacob: what do we need to do to get Matt permission to help edit the PE spec? 17:05:28 Art: all members already have permission 17:05:55 Jacob: OK, I'll work with Matt to make him an editor 17:06:00 -Art_Barstow 17:06:01 -Olli_Pettay 17:06:01 - +1.519.513.aacc 17:06:04 - +1.770.402.aabb 17:06:05 -[Microsoft.a] 17:06:11 - +1.717.578.aaaa 17:06:12 RWC_PEWG()11:00AM has ended 17:06:12 Attendees were +1.717.578.aaaa, +1.770.402.aabb, Matt_Brubeck, Art_Barstow, Olli_Pettay, [Microsoft], +1.519.513.aacc, Doug_Schepers 17:06:18 RRSAgent, make minutes 17:06:18 I have made the request to generate http://www.w3.org/2012/12/04-pointerevents-minutes.html ArtB 17:06:36 np Art, a few more times and I may start to get better at it ;-) 17:06:39 RRSAgent, make log Public 17:06:59 rbyers - you are doing a GREAT job! 17:07:15 Scribe: Rick 17:07:20 RRSAgent, make minutes 17:07:20 I have made the request to generate http://www.w3.org/2012/12/04-pointerevents-minutes.html ArtB 17:07:24 Thank you Rick 17:07:25 Thanks 17:08:33 zakim, bye 17:08:33 Zakim has left #pointerevents 17:32:16 rrsagent, bye 17:32:16 I see 4 open action items saved in http://www.w3.org/2012/12/04-pointerevents-actions.rdf : 17:32:16 ACTION: Jacob prepare a FPWD and notify Art when it is ready (see http://www.w3.org/wiki/Webapps/SpecEditing) [1] 17:32:16 recorded in http://www.w3.org/2012/12/04-pointerevents-irc#T16-09-27 17:32:16 ACTION: barstow send Transition Request for FPWD of Pointer Events [2] 17:32:16 recorded in http://www.w3.org/2012/12/04-pointerevents-irc#T16-12-38 17:32:16 ACTION: barstow add doug's use case about varying touch pressure to v.next list [3] 17:32:16 recorded in http://www.w3.org/2012/12/04-pointerevents-irc#T16-53-15 17:32:16 ACTION: barstow work with Doug and Rick on defining Touch Events mapping in the Web Events WG [4] 17:32:16 recorded in http://www.w3.org/2012/12/04-pointerevents-irc#T16-59-15