Re: [svgwg] Review implementation support - Paths chapter

The Working Group just discussed `https://github.com/w3c/svgwg/issues/384`.

<details><summary>The full IRC log of that discussion</summary>
&lt;ericwilligers> Topic: https://github.com/w3c/svgwg/issues/384<br>
&lt;BogdanBrinza> topic new<br>
&lt;BogdanBrinza> GitHub: https://github.com/w3c/svgwg/issues/384<br>
&lt;BogdanBrinza> ericwilligers: We'll start with Extensibility chapter<br>
&lt;BogdanBrinza> two changes to the spec<br>
&lt;Chris> great, good to hear<br>
&lt;liam> awesome<br>
&lt;ericwilligers> GitHub: https://github.com/w3c/svgwg/issues/385<br>
&lt;BogdanBrinza> all: sound great - no concerns to make width/height presentation attrbutes<br>
&lt;BogdanBrinza> GitHub: https://github.com/w3c/svgwg/issues/385<br>
&lt;liam> [i think at TPAC we agreed to remove bearing commands, would be good to reaffirm that here]<br>
&lt;BogdanBrinza> ericwilligers: bearing commands - no current implementations, at risk<br>
&lt;BogdanBrinza> https://svgwg.org/specs/paths/<br>
&lt;AmeliaBR> https://www.w3.org/2017/04/svg-2017.html#scope " features which are in the reference draft of SVG2 and which do not meet the stability and interoperability requirements for a Proposed Recommendation may be moved to separate specification modules, work on which would remain in scope, but at a lower priority."<br>
&lt;BogdanBrinza> resolution: remove bearing commands from SVG 2.0 specification, optionally move to https://svgwg.org/specs/paths/<br>
&lt;Chris> Tav: Inkscape plans to implement this<br>
&lt;Chris> BogdanBrinza: OK, but no browser implementation yet<br>
&lt;Chris> AmeliaBR: much asked-for feature<br>
&lt;BogdanBrinza> resolution: remove Z and z from SVG 2.0 and move to https://svgwg.org/specs/paths/<br>
&lt;BogdanBrinza> no issues with path, polygon, etc *<br>
&lt;BogdanBrinza> "Removed the SVGPathSeg* and SVGAnimatedPathData interfaces and the related methods on SVGPathElement."<br>
&lt;BogdanBrinza> tests suggest that only Chrome removed it - shouldn't be a blocker to removal from the specification<br>
&lt;BogdanBrinza> krit: are browsers interested in implementing new features? specifically mesh gradients, new path commands<br>
&lt;BogdanBrinza> krit: if they're not implemented will we have just another revision of SVG 1.1?<br>
&lt;BogdanBrinza> AmeliaBR: the discussion is really about this year, in time for candidate recommendation<br>
&lt;BogdanBrinza> Chris: suggest we keep focused on the discussion on the agenda<br>
&lt;BogdanBrinza> BogdanBrinza: (getting back to GitHub discussion)<br>
&lt;BogdanBrinza> ericwilligers: Promoted the ‘d’ attribute to a property. [At Risk]<br>
&lt;Chris> yes, keep this one in the spec<br>
&lt;BogdanBrinza> Tav: considering implementation in Inkscape<br>
&lt;BogdanBrinza> ericwilligers: "Removed the pathLength attribute, getTotalLength(), and getPointAtLength() methods from SVGPathElement, they are now on SVGGeometryElement. [At Risk]"<br>
&lt;BogdanBrinza> ericwilligers: no browser implementations<br>
&lt;BogdanBrinza> AmeliaBR: Chrome should support this<br>
&lt;BogdanBrinza> ericwilligers: will double check the test<br>
&lt;BogdanBrinza> resolution: this is (same) interface change - keep this at risk<br>
&lt;BogdanBrinza> ericwilligers: "Clarified that a value of zero for ‘pathLength’ is valid."<br>
&lt;BogdanBrinza> resolution: not at risk - just a clarification to a spec<br>
&lt;liam> [big thank you yes]<br>
&lt;Chris> nice one, ericwilligers<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/385#issuecomment-363207475 using your GitHub account

Received on Monday, 5 February 2018 20:14:44 UTC