05:32:25 RRSAgent has joined #svg 05:32:30 logging to https://www.w3.org/2025/10/23-svg-irc 05:32:31 Zakim has joined #svg 05:43:27 Vinay has joined #svg 05:45:03 present+ 05:45:13 present+ 05:46:39 present+ 05:47:07 dmangal has joined #svg 05:47:11 Ragvesh has joined #svg 05:47:21 present+ 05:50:22 karlcow has joined #svg 05:50:57 ScribeNick: karlcow 05:51:54 topic: Publish current status of SVG https://github.com/w3c/svgwg/issues/938 05:52:51 Carine: We do not have current editors in the WG. All the previous ones are gone. 05:53:02 Krit: I'm still an editor. 05:53:19 Carine: we should remove the previous editors apart of grit. 05:53:33 S/grit/Dirk/ 05:54:09 Carine: I will probably need help to republish the spec, and check if it's in the right format. 05:54:43 Krit: the publishing will be a copy/paste operation. 05:56:29 Karl: Should we coordinate in Kobe to move the spec to bikeshed/respec? 05:57:29 Krit: I do not mind any format. For respec, there will be more work after which defeats the purpose of automatic publication. 05:58:45 Carine: I will ask around if they use Respec for multipage. 05:59:18 Krit: Let's see if we can move forward for publishing a new version as-is today 05:59:33 ... who should be added as editors from Microsoft? 06:00:38 ... Someone from Microsoft will be defined. 06:03:53 RESOLVED: Vinay @@, Karl Dubost should be added/listed as spec editors. 06:04:16 Carine: Should we republish as a CR or a WD or a snapshot. 06:04:30 ... did we have substantial changes? 06:04:56 Karl: We went back to some ways of SVG 1.1 06:05:06 Carine: This should not have impact on IPR. 06:05:27 ... the process has changed a couple of times. 06:05:59 RESOLUTION: Let's publish a new snapshot. Please object if there are any concerns about this. 06:06:32 S/publish a new snapshot/publish a new CR snapshot/ 06:07:12 Carine: let's try to stage it in advance before the publication. Just in case we forgot something. 06:07:37 Krit: I will double check how to do that. Haven't done it in a longtime. 06:08:22 Karl: Do we need to modify the CSS references before publishing? When will it be published? 06:08:32 Krit: yes ideally. 06:08:57 ... Publication will probably happen end of November, beginning of December. 06:09:33 Topic: Meeting time change (in the light of summer/winter changes) 06:10:26 Krit: 7:45 Europe 06:10:27 ... 14:45 Japan 06:10:47 ... 22:45 Pacific 06:11:40 ... Right now, we have only Japan and Europe. 06:12:14 ... we can keep the time as-is for now. 06:12:32 https://github.com/w3c/svgwg/issues/1018 06:12:43 Topic: getBBox() - https://github.com/w3c/svgwg/issues/1018 06:14:17 Ragvesh: From blink side, we are good to go with the proposal changing our implementations. 06:14:52 karl: we should change the WPT. 06:17:37 RESOLUTION: let's remove the throwing part for invalid getbbox() and make the returned values be 0 for width/height and x/y 06:20:13 Topic: next agenda for next meeting. 06:20:13 Please use agenda+ on issues so the meeting is not canceled in advance. 06:20:32 S/Please use/krit: Please use/ 06:20:58 Rrsagent, make minutes 06:21:00 I have made the request to generate https://www.w3.org/2025/10/23-svg-minutes.html karlcow 06:21:14 Reagent, make log public 06:21:26 Rrsagent, make log public 07:33:54 @krit, https://www.w3.org/TR/web-sustainability-guidelines/ is using some JS to enable multipage with respec 07:38:47 caribou: It is not actually a paged spec. All information are in the same document but hidden. We would not be able to keep links alive like https://svgwg.org/svg2-draft/conform.html. 08:03:55 Zakim has left #svg 08:12:32 indeed, they are mimicking separate pages, but no separate files 08:12:51 we would have to set up a lot of redirects if we want to keep the uris