Meeting minutes
<karlcow__> karl+
ONe agenda Item: w3c/
SVGAnimatedLength initial value for fx and fy
karlcow__: gradient has a couple of attributes like cx/cy/fx/fy. Spec defines default values. There are 2 values for cx/cy
karlcow__: for fx/fy it is 50%
karlcow__: If fx is not defined, it should be the value of cx
karlcow__: If cx is not defined, it is 50%, so the same should be the case for fx
karlcow__: the implemented behavior is different though. If cx is not define but fx isn't, the value of fx is 50%.
krit: for all browsers?
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.
karlcow__: what do we want to do? FF doesn't seem wanting to change the behavior and Niko is the of the same opinion.
… some discussion to clarify the current behavior
karlcow__: I uploaded an extensive test case in the github issue.
krit: Seems like many vendors commented on the github issue to keep the implemented behavior and change the spec text
viralipurbey: Is there a test where cx isn't specified but fx is?
karlcow__: it is part of the test.
karlcow__: FF and Chrome are fully interoperable
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.
karlcow__: I'll upload a test to WPT once we made the decision.
karlcow__: at this point, changing browsers may actually be a bigger harm
RESOLUTION: fx/fy will have default values of 50% if not specified independent of the specified value of cx/cy.
ACTION: karlcow__ will edit the spec and add a test to WPT
<caribou> w3c/
Manual publication of SVG-AAM Working Draft
caribou: The ARIA WG wants to republish the interop spec. They ask if the SVG WG has an issue with republishing.
karlcow__: no concerns to republish
krit: me neither. Will comment on the issue
RRSAgent: make minutes