20:59:27 RRSAgent has joined #svg 20:59:27 logging to http://www.w3.org/2013/03/21-svg-irc 20:59:29 RRSAgent, make logs public 20:59:29 Zakim has joined #svg 20:59:31 Zakim, this will be GA_SVGWG 20:59:31 ok, trackbot, I see GA_SVGWG(SVG1)5:00PM already started 20:59:32 Meeting: SVG Working Group Teleconference 20:59:32 Date: 21 March 2013 20:59:34 ChrisL has joined #svg 20:59:57 rrsagent, here 20:59:57 See http://www.w3.org/2013/03/21-svg-irc#T20-59-57 21:00:09 +[IPcaller] 21:00:22 Zakim, [IP is me 21:00:22 +ed; got it 21:01:11 Agenda: http://lists.w3.org/Archives/Public/public-svg-wg/2013JanMar/0074.html 21:01:31 + +61.2.980.5.aabb 21:01:37 Zakim, +61.2 is me 21:01:37 +nikos; got it 21:01:46 +Rich_Schwerdtfeger 21:02:20 +ChrisL 21:02:46 yay, a new telcon time that isn't 11pm 21:03:02 glenn has joined #svg 21:04:03 scribenick: nikos 21:04:18 Topic: SVG 2 status 21:04:34 status - SVG2 full of broken links 21:04:36 http://lists.w3.org/Archives/Public/public-svg-wg/2013JanMar/0073.html 21:04:40 ed: There are some problems with broken links 21:05:00 ed: I took a look at filters, it seems we are referencing the ED of the compositing spec 21:05:44 ed: Some of the specs we are referencing are quite old. Will we be publishing new versions of them any time soon? 21:06:04 krit: for Filter Effects I'm waiting on feedback on the security model 21:06:53 ... For compositing we have problems with stacking contexts to resolve 21:07:24 ChrisL: I'd like to see new versions for specs that have changed. It's ok to point to the old version if there haven't been any changes 21:07:43 krit: I'd like to wait 2-3 weeks for Filter Effects. I'd like feedback from Robert O'Callaghan 21:08:09 nikos: We should check with Rik for Compositing and Blending 21:08:28 ed: For the masking links, I think we need to go through definitions.xml and remove things that are moved to the new spec 21:08:45 ... and setup something like definitions-filters.xml for anything filter related 21:08:54 ... we should do likewise for compositing and masks 21:09:21 krit: Do you mean we port these files from the other specs to SVG 2? 21:09:42 ChrisL: The xml just defines the links 21:10:04 ed: We can specify the base URL easily in the definition 21:10:12 so one edit updates all the links that are generated 21:10:29 s/definition/publish.xml file definition/ 21:11:19 krit: I've updated the file in the filter effects repository, How do I bring that across to SVG 2? 21:12:16 ed: we need to make sure the definitions file is correct for the last published working draft, as links will change 21:12:30 ... we should point to a particular WD 21:13:38 action: Erik to fix the definition XML file for filter effects in SVG 2. Point to a specific published version. 21:13:38 Created ACTION-3476 - Fix the definition XML file for filter effects in SVG 2. Point to a specific published version. [on Erik Dahlström - due 2013-03-28]. 21:13:55 action: Dirk to fix the definition XML file for masking in SVG 2. Point to a specific published version. 21:13:55 Created ACTION-3477 - Fix the definition XML file for masking in SVG 2. Point to a specific published version. [on Dirk Schulze - due 2013-03-28]. 21:14:15 action: Nikos to fix the definition XML file for compositing and blending in SVG 2. Point to a specific published version. 21:14:15 Created ACTION-3478 - Fix the definition XML file for compositing and blending in SVG 2. Point to a specific published version. [on Nikos Andronikos - due 2013-03-28]. 21:14:30 glenn has joined #svg 21:15:46 ed: So Chris, you'll do the publication when everything is fixed? 21:15:56 ChrisL: yes, I may need to get someone else to build if my system isn't ready 21:16:33 glenn_ has joined #svg 21:17:01 Topic: Referencing the HTML spec 21:17:06 http://lists.w3.org/Archives/Public/public-svg-wg/2013JanMar/0055.html 21:17:21 richardschwerdtfeger: We started looking at this list and got up to item 5 21:17:36 ... looking at focus navigation in SVG. I'm trying to follow the same navigation sequencing that is in HTML 5 21:17:45 ... they refer to how to parse the browsing context 21:18:00 ... in terms of the definition of the browsing context. Does anyone have reservations on me referencing the HTML 5 spec ? 21:18:02 http://www.w3.org/html/wg/drafts/html/CR/browsers.html#windows 21:18:13 krit: don't you already reference HTML 5? 21:18:18 richardschwerdtfeger: not for browsing context 21:18:33 http://www.w3.org/html/wg/drafts/html/CR/editing.html#sequential-focus-navigation-and-the-tabindex-attribute 21:19:00 richardschwerdtfeger: so for consistency, I just refer to that definition 21:19:18 krit: do we define a window proxy object in SVG? 21:19:23 richardschwerdtfeger: not sure, I don't think so 21:19:32 ... we probably will have to 21:19:37 krit: each browsing context requires one 21:20:05 richardschwerdtfeger: do we have a window object in SVG? 21:20:06 krit: yes 21:20:17 richardschwerdtfeger: might not be an issue then 21:20:27 ... that makes sense 21:20:42 krit: is window defined in HTML? 21:20:45 richardschwerdtfeger: yes 21:20:51 http://www.w3.org/html/wg/drafts/html/CR/browsers.html#window 21:20:51 krit: SVG has a window object too? 21:20:55 ed: yes 21:21:08 richardschwerdtfeger: I don't know that we have all the same methods 21:21:17 krit: we don't have scrolling 21:21:42 http://www.w3.org/TR/SVGTiny12/svgudom.html#dom__Window 21:21:42 krit: I think it's fine 21:21:59 ed: I'm not sure that SVG 1.1 has a window definition but SVG 1.2 does 21:22:25 ChrisL: SVG 1.2 tiny was the first W3C to define a window object, but it's probably quite old and HTML5's is more up to date 21:22:39 richardschwerdtfeger: moving on to 6 then 21:22:56 ... we need focus and hasFocus from HTMLElement 21:23:06 ... should we request HTML move them up to the Element object? 21:23:12 ... what do you guys prefer we do here? 21:23:21 krit: might be easier to just put it on SVGElement as well 21:23:50 richardschwerdtfeger: Number 7 21:24:02 ... tabIndex is a global attribute in HTML so can apply to any element e.g. the title element 21:24:35 title {display: block; position: fixed } 21:25:20 ChrisL: it's easy in HTML to say that things in head don't get rendered 21:25:31 ... but we have a bunch of stuff that doesn't render by itself e.g. gradients 21:26:10 richardschwerdtfeger: my recommendation is that we apply it to all elements but we stipulate that an element is focusable if the UAs default behaviour is to allow it focusable or it has tabindex 21:26:43 ... should we list the elements that don't apply? 21:26:58 krit: what about references via use? 21:27:07 ed: could be tricky, do you get one per use or one per definition? 21:27:17 ChrisL: it's assuming one element produces one rendering and that's not the case here 21:27:25 ... we've covered the case with zero renderings, but not multiple 21:27:31 ... it's the instances that can be focused 21:27:46 richardschwerdtfeger: so we need to modify the definition? 21:27:49 ChrisL: I think so 21:28:18 ... I would need to think about it and take a look at what you have already. Can we do it via email? 21:28:28 ... it probably needs to be made to apply to HTML as well 21:28:40 richardschwerdtfeger: so the general definition is ok, but we need to deal with multiple instances 21:28:44 richardschwerdtfeger: Number 8 21:29:21 ... part of what is needed for sequential flow navigation is to deal with browsing contexts 21:29:49 richardschwerdtfeger: it doesn't sound like people disagree that we would refer to the definitions? 21:30:05 s/people disagree/people don't disagree 21:30:21 ... I'm trying not to redefine things if possible 21:30:22 zakim, who is on the phone? 21:30:22 On the phone I see +1.425.373.aaaa, Krit, ed, nikos, Rich_Schwerdtfeger, ChrisL 21:30:52 ed: Haven't heard any disagreement so I think it's fine 21:31:03 richardschwerdtfeger: we have some inconsistencies in naming like blur and focus out 21:31:25 ... This is number 9 21:31:39 ... do people have thoughts on mapping between the two? 21:31:47 ... browsers handle it but I'd like to hear your thoughts 21:32:02 glenn has joined #svg 21:32:03 ChrisL: When it was first proposed it was called blur and then it changed and then changed back 21:32:14 ... I vaguely remember firing multiple events, but that's hacky 21:33:21 ... how do the HTML browsers handle it? are they consistent? 21:33:21 richardschwerdtfeger: multiple events I think 21:33:21 ed: yes that's correct 21:33:21 ... since SVG 1.1 didn't have blur and focus I don't think the browsers have them in an SVG context 21:33:21 krit: my experience is that inline SVG does 21:33:35 richardschwerdtfeger: for backward compatibility we will need focusout 21:33:49 ... do we say you only register one handler? 21:33:54 ... or do we say blur and focusout are equivalent? 21:34:00 ... or do we tell browsers to generate both events? 21:34:23 ed: the question is how backward compatibility it would need to be as I don't think browsers implement this in SVG 21:34:28 ... there may not be much content using it 21:34:50 richardschwerdtfeger: the only SVG element that it might apply to currently is anchor? 21:34:59 ed: animation and editable text in Tiny 1.2 as well 21:35:19 s/only SVG element /only SVG 1.1 element 21:35:46 richardschwerdtfeger: so it sounds like we will have a backward compatibility issue if we don't have both events 21:35:58 ed: I don't think it would be a big deal but it might make sense to investigate 21:36:04 ... there is probably some content, but not much 21:37:06 richardschwerdtfeger: we will use the HTML names vs the exiting SVG names. So will use blur rather than focusout in the SVG 2 spec 21:37:14 ed: might be safer to deprecate 21:37:37 richardschwerdtfeger: ok we will deprecate the old names and adopt the HTML 5 naming conventions 21:37:42 ... Number 10 21:38:20 ... do we change the document or do we do something specific in SVG? 21:38:46 ... do we want our own version of document or have the HTML 5 document object change? 21:39:06 krit1 has joined #svg 21:39:09 ed: there are only a few things we have on the SVG document that are in conflict with the HTML 5 document 21:39:14 ... I think the HTML 5 spec documents them 21:39:35 ... I think for the most part, they are more or less the same. SVG document is a subset 21:39:44 ... the only thing the SVG document adds is the root element 21:39:59 richardschwerdtfeger: the HTML one has a lot of stuff we wouldn't implement 21:40:06 ed: do you want to import from the HTML element? 21:40:15 s/element/document/ 21:40:51 richardschwerdtfeger: we need active element, we asked Anna if he would put it in DOM 4 (we reference DOM 4). He said no, he'd rather we adopt the HTML 5 document interface 21:41:01 http://lists.w3.org/Archives/Public/public-svg-wg/2013JanMar/0072.html 21:41:19 ... last time we discussed it, there was some reluctance to do that 21:41:45 ... this carries over into the next agenda item 21:42:27 ed: Dirk you thing it should be on the document interface? 21:42:32 krit1: it feels more natural 21:42:43 ... we inherit from HTML document in webkit 21:43:04 ed: I don't have a strong opinion where it goes as long as it's there 21:43:22 richardschwerdtfeger: if we have the two together we'd use the HTML document, if you have standalone SVG what do you do? 21:43:27 ... not support some functions? or have a subset? 21:43:39 ... Anna's argument was that script developers want access to the entire set of APIs 21:43:51 ... but in a standalone environment I'm not sure what to do with that 21:44:05 ... Dirk you wanted to preserve the XML document object? 21:44:11 krit1: yes 21:44:44 ... I have a strong opinion on that, I'm not sure Mozilla would let SVG document inherit from HTML document 21:45:08 ... they want it on the DOM as well 21:45:43 richardschwerdtfeger: I will ask Boris 21:45:56 ... we can discuss next week if needed 21:46:00 -ChrisL 21:46:17 Topic: SVG font-face-src required in the schema but optional in the spec 21:46:20 http://www.w3.org/mid/CALvn5ECR4cPCgayiKOzGH5U5VZWxCx-bk1JdLSMxSuHG=6nqiA@mail.gmail.com 21:46:33 ed: I was wondering what we want to do with this 21:46:39 ... Chris replied and said the DTD is incorrect 21:46:41 ... I would agree 21:46:46 +ChrisL 21:47:06 ChrisL: I'll take an action to do the errata 21:47:10 ... and tell IPDF 21:47:40 action: Chris to write errata for ‘font-face-src’ 21:47:40 Created ACTION-3479 - Write errata for ‘font-face-src’ [on Chris Lilley - due 2013-03-28]. 21:47:47 have to drop 21:47:55 -Rich_Schwerdtfeger 21:48:22 Topic: Matrix specification editorship 21:48:35 krit1: Could Rik become co-editor of this? 21:48:57 s/Rik/Rik and I/ 21:49:21 ed: no objections? That's fine then 21:54:10 -ed 21:54:11 -ChrisL 21:54:12 - +1.425.373.aaaa 21:54:13 -nikos 21:54:13 -Krit 21:54:15 GA_SVGWG(SVG1)5:00PM has ended 21:54:15 Attendees were +1.425.373.aaaa, Krit, [IPcaller], ed, +61.2.980.5.aabb, nikos, Rich_Schwerdtfeger, ChrisL 21:54:35 RRSAgent, make minutes 21:54:35 I have made the request to generate http://www.w3.org/2013/03/21-svg-minutes.html nikos 21:54:43 thomassmailus has left #svg 22:16:13 glenn has joined #svg 22:49:07 birtles has joined #svg 22:52:11 shepazu has joined #svg 23:01:18 shanestephens has joined #svg 23:42:43 birtles has joined #svg 23:48:15 krit has joined #svg