21:00:23 RRSAgent has joined #svg 21:00:23 logging to http://www.w3.org/2013/02/28-svg-irc 21:00:23 cabanier: that is what I meant :P 21:00:25 RRSAgent, make logs public 21:00:25 Zakim has joined #svg 21:00:27 Zakim, this will be GA_SVGWG 21:00:27 ok, trackbot, I see GA_SVGWG(SVG1)4:00PM already started 21:00:28 Meeting: SVG Working Group Teleconference 21:00:28 Date: 28 February 2013 21:00:32 cabanier: I am 21:00:38 cabanier: but no one else :P 21:00:56 +Doug_Schepers 21:01:25 +[IPcaller] 21:01:37 Zakim, [IP is me 21:01:37 +ed; got it 21:02:00 nikos_ has joined #svg 21:02:51 +cabanier 21:03:16 Agenda: http://lists.w3.org/Archives/Public/public-svg-wg/2013JanMar/0061.html 21:03:33 +??P4 21:03:55 Zakim, +??p4 is me 21:03:55 sorry, nikos_, I do not recognize a party named '+??p4' 21:04:02 Zakim, +?? is me 21:04:02 sorry, nikos_, I do not recognize a party named '+??' 21:04:24 Zakim, ?? is me 21:04:24 +nikos_; got it 21:04:46 Zakim, aaaa is me 21:04:46 +krit; got it 21:06:23 + +33.9.53.77.aabb 21:07:25 Zakim, pick a scribe? 21:07:25 I don't understand your question, ed. 21:07:29 shanestephens has joined #svg 21:07:41 Zakim, pick a victim 21:07:41 Not knowing who is chairing or who scribed recently, I propose Doug_Schepers 21:08:14 scribenick: cabanier 21:08:24 Zakim, +33 is me 21:08:24 +Tav; got it 21:08:29 topic: publishing SVG2 21:08:45 ed: I sent my feedback 21:09:01 … there are 'missing reference, couldn't find, etc" 21:09:07 … it would be nice to fix that 21:09:20 krit: that's a requirement for publishing 21:09:42 ed: maybe somone should go through and see what problems there are 21:10:01 … unless anyone objects, we should publish 21:10:09 nikos: I can take an action 21:10:12 ed: great 21:10:24 s/great/ok/ 21:10:37 action: Nikos to validate the spec for lose references 21:10:37 Created ACTION-3466 - Validate the spec for lose references [on Nikos Andronikos - due 2013-03-07]. 21:10:49 see http://lists.w3.org/Archives/Public/public-svg-wg/2013JanMar/0058.html 21:11:18 ed: we need to change the appendix from svg 1.1 21:11:27 … should we keep it? 21:11:40 krit: I think we already resolved to do it the same as css 21:11:57 ed: OK. we need another action to see what needs to be listed 21:13:18 action: Nikos to see what needs to be done to update the appendix 21:13:19 Created ACTION-3467 - See what needs to be done to update the appendix [on Nikos Andronikos - due 2013-03-07]. 21:13:33 krit: you just need to check what needs to be modified 21:13:48 ed: can we resolve to publish once these actions are done? 21:14:28 resolution: The WG will publish the spec once action 3466 and 3467 are done 21:15:04 topic: referencing the HTML spec 21:15:15 ed: is rich on the call? 21:15:28 … if he want to clarify the topic 21:15:38 … I was replying to his email 21:16:06 krit: the HTML spec has things that we want to reference 21:16:39 … it's not in the HTML5 spec so can we reference the WhatWG spec 21:16:56 cabanier: did you look at the 5.1 spec? 21:17:09 shepazu: what are you looking for? 21:17:34 http://www.w3.org/TR/2006/WD-Window-20060407/ 21:17:37 krit: the section that refers to window 21:18:13 ed: that is just an informative reference from the svg spec 21:18:25 krit: why not normative? 21:18:40 ed: we didn't want a window object in 1.1 21:18:47 http://www.w3.org/TR/2012/CR-html5-20121217/browsers.html#the-window-object 21:19:10 http://www.w3.org/html/wg/drafts/html/master/browsers.html#the-window-object 21:19:19 s/ we didn't want/ there was no / 21:19:59 http://www.w3.org/TR/SVG11/struct.html#InterfaceGetSVGDocument 21:20:52 ed: is there anything there in the whatwg that is not in the html5 spec 21:21:09 krit: I don't think so 21:21:36 … I will change the reference from the window spec to HTML5 21:22:13 action: krit to update the spec and change the reference from the window spec to the HTML5 spec 21:22:13 Created ACTION-3468 - Update the spec and change the reference from the window spec to the HTML5 spec [on Dirk Schulze - due 2013-03-07]. 21:22:36 http://lists.w3.org/Archives/Public/public-svg-wg/2013JanMar/0055.html 21:23:38 ed: should we go over this list? 21:23:52 cabanier: maybe we should wait until he calls in 21:24:02 krit: or we can discuss it on the mailing list? 21:24:17 shepazu: can we discuss it on www-svg? 21:24:20 ed: sure 21:24:28 topic: text on path overflowing 21:24:32 http://lists.w3.org/Archives/Public/www-svg/2013Feb/0053.html 21:25:03 krit: text now gets clipped. sometimes that's what you want but sometimes not 21:25:15 … but I agree with Erik's reply on the list 21:25:26 ed: should we define how the text overflows? 21:25:39 krit: maybe. but no magic 21:25:54 ed: is that wrapping? 21:26:10 krit: yes. no estimating like continuing an arc 21:26:38 ed: for me, it would be fine to tie the end together. Just restart from the beginning 21:26:51 … that would be a simple model 21:27:12 krit: there are use case that the text just continues 21:27:46 … if we take the last angle and continue in a straight line 21:27:58 … which seemed what he asked for 21:28:09 … but your suggestion sounds good too 21:28:25 ed: like a 'wrapped' keyword 21:28:47 … but I don't know if it makes sense to extend text overflow like this 21:28:58 krit: I have no strong opinion on this 21:29:51 ed: I think it would be fine to have a workaround for this. 21:30:22 … his email states that he already is fixing it by extending the path. So I think it's OK to defer 21:30:30 krit: that would be fine for me as wel 21:31:06 resolution: defer text on a path extension to a later date 21:31:12 * sure. thanks! * 21:31:21 scribenick: shanestephens 21:31:36 scribenick: shepazu 21:31:56 Topic: Whitespace at end of textpath 21:32:27 https://bugzilla.mozilla.org/show_bug.cgi?id=641187 21:32:31 ed: not sure how this is affected by changes we're making to whitespace, propose to defer until we know more about how CSS whitespace will affect us 21:34:27 Issue: figure out how to deal with trailing whitespace in textpath per https://bugzilla.mozilla.org/show_bug.cgi?id=641187 21:34:27 Created ISSUE-2446 - Figure out how to deal with trailing whitespace in textpath per https://bugzilla.mozilla.org/show_bug.cgi?id=641187; please complete additional details at . 21:34:57 https://www.w3.org/Bugs/Public/enter_bug.cgi?product=SVG 21:35:23 Topic: html element in SVG 21:36:02 glenn has joined #svg 21:36:37 dirk: discussed this at F2F, also talking about it in WebKit 21:36:54 http://www.w3.org/TR/SVG/interact.html#PointerEventsProperty 21:37:24 dirk: pointer-events property started in SVG, implemented for CSS+HTML 21:37:31 … dropped from CSS UI 3 21:37:40 q+ 21:37:42 s/dirk/krit/g 21:38:20 ed: you want to add this to SVG 2? 21:39:01 krit: pointer-events in all browsers, but Firefox and WebKituse 'auto' as initial value 21:39:32 … I propose for SVG that we allow 'auto' as value and use as initial value 21:42:03 shepazu: I propose that this be done in CSS, and that it should be part of a larger hit-testing spec… let's not define it in SVG anymore 21:42:11 krit: fine by me 21:42:53 http://www.w3.org/TR/SVGTiny12/interact.html#PointerEventsProperty 21:43:04 ed: sound fine, as long as we add the SVG Tiny 1.2 property keyword 'bounding-box' 21:43:25 s/'bounding-box'/'boundingBox'/ 21:44:36 shepazu: could also have alpha-based hit-testing, for games 21:44:47 krit: talked about this in WebKit, expensive for us 21:45:24 shepazu: more difficult still for people doing it in JS 21:45:31 krit: just do it in canvas 21:45:42 shepazu: then why optimize that way in the implementation? 21:45:59 s/why optimize/why not optimize/ 21:46:04 krit: sure, why not? 21:46:43 Action: propose hit-testing/pointer-events spec to CSS WG 21:46:43 Error finding 'propose'. You can review and register nicknames at . 21:47:04 Action: shepazu to propose hit-testing/pointer-events spec to CSS WG 21:47:05 Created ACTION-3469 - Propose hit-testing/pointer-events spec to CSS WG [on Doug Schepers - due 2013-03-07]. 21:48:11 ..html..content.. 21:48:22 must have boundaries 21:48:28 —> SVGHTMLElement 21:48:48 shepazu: did we resolve around without ? 21:49:04 ed: we'd need x/y on 21:49:47 krit: Hixie proposed this, and said it's up to SVG WG 21:49:59 also width/height 21:50:00 -Tav 21:50:49 +Tav 21:50:56 krit: the tag inside the SVG NS would be an SVG element 21:51:45 It would be more like the HTMLBodyElement 21:52:42 shepazu: let's take it to www-svg 21:53:23 ADJOURNED 21:53:25 -cabanier 21:53:29 -Tav 21:53:30 -krit 21:53:30 -ed 21:53:30 trackbot, end telcon 21:53:30 Zakim, list attendees 21:53:31 As of this point the attendees have been +1.415.308.aaaa, Doug_Schepers, [IPcaller], ed, cabanier, nikos_, krit, +33.9.53.77.aabb, Tav 21:53:34 -nikos_ 21:53:36 -Doug_Schepers 21:53:38 GA_SVGWG(SVG1)4:00PM has ended 21:53:38 Attendees were +1.415.308.aaaa, Doug_Schepers, [IPcaller], ed, cabanier, nikos_, krit, +33.9.53.77.aabb, Tav 21:53:38 RRSAgent, please draft minutes 21:53:39 I have made the request to generate http://www.w3.org/2013/02/28-svg-minutes.html trackbot 21:53:39 RRSAgent, bye 21:53:39 I see 5 open action items saved in http://www.w3.org/2013/02/28-svg-actions.rdf : 21:53:39 ACTION: Nikos to validate the spec for lose references [1] 21:53:39 recorded in http://www.w3.org/2013/02/28-svg-irc#T21-10-37 21:53:39 ACTION: Nikos to see what needs to be done to update the appendix [2] 21:53:39 recorded in http://www.w3.org/2013/02/28-svg-irc#T21-13-18 21:53:39 ACTION: krit to update the spec and change the reference from the window spec to the HTML5 spec [3] 21:53:39 recorded in http://www.w3.org/2013/02/28-svg-irc#T21-22-13 21:53:39 ACTION: propose hit-testing/pointer-events spec to CSS WG [4] 21:53:39 recorded in http://www.w3.org/2013/02/28-svg-irc#T21-46-43 21:53:39 ACTION: shepazu to propose hit-testing/pointer-events spec to CSS WG [5] 21:53:39 recorded in http://www.w3.org/2013/02/28-svg-irc#T21-47-04