minutes, January 29 2026 SVG WG telcon

Minutes from today’s telcon are below.

<https://www.w3.org/2026/01/29-svg-minutes.html>
SVG WG Meeting – 29 January 2026<https://www.w3.org/2026/01/29-svg-minutes.html>
w3.org<https://www.w3.org/2026/01/29-svg-minutes.html>
[favicon.ico]<https://www.w3.org/2026/01/29-svg-minutes.html>


IRC log of svg on 2026-01-29

Timestamps are in UTC.

06:38:53 [RRSAgent]
RRSAgent has joined #svg
06:38:58 [RRSAgent]
logging to https://www.w3.org/2026/01/29-svg-irc

06:43:48 [karlcow__]
karl+
06:45:23 [Vinay]
Vinay has joined #svg
06:45:53 [Vinay]
present+
06:46:12 [dmangal]
dmangal has joined #svg
06:46:33 [caribou]
Meeting: SVG WG Meeting
06:47:06 [dmangal]
present+
06:47:11 [krit]
present+
06:47:14 [karlcow__]
scribeNick: krit
06:47:20 [caribou]
present+
06:47:22 [karlcow__]
present+
06:47:27 [krit]
ONe agenda Item: https://github.com/w3c/svgwg/issues/1054

06:47:29 [viralipurbey]
viralipurbey has joined #svg
06:47:35 [viralipurbey]
present+
06:47:37 [krit]
topic: SVGAnimatedLength initial value for fx and fy
06:47:41 [krit]
https://github.com/w3c/svgwg/issues/1054

06:48:21 [krit]
karlcow__: gradient has a couple of attributes like cx/cy/fx/fy. Spec defines default values. There are 2 values for cx/cy
06:48:30 [krit]
karlcow__: for fx/fy it is 50%
06:49:00 [krit]
karlcow__: If fx is not defined, it should be the value of cx
06:49:19 [krit]
karlcow__: If cx is not defined, it is 50%, so the same should be the case for fx
06:50:14 [krit]
karlcow__: the implemented behavior is different though. If cx is not define but fx isn't, the value of fx is 50%.
06:50:35 [krit]
krit: for all browsers?
06:51:09 [krit]
karlcow__: chrome and FF yes. For webkit the test was broken and we wanted to fix the issue. While fixing we saw the difference between spec and browsers.
06:51:54 [krit]
karlcow__: what do we want to do? FF doesn't seem wanting to change the behavior and Niko is the of the same opinion.
06:52:54 [krit]
... some discussion to clarify the current behavior
06:54:04 [krit]
karlcow__: I uploaded an extensive test case in the github issue.
06:56:02 [krit]
krit: Seems like many vendors commented on the github issue to keep the implemented behavior and change the spec text
06:56:40 [krit]
viralipurbey: Is there a test where cx isn't specified but fx is?
06:56:51 [krit]
karlcow__: it is part of the test.
06:57:07 [krit]
karlcow__: FF and Chrome are fully interoperable
06:58:45 [krit]
krit: personally I like the speced behavior more, but since it isn't reflecting the reality and there doesn't seem to be complains from content creators, there is no reason to keep the speced text. So better to adapt the spec to reality.
06:59:00 [krit]
karlcow__: I'll upload a test to WPT once we made the decision.
07:00:02 [krit]
karlcow__: at this point, changing browsers may actually be a bigger harm
07:00:39 [krit]
RESOLUTION: fx/fy will have default values of 50% if not specified independent of the specified value of cx/cy.
07:01:17 [krit]
ACTION: karlcow__ will edit the spec and add a test to WPT
07:01:44 [caribou]
https://github.com/w3c/svg-aam/issues/41

07:01:54 [krit]
topic: Manual publication of SVG-AAM Working Draft
07:01:58 [krit]
https://github.com/w3c/svg-aam/issues/41

07:02:47 [krit]
caribou: The ARIA WG wants to republish the interop spec. They ask if the SVG WG has an issue with republishing.
07:02:58 [viralipurbey]
viralipurbey has joined #svg
07:04:03 [krit]
karlcow__: no concerns to republish
07:04:11 [krit]
krit: me neither. Will comment on the issue
07:06:26 [krit]
RRSAgent: make minutes
07:06:27 [RRSAgent]
I have made the request to generate https://www.w3.org/2026/01/29-svg-minutes.html krit
07:06:51 [krit]
RRSAgent, make logs public