19:31:46 RRSAgent has joined #svg 19:31:46 logging to http://www.w3.org/2008/12/18-svg-irc 19:31:48 RRSAgent, make logs public 19:31:48 Zakim has joined #svg 19:31:50 Zakim, this will be GA_SVGWG 19:31:50 ok, trackbot; I see GA_SVGWG()2:30PM scheduled to start now 19:31:51 Meeting: SVG Working Group Teleconference 19:31:51 Date: 18 December 2008 19:32:40 GA_SVGWG()2:30PM has now started 19:32:47 +??P0 19:32:53 Zakim, ?? is me 19:32:53 +ed; got it 19:33:04 ChrisL has joined #svg 19:33:40 +??P1 19:34:01 Zakim, ??P1 is me 19:34:01 +shepazu; got it 19:34:13 +ChrisL 19:35:37 +??P3 19:35:39 Zakim, ??P3 is me 19:35:39 +heycam; got it 19:38:13 19:38:45 +[IPcaller] 19:39:13 19:39:20 19:39:22 Zakim, [IP is me 19:39:22 +anthony; got it 19:42:34 Scribe: anthony 19:42:40 Chair: Erik 19:42:52 http://lists.w3.org/Archives/Public/www-svg/2008Dec/0049.html 19:43:03 Topic: Never-ending Clip Path Errata Item 19:43:23 ED: Pasted in a link to my question 19:43:37 ... if you have a nested SVG element that establishes a clipping viewport 19:43:48 ... you wouldn't expect to get mouse events outside that viewport 19:43:54 ... I think a group element would be kind of the same 19:44:05 19:44:28 ED: If you had that, then you say the SVG was a bit smaller and clipped the SVG a bit 19:44:34 19:44:46 ... I'd consider that to be similar to something like this 19:45:06 DS: I understand why you would expect that 19:45:18 .... but I don't think it's actually a clip path right 19:45:22 ... it is clipped 19:45:41 ... Because they establish a new coordinate system 19:45:53 ... they do a number of things that clippaths do not do 19:46:25 ... I just see them as very different things 19:46:34 ED: I agree, but they have similarities 19:47:07 DS: So you're saying that any clipping whether it be from the viewport establishing element or a clippath would behave similarly? 19:47:27 ED: To me I'm seeing it like a filter 19:47:34 ... you're clipping something 19:47:53 ... I'd expect only the events going to that clippath 19:48:06 ... I'd expect whatever was in the viewport to be clipped or limited by the clipping 19:48:14 s/to that clippath/through that clippath/ 19:48:20 DS: I guess it just doesn't seem intuitive to me 19:49:00 ... You're going off the computed value. You might want to have different things have different pointer events within the same group 19:49:58 ED: Yes. I had tests made for it already but I think it would be useful to see what implementations are doing 19:51:39 ... A group doesn't have a fill or stroke 19:51:44 DS: But we are working on computed values 19:51:55 ED: I'd like to see a couple of implementations doing one way 19:51:59 DS: I'll make a test 19:52:46 ACTION: Doug to Test for event clipping when the clippath is on a group 19:52:46 Created ACTION-2384 - Test for event clipping when the clippath is on a group [on Doug Schepers - due 2008-12-25]. 19:53:45 Topic: SVG 1.1 Test Suite 19:53:50 http://dev.w3.org/SVG/profiles/1.1F2/test/ 19:53:55 ED: I moved the tests from the old archive to the new one 19:54:07 ... I moved latest revisions 19:54:23 ... it turns out that diffing these tests against the 1.2 Tiny tests 19:54:32 ... has quite a few significant changes 19:54:41 ... one of the problems is because we use a new template 19:54:44 ... for Tiny 1.2 19:55:00 ... doesn't have the exact same syntax for test case descriptions 19:55:06 ... uses xml:id - small thing 19:55:14 ... I had hoped for something better 19:55:22 ... just wondering what's the best way to deal with this now 19:55:49 CL: We could XSLT out the content of the test 19:55:53 ... all the stuff should be there 19:55:59 ... it would be easier 19:56:09 ... and let us focus on what the differences are 19:56:14 ... then looking on the SVG root element 19:56:21 ... to see what the differences are 19:56:26 ... see if there is anything added 19:56:41 ED: One thing I was wandering was the SVG Fonts 19:56:49 ... we used them all over in SVG Tiny 1.2 19:56:54 ... but not in 1.1 19:57:05 CL: Reason for that 1.1 Tiny didn't let you use SVG Fonts 19:57:10 ... but 1.1 Full did 19:57:17 ... previously you had to have certain fonts installed 19:57:23 ... and you'd get inconsistencies 19:57:30 ... I think it should be ok to use SVG Fonts though 19:58:36 AG: I committed the new template to the archive 19:58:50 .. which is similar to the SVG Tiny 1.2 template 19:58:57 ... it uses SVG Fonts 19:59:03 ... I like Chris's idea 19:59:19 ED: I agree we should probably use the new template everywhere 19:59:36 ... so the question is would it be easier to make a script for it or get XSLT to do the same 19:59:56 ... I don't really mind either way as long as the end result is the same 20:00:42 AG: I guess it'd probably be ok to use XSLT 20:00:56 CL: Once we have a working method for doing this 20:01:03 ... we can just check in the new ones 20:01:12 ... perhaps tag them before we commit the new ones 20:02:27 ED: My action to moving the test suite and diffing the test suite 20:02:36 ... should I close the action 20:02:44 AG: I think that action is complete 20:02:51 ... for this task we need a new action 20:03:08 ED: One thing I didn't move on purpose was move the scripts directory 20:03:31 ... I figured we'd probably only want one script to work on the test suites 20:03:43 trackbot, close ACTION-2382 20:03:44 ACTION-2382 Move the 1.1 tests to public cvs, checking diffs against the corresponding 1.2T tests closed 20:04:39 ACTION-2352 20:04:48 ACTION-2352? 20:04:48 ACTION-2352 -- Erik Dahlström to get rid of svggen/ -- due 2008-11-27 -- OPEN 20:04:48 http://www.w3.org/Graphics/SVG/WG/track/actions/2352 20:04:57 ED: I guess I can continue my current action to try to rip out stuff from the old scripts and try to merge with the new ones 20:05:15 ... I'll add a note to that action saying that's also about merging the scripts 20:05:38 AG: Keep in mind when you merge the scripts to base it on the new template 20:08:02 ACTION: Anthony to Make an XSLT to change the template of the 1.1 tests to the new one 20:08:02 Created ACTION-2385 - Make an XSLT to change the template of the 1.1 tests to the new one [on Anthony Grasso - due 2008-12-25]. 20:10:59 Topic: Name Change of SVG Tiny 1.2 20:11:13 DS: I emailed Bitflash and Ikivo off list 20:11:17 ... they did respond 20:11:32 s/clipped the SVG a bit/clipped the circle a bit/ 20:11:50 DS: Bitflash - didn't like the change for marketing reasons. They didn't want to confuse their customers 20:12:06 ... Ikivo - didn't mind the name chage however they didn't want anything to slow down publication 20:12:35 ... We have a commitment to JIS but also to OMA and JSR and they are counting on SVG Tiny being published as soon as possible 20:12:47 s/ED: Yes. I had tests made for it already but/ED: / 20:13:13 ... JSR already references SVG Tiny 1.2 20:13:32 CL: I suggested that we clarify in the status of the document 20:13:45 ... we should clarify this relationship 20:13:56 ... and say that future versions of this will be called Core 20:14:16 ... and not Tiny 20:16:04 AG: Canon thinks that it is important to change the name 20:16:56 DS: I understand Canon's position but I'm also concerned about the positions of the other members 20:26:42 +??P4 20:27:07 Zakim, ??P4 is jwatt 20:27:07 +jwatt; got it 20:28:07 Topic: Errata Items 20:28:18 http://dev.w3.org/SVG/profiles/1.1F2/errata/errata.xml 20:30:48 http://dev.w3.org/SVG/profiles/1.1F2/errata/errata.xml#svgzoomevent-interface 20:32:17 http://lists.w3.org/Archives/Public/www-svg/2008Dec/0049.html 20:34:10 ED: First one is the Zoom Event interface 20:34:24 ... Reported by JWatt 20:34:31 ... I think we were almost decided on this one 20:35:05 AG: I remember making the changes for it, but Andrew had an action to investigate something relating to it 20:35:13 ED: So it might something in Tiny? 20:35:17 AG: I can't remember 20:35:24 ED: SVGZoom is an Event in SVG Tiny 20:35:34 ... it's a Mouse event 20:36:11 http://www.w3.org/TR/SVG11/interact.html 20:36:26 s/Mouse event/Event/ 20:36:36 ... there's no corresponding DOM2 category in SVG 1.1 20:36:45 ...for SVGZoom 20:37:06 ED: So they do seem to be slightly different 20:37:25 interface SVGZoomEvent : events::UIEvent { 20:37:25 readonly attribute SVGRect zoomRectScreen; 20:37:25 readonly attribute float previousScale; 20:37:25 readonly attribute SVGPoint previousTranslate; 20:37:26 readonly attribute float newScale; 20:37:26 readonly attribute SVGPoint newTranslate; 20:37:28 }; 20:38:06 ED: This is what the IDL says not what the table in the interactivity section says 20:38:35 CM: DOM2 Category doesn't always need to correspond to the interface 20:38:40 ... but it would be better if they did 20:39:28 ED: Is it necessary that the Zoom event to inherit form the UI event 20:39:39 ... one way to inherit just from event 20:39:59 ... just wondering if there is anything in UI Event that is needed 20:40:03 CM: View perhaps 20:40:07 ... you need a particular view 20:40:10 ... not useful 20:40:17 DS: I guess that's fair enough 20:40:30 s/DS:/EDS/ 20:40:44 agenda+ SVG Open 20:41:18 ED: So in Tiny 1.2 there is nothing on the SVG Zoom 20:41:26 ... you only get the Event with the type of SVG Zoom 20:41:34 ... but you don't have any properties like in 1.1 20:42:21 ... the other thing is the bubbling canceling of the events because they are similar 20:43:20 ... so that would make it a bit difficult I guess 20:43:43 ... question is do we need to bubble or should we errata 1.2? 20:43:59 ... I can admit to not having used Zoom events that much 20:44:07 CL: Do we have content that depends on this? 20:44:16 ... usually on the root element 20:44:18 ED: Yes 20:44:29 CL: Which kind of means it's not going anywhere 20:44:45 DS: If I recall correctly in SVG 1.1 it's only allowed on the root 20:44:54 ... although I could be thinking of ASV 20:45:21 JW: That's how Mozilla does it. We don't implement zoom on anything else but the Zoom element 20:45:55 s/Zoom element/root element/ 20:46:24 Mozilla only pays attention to attempts to set currentScale/currentTranslate on the root element 20:46:51 DS: And that would actually correspond to how the current Zoom and current translate on nested reflect the value of the root 20:47:01 so trying to change them on nested elements will be ignored 20:47:17 i.e. we don't dispatch an SVGZoom event there 20:47:42 ED: Sounds more like better to say that it doesn't in 1.1 to go with what we have 1.2 Tiny 20:47:46 DS: Sounds good 20:47:57 JW: Are there bubbling events in Tiny though? 20:48:02 ED: Sure there are a couple of those 20:49:06 -shepazu 20:49:29 s/ED: Sounds more like better to say that it doesn't/ED: Sounds more like it's better to say that it doesn't bubble/ 20:49:32 so my concern with saying that SVGZoomEvent doesn't bubble is that there could be content out there that relies on that 20:49:42 so things could break 20:49:50 +??P1 20:50:01 Zakim, ??P1 is me 20:50:01 +shepazu; got it 20:50:22 DS: I guess that concern could be addressed by saying that event is dispatched to the outermost/rootmost element in SVG 1.1 20:50:36 but saying in tiny that it does bubble isn't much of a burden on tiny implementers 20:50:44 and avoids the risk of breaking stuff 20:50:49 zakim, who is noisy? 20:51:04 ChrisL, listening for 10 seconds I could not identify any sounds 20:51:12 zakim, you suck 20:51:12 I don't understand 'you suck', ChrisL 20:51:54 ED: Saying that it does bubble in Tiny at this point is a bit light I guess 20:52:00 ... we could issue an errata 20:52:03 s/light/late/ 20:53:27 ED: I think those issues are the one we have to deal with 20:53:27 so I don't have a strong preference either way 20:53:33 ... I don't think there are any more 20:53:55 but please use "document element", not "rootmost element" 20:54:55 jwatt, "rootmost element" has a particular defined meaning in 1.2T 20:55:22 ED: Document element may include an element other than SVG element 20:55:28 ... depends on how you implement I guess 20:55:42 ... Opera does support zooming on particular SVG graphics 20:55:49 ... not sure how we do Zoom Events 20:57:05 ED: We should definitely align 1.1 and 1.2 20:57:26 CL: I agree we just need to be careful about any effects the changes my cause 20:58:23 ED: JWatt would you like to take an action to investigate this any further 20:58:28 JW: Sure 20:58:29 ja 20:58:46 tracker status? 20:58:58 trackbot, status? 20:59:46 ACTION: Jonathan to Investigate the "SVGZoomEvent - Interface" errata item further 20:59:46 Created ACTION-2386 - Investigate the \"SVGZoomEvent - Interface\" errata item further [on Jonathan Watt - due 2008-12-25]. 21:00:13 action-2386? 21:00:14 ACTION-2386 -- Jonathan Watt to investigate the "SVGZoomEvent - Interface" errata item further -- due 2008-12-25 -- OPEN 21:00:14 http://www.w3.org/Graphics/SVG/WG/track/actions/2386 21:00:34 Action: jwatt to look into Mozilla helping sponsor SVG Open 21:00:34 Created ACTION-2387 - Look into Mozilla helping sponsor SVG Open [on Jonathan Watt - due 2008-12-25]. 21:01:11 -shepazu 21:01:17 dang skype 21:02:01 Topic: Break 21:02:13 ED: There will be no Telcons for the next 2 weeks 21:02:35 ... we will have the next telcon on 5th Monday 21:02:47 Zakim won't let me rejoin 21:02:54 -ed 21:02:55 -ChrisL 21:03:03 -heycam 21:03:03 CL: I'll still be on holidays then, but I'll back for the Thursday one 21:03:09 -anthony 21:03:31 -jwatt 21:03:32 GA_SVGWG()2:30PM has ended 21:03:33 Attendees were ed, shepazu, ChrisL, heycam, [IPcaller], anthony, jwatt 21:03:45 Zakim, bye 21:03:45 Zakim has left #svg 21:03:55 RRSAgent, make minutes 21:03:55 I have made the request to generate http://www.w3.org/2008/12/18-svg-minutes.html anthony 21:17:09 ed__ has joined #svg 21:28:54 anthony has joined #svg 22:45:50 heycam has joined #svg 23:36:31 shepazu has joined #svg