- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Dec 2019 20:27:55 +0000
- To: public-svg-issues@w3.org
The SVG Working Group just discussed `Rect decomposition is invalid / markers equivalent paths for basic shapes`, and agreed to the following: * `RESOLUTION: Equivalent path for rect without corner radius uses a closepath segment for the last straight line` * `RESOLUTION: Make markers on circle, ellipse, and rect At Risk; file browser bugs asking for implementation plans & feedback (including re equivalent path interactions)` <details><summary>The full IRC log of that discussion</summary> <AmeliaBR> Topic: Rect decomposition is invalid / markers equivalent paths for basic shapes<br> <AmeliaBR> github: https://github.com/w3c/svgwg/issues/753<br> <nzimmermann> AmeliaBR: presents rect decomposition is invalid<br> <nzimmermann> AmeliaBR: issue complains that the equivalent path description for rectangles has a bunch of conditional statements, depending on rx/ry. as it is currently written for rx=ry=0 the path is not closed. if someone literally implements the wording of the spec one could end up with an unclosed path<br> <nzimmermann> AmeliaBR: the discussion in the issue got complex, how to resolve this properly in svg2.<br> <nzimmermann> AmeliaBR: explains the broader scope of the topic<br> <nzimmermann> AmeliaBR: summary of the discussion in the issue<br> <nzimmermann> AmeliaBR: right now you cannot create a circle with a path when using the equivalent path formulation: the difference is in how markers are treated (additional close path segment)<br> <AmeliaBR> s/when using/that has the same effect as/<br> <nzimmermann> AmeliaBR: follow up was: the same thing is true for curved rectangles, for straight-line rectangles there is no issue<br> <nzimmermann> AmeliaBR: my recommandation is: fix the issue about straight line rectangles, make sure it is closed, with a simple closePath command, and add an at-risk warning about markers on the shapes that did not have markers in SVG1<br> <nzimmermann> AmeliaBR: file browser bugs asking to implement markers on the other shapes (rectangles, circles and ellipses) and see if we can get any feedback from implementors, about it being difficult or not<br> <nzimmermann> AmeliaBR: difficulty might be regarding segment completing curves, as this does not exists in paths currently<br> <nzimmermann> AmeliaBR: if we do get feedback that segment completing curves are a problem, then we need to think about alternatives<br> <nzimmermann> Tavmjong: if you put mid-marker on a rect it would only be on 3 corners<br> <nzimmermann> AmeliaBR: correct to get a marker on all 4 corners, one would also need start/end markers<br> <nzimmermann> krit: asks about markers support in polygons<br> <nzimmermann> AmeliaBR: not implemented yet<br> <nzimmermann> Tamvjong: Inkscape can render it<br> <krit> s/in polygons/in regular shapes/<br> <AmeliaBR> Proposed resolution: Equivalent path for rect without corner radius uses a closepath segment for the last straight line<br> <nzimmermann> RESOLUTION: Equivalent path for rect without corner radius uses a closepath segment for the last straight line<br> <AmeliaBR> Proposed 2: Make markers on circle, ellipse, and rect At Risk; file browser bugs asking for implementation plans & feedback (including re equivalent path interactions)<br> <nzimmermann> RESOLUTION: Make markers on circle, ellipse, and rect At Risk; file browser bugs asking for implementation plans & feedback (including re equivalent path interactions)<br> <nzimmermann> s/Make/Mark/<br> <nzimmermann> Tavmjong: will work on the tests, to reflect the changes<br> <nzimmermann> AmeliaBR: will work on the spec, and review test changes<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/svgwg/issues/753#issuecomment-567199686 using your GitHub account
Received on Wednesday, 18 December 2019 20:27:57 UTC