Minutes, March 26 2026 SVG WG telcon

Minute from today’s telcon: https://www.w3.org/2026/03/26-svg-minutes.html



IRC log of svg on 2026-03-26

Timestamps are in UTC.

06:45:41 [RRSAgent]
RRSAgent has joined #svg
06:45:45 [RRSAgent]
logging to https://www.w3.org/2026/03/26-svg-irc

06:45:46 [Zakim]
Zakim has joined #svg
06:46:07 [dmangal]
dmangal has joined #svg
06:46:10 [dmangal]
present+
06:47:04 [ydaniv]
present+
06:47:49 [caribou]
present+
06:47:58 [krit]
scribe: krit
06:48:01 [krit]
topic: Support pathLength via CSS
06:48:05 [krit]
https://github.com/w3c/svgwg/issues/773

06:48:37 [krit]
viralipurbey: This is a follow up: Should we extend the property unit from number to length.
06:48:53 [krit]
viralipurbey: For now we just extend the existing attribute to presentation attribute.
06:49:19 [krit]
viralipurbey: While implementing, we signaled the implementation to Firefox
06:49:45 [krit]
viralipurbey: It has a lot of complexity to support length.
06:50:09 [krit]
viralipurbey: We should take it as a different issue and land the presentation attribute change in the spec.
06:50:20 [krit]
nzimmermann: Don't mind to take it into 2 steps.
06:50:52 [krit]
krit: Might there be a complication if we change unit from number to length?
06:51:10 [krit]
viralipurbey: we can talk about it later?
06:51:33 [krit]
viralipurbey: It is already a number unit. So don't see an issue
06:51:52 [krit]
krit: No objection from my side.
06:52:44 [krit]
RESOLUTION: pathLength attribute will get a presentation attribute with the CSS property being path-length taking a number unit only for now
06:53:19 [krit]
ACTION: viralipurbey to prepare spec edits. ydaniv and nzimmermann to review the PR
06:54:10 [Vinay]
Vinay has joined #svg
06:54:11 [krit]
s/ydaniv/dmangal/
06:54:27 [Vinay]
present+
06:55:09 [krit]
topic: Multi-Page support
06:55:12 [krit]
https://github.com/w3c/svgwg/issues/157

06:57:17 [krit]
krit: This is a request to support multi pages support from the SVG draft 1.2 in SVG 2.
06:57:54 [krit]
nzimmermann: I support to reject the request. CSS Paged Media is better suited for this task
06:58:01 [krit]
nzimmermann: it is hard to implement too
06:58:29 [krit]
krit: Out of charter scope anyway
06:58:39 [krit]
caribou: correct
06:58:53 [krit]
RESOLUTION: Multi pages will not get adapted in SVG2
06:59:05 [krit]
topic: Publish current status of SVG
06:59:10 [krit]
https://github.com/w3c/svgwg/issues/938

06:59:35 [krit]
caribou: Karl was working on supporting bikeshed for the spec
06:59:58 [krit]
caribou: We are making progress on the editors draft but should also focus on an actual publication
07:00:51 [krit]
krit: would you prefer using the old system or can we wait for bikeshed migration?
07:01:19 [krit]
caribou: Maybe it is ok to wait for the bikeshed migration
07:02:05 [krit]
krit: Lets wait for Karl to provide feedback on the current status before we make the decision.
07:03:05 [krit]
topic: SVGPathSegment should be a dictionary, not a [NoInterfaceObject] interface
07:03:08 [krit]
https://github.com/w3c/svgwg/issues/1082

07:03:15 [krit]
Vinay: this is about the new data API
07:03:46 [krit]
Vinay: Previous old API using DOM was deprecated 15 years back. Chromium has deprecated.
07:04:12 [krit]
viralipurbey: Edge cases were not defined properly in the old API and remove
07:04:28 [krit]
viralipurbey: the new API was added. Last year Firefox implemented it.
07:04:38 [krit]
viralipurbey: Chromium also plans to implement.
07:05:18 [krit]
viralipurbey: We should use a dictionary rather than NoInterface for SVGPathSegment
07:05:46 [krit]
viralipurbey: Even Firefox ran into issues when adapting the new API and uses dictionary
07:06:11 [krit]
krit: dictionary is more flexible anyway. Any downside for it?
07:06:27 [krit]
viralipurbey: we don't see any. Even our polyfill is working fine with that.
07:07:06 [krit]
viralipurbey: sugesting to got from
07:07:45 [krit]
viralipurbey: going from float to unrestricted float to support 0 and NaN types.
07:08:02 [krit]
viralipurbey: earlier it gave type error
07:08:33 [krit]
viralipurbey: Firefox also did the suggested change
07:09:11 [krit]
RESOLUTION: SVGPathSegment defined as dictionary instead of NoInterfaceObject and make value unrestricted float from float
07:09:33 [krit]
topic: New Interface SVGPathSegment: segments should be more editable
07:09:39 [krit]
https://github.com/w3c/svgwg/issues/974

07:10:06 [krit]
viralipurbey: Same thing: Previously there was a CTOR for SVGPathElement. With dictionary, this is not valid.
07:10:23 [krit]
viralipurbey: All new code doesn't use the CTOR.
07:10:48 [krit]
viralipurbey: no backwards compatibiliy since it hasn't been implemented anywhere
07:13:02 [krit]
nzimmermann: My concern is the SVG Path spec which is WD since 2015 last updated
07:13:10 [krit]
nzimmermann: it is not in SVG2 but SVG Path
07:13:30 [krit]
nzimmermann: SVG Path also has new features that haven't been implemented and have many open issues
07:13:38 [krit]
nzimmermann: So where should we put all this?
07:14:17 [karlcow]
present+
07:15:31 [krit]
krit: It is still part of SVG2 but the interfaces are missing and in SVG Path spec.
07:15:48 [karlcow]
Close in webkit bugs https://bugs.webkit.org/show_bug.cgi?id=168519

07:16:12 [krit]
nzimmermann: Question is where we normatively define SVGPathSegment? Is it still in SVG 2 or SVG Path spec (which never reached CR)
07:19:06 [caribou]
https://www.w3.org/TR/SVG2/paths.html

07:19:10 [karlcow]
https://www.w3.org/2011/10/27-svg-irc#T18-23-23

07:19:39 [krit]
krit: the entire interface section has been removed from SVG 2
07:19:57 [caribou]
https://www.w3.org/TR/SVG2/paths.html#InterfaceSVGPathElement leads to nothing
07:20:08 [karlcow]
https://w3c.github.io/svgwg/specs/paths/

07:20:21 [karlcow]
https://w3c.github.io/svgwg/specs/paths/#InterfaceSVGPathSegment

07:21:16 [krit]
krit: Path Spec is out of scope from charter. I suggest to create a proposal to re-add the interfaces. And all members agree on get re-added to SVG 2.
07:21:20 [krit]
nzimmermann: agree
07:22:58 [krit]
ACTION: viralipurbey to create a PR to re-introduce SVG Path interfaces from SVG Path spec into SVG 2 for approval of the WG
07:24:46 [krit]
dmangal: Does introducing dictionaries make path data editable?
07:24:53 [krit]
dmangal: we need to be sure it dows
07:24:58 [krit]
s/dows/does/
07:25:34 [krit]
viralipurbey: I don't see an issue. The Polyfill does use the dictionary approach and has no issue with edtiablity
07:25:56 [krit]
RESOLUTION: Drop SVGPathElement constructor in favor for dictionary model
07:34:08 [krit]
Zakim, make minutes
07:34:08 [Zakim]
I don't understand 'make minutes', krit
07:34:14 [krit]
RRSAgent: make minutes
07:34:15 [RRSAgent]
I have made the request to generate https://www.w3.org/2026/03/26-svg-minutes.html krit
07:34:27 [krit]
RRSAgent, make logs public