- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Jul 2018 22:31:24 +0000
- To: public-svg-issues@w3.org
AmeliaBR has just labeled an issue for https://github.com/w3c/svgwg as "Test suite": == Review implementation support - Paths chapter == [Changes:](https://svgwg.org/svg2-draft/changes.html#paths) ### Added new B and b "bearing" path commands. [At Risk] [Tests](https://wpt.fyi/svg/path/bearing) show no browsers support bearing commands. ### Allow Z or z to fill in missing path coordinate data in the previous command with the coordinate of the initial point in the subpath. [At Risk] [Tests](https://wpt.fyi/svg/path/closepath) show no browsers support z filling in missing path coordinate data. InkScape plans to implement. ### Define ‘path’, ‘polygon’ and ‘polyline’ elements with no data set (empty or zero valid commands) to not render. [Tests](https://wpt.fyi/svg/path/error-handling) show Chrome, Edge, Firefox, Safari support this functionality. ### Removed the SVGPathSeg* and SVGAnimatedPathData interfaces and the related methods on SVGPathElement. [Tests](https://wpt.fyi/svg/path/interfaces/SVGAnimatedPathData-removed.svg) show only Chrome has removed the interfaces and related methods. ### Promoted the ‘d’ attribute to a property. [At Risk] [Tests](https://wpt.fyi/svg/path/property) show Chrome exposes 'd' as a property, with an implementation that [differs](https://github.com/w3c/svgwg/pull/374) from the current spec. ### Removed the pathLength attribute, getTotalLength(), and getPointAtLength() methods from SVGPathElement, they are now on SVGGeometryElement. [At Risk] [Tests](https://wpt.fyi/svg/types/elements/SVGGeometryElement-rect.svg) show lack of browser support. ### Clarified that a value of zero for ‘pathLength’ is valid. [Tests](https://wpt.fyi/svg/path/distance) exist. There are some test failures, these need investigation. See https://github.com/w3c/svgwg/issues/385
Received on Monday, 9 July 2018 22:31:28 UTC