20:53:54 RRSAgent has joined #indie-ui 20:53:54 logging to http://www.w3.org/2013/05/15-indie-ui-irc 20:53:56 RRSAgent, make logs public 20:53:56 Zakim has joined #indie-ui 20:53:58 Zakim, this will be INDIE 20:53:58 ok, trackbot; I see WAI_Indie()5:00PM scheduled to start in 7 minutes 20:53:59 Meeting: Independent User Interface Task Force Teleconference 20:53:59 Date: 15 May 2013 20:54:03 Meeting: IndieUI Task Force Teleconference 20:54:03 Chair: Janina_Sajka 20:54:03 agenda+ TPAC2013 https://www.w3.org/2013/11/TPAC/ 20:54:03 agenda+ Editor's Update 20:54:03 agenda+ Default Activation Event [See Below] 20:54:06 agenda+ user context properties [See Below] 20:54:08 agenda+ User Context Issues & Actions https://www.w3.org/WAI/IndieUI/track/products/3 20:54:11 agenda+ Events Issues & Actions https://www.w3.org/WAI/IndieUI/track/products/2 20:54:14 agenda+ Privacy and Security: The cases for exposing AT 20:54:17 agenda+ Renaming POR: Open Discussion 20:54:19 agenda+ Scribe for our Next Teleconference (on 30 May at 21:00Z) 20:54:22 agenda+ Be Done 20:57:11 WAI_Indie()5:00PM has now started 20:57:18 +??P0 20:57:58 andy has joined #indie-ui 20:58:33 +??P1 20:58:38 zakim, ??P1 is me 20:58:38 +janina; got it 20:59:24 zakim, who's on the phone? 20:59:24 On the phone I see ??P0, janina 20:59:27 jasonjgw has joined #indie-ui 21:00:03 zakim, ??P0 is Andy_Heath 21:00:03 +Andy_Heath; got it 21:00:18 jcraig has joined #indie-ui 21:00:37 +??P2 21:00:53 +[Apple] 21:01:01 Zakim, Apple has jcraigh 21:01:01 +jcraigh; got it 21:01:02 rich_ has joined #indie-ui 21:01:13 Zakim, jcraigh is jcraig 21:01:13 sorry, jcraig, I do not recognize a party named 'jcraigh' 21:01:38 Zakim, Apple has jcraig 21:01:38 +jcraig; got it 21:01:46 zakim, call cooper-mobile 21:01:46 ok, MichaelC; the call is being made 21:01:48 +Cooper 21:01:55 zakim, jcraigh has left Apple 21:01:55 MichaelC, I was not aware that jcraigh was in Apple 21:01:55 Zakim, who is on the call 21:01:57 I don't understand 'who is on the call', jcraig 21:02:00 + +1.412.901.aaaa 21:02:05 Zakim, who's here? 21:02:05 On the phone I see Andy_Heath, janina, ??P2 (muted), [Apple], Cooper, +1.412.901.aaaa 21:02:07 [Apple] has jcraig 21:02:07 On IRC I see rich_, jcraig, jasonjgw, andy, Zakim, RRSAgent, smaug, Lachy, janina, MichaelC, hober, trackbot 21:02:30 zakim, aaaa is Rich_Simpson 21:02:31 +Rich_Simpson; got it 21:02:48 zakim, ??P2 is Jason_White 21:02:48 +Jason_White; got it 21:03:20 richardschwerdtfeger has joined #indie-ui 21:04:46 zakim, take up item 1 21:04:46 agendum 1. "TPAC2013 https://www.w3.org/2013/11/TPAC/" taken up [from janina] 21:05:42 scribe: jcraig 21:05:59 JS: Nov 11-15 in Shenzhen China 21:06:11 IndieUI F2F will be that week 21:06:14 We'll try to have our meeting at TPAC for two days, 11-15 November. 21:06:22 zakim, next item 21:06:22 agendum 2. "Editor's Update" taken up [from janina] 21:06:33 scribe: jasonjgw 21:07:04 +[Apple.a] 21:07:07 what is the conference code/ 21:07:08 ? 21:07:09 Zakim, Apple.a has me 21:07:09 +hober; got it 21:07:15 agenda: http://lists.w3.org/Archives/Public/public-indie-ui/2013May/0019.html 21:07:19 Particularly the directional and linear focus requests. 21:07:19 The main question is that distributed to the list regarding edits to events spec. 21:07:30 it says 46343 is not valid! 21:07:34 that is the second time today 21:07:56 For how they are two events: directionalfocusrequest and linearfocusrequest that each will have a detectable focusType attribute in the Event object matching, for example, LINEAR_PREVIOUS, LINEAR_NEXT, DIR_EAST, DIR_SOUTHWEST, etc. 21:07:58 Hmmm, Rich, it seems to be an issue accepting DTMF, perhaps? 21:08:11 +[IPcaller] 21:08:51 The other variation would be to have each be a separate named event. For example, focuspreviousrequest, focusnextrequest, focuseastrequest, focussouthwestrequest, etc. I thought adding twelve events would be more confusing than adding two with parameters. 21:08:53 James notes the distinction between direction focus events (next, previous, first, last) reserved for maps or similar objects. For now we have DirectionalFocusRequest and LinearFocusRequest with a focus type. 21:09:21 The linear focus events are all individually named events. 21:09:27 Does this rest of the group agree with my assumption? If not, why? 21:09:38 q+ 21:09:39 Does the working group support this scheme? 21:09:54 ack r 21:10:32 q+ to say I think fewer events with parameters easier, and also easier to add parameters later if circumstances come up 21:10:47 Rich suggests adopting the same vocabulary that is under consideration for SVG Tiny 1.2. 21:10:47 q+ 21:10:48 ack m 21:10:49 MichaelC, you wanted to say I think fewer events with parameters easier, and also easier to add parameters later if circumstances come up 21:10:52 http://www.w3.org/TR/SVGTiny12/ 21:11:15 ack a 21:11:27 Michael thinks MMMMichael and Andy think there is more flexibility in having events as parameters. 21:12:18 http://www.w3.org/TR/SVGTiny12/interact.html#navigation 21:12:47 http://www.w3.org/TR/SVGTiny12/single-page.html#interact-navigation 21:13:39 James observes that it's similar to a CSS proposal, which has similar problems to tabindex. 21:14:39 SVG uses syntax nav-next="url(#Chan2Prog1)" 21:15:01 The CSS proposal was deleted from their spec recently, James notes. 21:15:56 q? 21:16:12 The issue raised by Rich, to clarify, is alignment of vocabulary. 21:16:46 No further editor's updates. 21:16:59 zakim, next item 21:16:59 agendum 3. "Default Activation Event" taken up [from See Below] 21:17:05 Nothing more from me except I have to read this section of the SVG spec now . ;-) 21:19:26 This agenda item is postponed for now. 21:19:33 zakim, next item 21:19:33 agendum 4. "user context properties" taken up [from See Below] 21:19:46 Action-50? 21:19:46 ACTION-50 -- James Craig to prepare a list of user context properties that might be able to be covered by media queries -- due 2013-04-17 -- PENDINGREVIEW 21:19:46 http://www.w3.org/WAI/IndieUI/track/actions/50 21:20:36 CSS Conditionals 21:20:41 CSS Media Features 21:20:52 James: media queries seems a good opportunity to bring aspects of User Contexts into a well known and accepted format, namely CSS. CSS conditionals and media features are the relevant specs. 21:21:30 IndieUI and PF may wish to propose additional media queries. 21:22:02 Example: high contrast proposal. 21:22:22 Microsoft proposal for high contrast: 21:22:22 -ms-high-contrast: active | black-on-white | white-on-black | none; 21:22:45 My proposal variant: 21:22:46 display-colors-inverted: inverted | off; 21:22:46 display-contrast: ; 21:23:11 display-increase-contrast: 100%; may be equivalent to -ms-high-contrast: active; 21:23:12 display-increase-contrast: 0%; may be equivalent to -ms-high-contrast: none; 21:23:41 As a variant, James proposed two properties: colours inverted and a contrast percentage value. 21:23:59 @media (display-colors-inverted: inverted) { img, video { filter: invert(100%); } } 21:25:42 Discussion of contrast settings on different operating systems. 21:26:11 base-color 21:26:12 base-background-color 21:26:13 base-font-size 21:26:15 base-letter-spacing 21:26:16 base-line-height 21:26:18 base-word-spacing 21:26:19 display-colors-inverted 21:26:20 display-contrast-increased 21:26:21 minimum-font-size 21:26:42 James suggests, in answer to a question, that a joint IndieUI/PF position would be the best way to establish a proposal to extend the media queries supported in CSS. 21:28:17 James further clarifies that when relevant changes occur, so do the results of the media queries and hence the style applied to the document. 21:29:08 James suggests preparing a draft for CSS wg to review. 21:31:15 DiscussionTTTThe group notes a need to obtain input regarding different operating systems (Android, Linux and others). 21:31:33 +[IPcaller] 21:32:18 RS: Check with Google platforms and Linux to make sure this list covers other platforms besides Windows, Mac, and iOS. 21:32:28 https://www.w3.org/WAI/IndieUI/track/actions/50 21:36:56 zakim, take up item 3 21:36:56 agendum 3. "Default Activation Event" taken up [from See Below via janina] 21:39:09 q+ to ask if equivalent of "click" is sent in default framework controls 21:39:20 Eitan notes that some Firefox OS applications do not listen for click events, but only for low-level touch events. The system listens for touch events, not click. 21:40:19 Zakim, who is noisy? 21:40:33 jcraig, listening for 10 seconds I could not identify any sounds 21:40:48 He supports James' proposal that click still be used, but when an object is not activated this way, an IndieUI focus event should be available and used. 21:41:42 ack me 21:41:42 jcraig, you wanted to ask if equivalent of "click" is sent in default framework controls 21:41:52 -janina 21:43:06 James suggests that if a higher-level UI framework is being proposed, click could still be used as a default activation event (simulated rather than driven by mouse hardware in the touch screen case). 21:45:10 Eitan notes that there isn't a common framework at this stage. There are difficulties in determining when a click event has to be simulated. 21:45:44 James agrees there is no definition of what constitutes a "click", i.e., on what circumstances the event is to be simulated/dispatched. This needs to be defined per operating system. 21:46:47 James notes that the DOM wg considers click an abstract activation event; it is named "click" purely for historical reasons. 21:48:18 James proposes a secondary activation event request to be used in limited circumstances, with a strong note that the (abstract) click event defined in DOM should be used where possible. 21:49:09 q+ to ask how a