20:27:41 RRSAgent has joined #svg 20:27:41 logging to http://www.w3.org/2015/04/16-svg-irc 20:27:43 RRSAgent, make logs public 20:27:43 Zakim has joined #svg 20:27:45 Zakim, this will be GA_SVGWG 20:27:45 ok, trackbot; I see GA_SVGWG()4:30PM scheduled to start in 3 minutes 20:27:46 Meeting: SVG Working Group Teleconference 20:27:46 Date: 16 April 2015 20:28:01 AmeliaBR has joined #svg 20:28:08 Agenda: https://lists.w3.org/Archives/Public/www-svg/2015Apr/0010.html 20:28:15 GA_SVGWG()4:30PM has now started 20:28:22 +Doug_Schepers 20:30:07 +[IPcaller] 20:30:42 +??P0 20:30:53 Zakim, [IP is me 20:30:53 +ed; got it 20:30:53 zakim, ??P0 is me 20:30:54 +AmeliaBR; got it 20:31:00 +??P3 20:31:15 smailus has joined #svg 20:31:30 zakim, ??P3 is me 20:31:30 +stakagi; got it 20:31:44 +Thomas_Smailus 20:33:20 ChrisLittle has joined #svg 20:36:08 afk for bio break 20:36:28 Zakim, pick a scribe 20:36:28 Not knowing who is chairing or who scribed recently, I propose ed 20:36:52 scribeNick: ed 20:37:59 topic: stroke-dasharray="0" 20:38:06 https://lists.w3.org/Archives/Public/www-svg/2015Apr/0001.html 20:38:31 ABR: there was a inconsistency between firefox and the other browsers when you had stroke-dasharray=0 20:38:36 +[IPcaller] 20:38:39 ... comes down to some unclear prose 20:39:15 ... spec said should be treated as a value of none was specified, but it was unclear where that meant for the stroke or for stroke-dasharray 20:39:30 +[Microsoft] 20:39:32 ... 20:39:52 ... so still draw the stroke, but don't dash it 20:40:05 ... Robert Longson was happy with the proposed wording 20:40:16 ... so, can we resolve on doing that clarification? 20:41:10 All: yes 20:41:49 ACTION: AmeliaBR to clarify the wording around stroke-dasharray=0 to say that that means draw the stroke but don't dash it 20:41:49 Created ACTION-3777 - Clarify the wording around stroke-dasharray=0 to say that that means draw the stroke but don't dash it [on Amelia Bellamy-Royds - due 2015-04-23]. 20:42:11 topic: meeting at TPAC? 20:42:20 DS: it's in Sapporo, Japan 20:42:43 ... we need to let the planners know if SVGWG is meeting, by apr 30 20:42:44 +Tav 20:43:05 ... and we don't want to meet with days overlapping with CSS 20:43:13 ... who here will attend? 20:43:39 Rossen: we're going to have somebody there, probably me and maybe bogdan 20:43:45 ... will attend CSS too 20:44:04 ED: will go if SVG is meeting 20:44:12 DS: will go 20:44:20 BB: I expect I'll go 20:44:25 I'm attending. 20:44:42 will go 20:44:43 Tav: I'll probably not go, too expensive for two days 20:45:30 TPAC is 26-30 Oct 2015 20:45:44 DS: does anyone think we shouldn't meet at tpac? 20:45:50 20:46:08 DS: thu-fri is typically when svg meets 20:46:20 ... might be a bit crowded, but no problem 20:46:47 ... assuming people in the group will attend CSS too, so we shouldn't have overlap 20:46:56 Rossen: maybe FXTF too? 20:47:12 DS: will we have one? 20:47:24 Rossen: sure, if there are things to discuss 20:47:32 ... assuming it'll happen on wednesday 20:47:47 ... or perhaps take some time from the css or svg meeting 20:48:37 ACTION: ed to respond to the TPAC organizers saying SVG will meet at TPAC 2015 20:48:37 Created ACTION-3778 - Respond to the tpac organizers saying svg will meet at tpac 2015 [on Erik Dahlström - due 2015-04-23]. 20:49:18 topic: SVG 2 open issue discussion 20:49:23 -Doug_Schepers 20:49:24 https://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Chapter_Assessment 20:49:46 +Doug_Schepers 20:49:48 -Doug_Schepers 20:50:21 +Doug_Schepers 20:50:38 Rossen: orthogonal question, some chapter are assigned to Dirk, anyone know if he's still active in the group, and if he's going to work on the things he's assigned? 20:50:56 ... if not, we should divvy up the chapters on other ppl 20:51:16 DS: he hasn't been on the calls recently 20:51:25 AmeliaBR: he's been active on the list 20:51:34 Rossen: ok, moving on to the issues then 20:52:48 Topic: chapter 19, extensibility 20:53:41 https://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Chapter_Assessment#Extensibility_.28Rossen.29 20:53:49 https://svgwg.org/svg2-draft/extend.html#issue2 20:54:08 AmeliaBR: issue 2 and 3, it's not specific to foreignObject 20:54:15 ... going to come up all over the svg dom 20:54:31 -Doug_Schepers 20:54:49 ... what to do with the attributes we turned into presentation attributes, has to be done consistently across the board 20:54:53 Rossen: sounds good 20:54:54 +Doug_Schepers 20:55:08 ... I believe the issues were raised in the wrong part of the spec 20:55:15 ... not specific to FO itself 20:55:47 ... I woudln't expect anythign special here 20:56:04 BB: the only thing that might be different 20:56:18 ... maybe because it's not used so much we could make them domstrings 20:56:33 AmeliaBR: I'd advise caution there 20:56:43 ... ppl also expect things to work the same way 20:57:02 BB: ppl probably don't use animVal for width and height on a FO 20:57:47 Rossen: but what makes FO special here? 20:58:19 BB: if the APIs aren't used (much) it'd be nicer to be able to simplify things 20:59:37 ED: I'm fine with moving this to whatever chapter needs to deal with this, I agree that the extensibility chapter shouldn't do it alone 20:59:43 q+ 21:00:38 Rossen: fine with moving it to the proper chapter 21:01:00 DS: might be useful to raise an issue in ext chapter about other ways to embed html 21:01:13 ... we should raise such an issue here as a placeholder 21:01:41 AmeliaBR: iframe and foreignObject have similarites 21:02:05 DS: maybe those two chapters should simply be merged 21:02:26 AmeliaBR: there's a difference in linking vs embedding, but merging might make sense 21:02:40 s/similarites/similarities 21:02:53 DS: I wouldn't look for FO in an extensibility chapter 21:03:05 Rossen: I can merge those chapters if that's what we want to do 21:03:40 ... I see that in embedded content chapter, there are other examples of x,y,width,height presentation attributes 21:05:10 ACTION: Rossen to merge the embedded content and extensibility chapters (removing the ext chapter) 21:05:10 Created ACTION-3779 - Merge the embedded content and extensibility chapters (removing the ext chapter) [on Rossen Atanassov - due 2015-04-23]. 21:05:44 topic: animations chapter 21:05:54 Rossen: three issues needing discussion 21:06:06 https://svgwg.org/svg2-draft/animate.html#issue2 21:07:51 AmeliaBR: what is #xC? 21:07:58 Tav: it's form feed 21:08:05 AmeliaBR: consistency is good 21:09:21 ED: so, I did some changes to the types chapter to align what is considered "whitespace" across svg, html and css 21:09:39 ... it was previously referenced from here (I think) 21:09:58 ... the types chapter is referencing css now, so automatically is aligned with that 21:10:08 ... I think the animations chapter should use the same definition of whitespace 21:12:20 Rossen: ok, sounds good, point to css definition of whitespace 21:13:08 RESOLUTION: align what is considered whitespace in animations chapter with CSS, by referencing css' definition of whitespace 21:13:54 ACTION: Rossen to reference CSS' definition of whitespace for the S production in the animations chapter (issue 2) 21:13:54 Created ACTION-3780 - Reference css' definition of whitespace for the s production in the animations chapter (issue 2) [on Rossen Atanassov - due 2015-04-23]. 21:13:59 https://svgwg.org/svg2-draft/animate.html#issue8 21:14:34 Rossen: this is unclear to me 21:14:46 ... should we reference the transform property, or what is this about? 21:14:54 The CSS definition of whitespace is at http://dev.w3.org/csswg/css-syntax/#whitespace 21:15:15 (Note that u+000c is processed out during preprocessing, and so doesn't show up in the definition explicitly. There's a note covering this.) 21:15:18 BB: not sure who added this, but maybe that you can use the regular animate element to animate transform 21:16:32 AmeliaBR: I think the immidiate issue is to just change the text, so that animateTransform refers to the transform style property as well as the attribute 21:17:20 BB: I'm adressing this chapter top-to-bottom, so not sure we need to talk about this yet 21:17:32 Rossen: the rest are mostly editorial 21:18:09 BB: I've been working on this chapter 21:18:42 https://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Chapter_Assessment#Animation_.28Rossen.29 21:18:42 Rossen: the reason why the animation chapter had my name next to it, happy to give it back to you brian 21:20:15 ... so for issue 8, add the reference to transform property and then deprecate? 21:20:30 https://svgwg.org/svg2-draft/animate.html#issue8 21:21:07 BB: just needs to be updated to talk about the transform property 21:21:40 https://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Chapter_Assessment#Animation_.28Brian.29 21:21:42 Rossen: ok, I did reflect this in the chapter assessment, and assigned Brian the animation chapter 21:22:40 topic: deprecating xlink:href 21:22:54 BB: there are three questions I have around this 21:23:00 ... first, animated interfaces 21:23:13 ... since we're not going ahead with heycam's new dom 21:23:36 ... if that's the case, then the href IDL attributes point to an SVGAnimatedString 21:23:42 ... and if they're not used much 21:23:51 ... to replace them with plain domstring 21:25:24 ED: I landed a patch in blink today for measuring the usage of href.baseVal and href.animVal, we'll have to wait a bit for the results 21:25:44 Q: What interface makes xlink:href available as an animated string? 21:25:47 BB: For ,