1239142 - Implement 'arcs' value for 'stroke-linejoin' property

Status: NEW

(Core :: SVG, enhancement, P5)

Description

[Sebastian Zartner [:sebo]]

The SVG 2 spec. describes an 'arcs' value for the 'stroke-linejoin' property, which allows to an arcs corner to be used to join path segments.

Sebastian

Comment 1

[violet.bugreport]

The values miter-clip and arcs of the stroke-linejoin property are at risk. There are no known browser implementations. See issue Github issue #592.

https://svgwg.org/svg2-draft/painting.html#StrokeLinejoinProperty

Mark as P5 minor. Likely just a WONTFIX.

Comment 2

[Sebastian Zartner [:sebo]]

(In reply to violet.bugreport from comment #1)

The values miter-clip and arcs of the stroke-linejoin property are at risk. There are no known browser implementations. See issue Github issue #592.

https://svgwg.org/svg2-draft/painting.html#StrokeLinejoinProperty

Mark as P5 minor. Likely just a WONTFIX.

I am wondering why this was marked as P5 by you, violet.bugreport. Nothing personal, but I saw that you are rather new to Bugzilla and I guess not part of Mozilla staff and the note in the specification doesn't indicate any implementation priority, it just says that there are no implementations and therefore may be removed from the spec. at some point.
As I reported this more than three years ago and since then nobody picked it up, it obviously does have low priority for Mozilla, though it doesn't mean it's WONTFIX.

Anyway, I am not pushing on this feature, just wanting to get the priority clarified. Maybe Cameron can comment on this?

Sebastian

Comment 3

[violet.bugreport]

Nothing personal, but I saw that you are rather new to Bugzilla

Making judgments based on another user being "rather new" is personal, by the very definition of the word.

it just says that there are no implementations and therefore may be removed from the spec. at some point.
As I reported this more than three years ago and since then nobody picked it up, it obviously does have low priority for Mozilla

Ignoring de facto very low priority feature by not making the fact clear is detrimental to those who actually submit patches and implement features. Please take a look at some unfortunate situation like Bug 1318208, where some contributors spent a lot of time implementing an at-risk feature that finally turned out to be wasted effort.

I'm just a contributor here, if you disagree with some my action on some certain bug, feel free to revert them.

Comment 4

[Sebastian Zartner [:sebo]]

(In reply to violet.bugreport from comment #3)

Nothing personal, but I saw that you are rather new to Bugzilla

Making judgments based on another user being "rather new" is personal, by the very definition of the word.

Really didn't mean to, sorry!

it just says that there are no implementations and therefore may be removed from the spec. at some point.
As I reported this more than three years ago and since then nobody picked it up, it obviously does have low priority for Mozilla

Ignoring de facto very low priority feature by not making the fact clear is detrimental to those who actually submit patches and implement features. Please take a look at some unfortunate situation like Bug 1318208, where some contributors spent a lot of time implementing an at-risk feature that finally turned out to be wasted effort.

Good point! And a good example for how things should not end up.

And regarding the triage rules you're probably right with P5.

For reference, there is also a Chromium bug.

Sebastian

Comment 5

[Cameron McCormack (:heycam)]

I think this is fine as P5. It's not something we will prioritize over other P3 work.

Comment 6

[Amelia Bellamy-Royds]

An independent contributor, Skef Iterum, has prepared a patch for the Skia rendering engine that would support arc linejoins as a standard part of stroking. It's currently waiting on review: https://skia-review.googlesource.com/c/skia/+/303483

If that gets approved, the Chromium implementation will probably be fairly straightforward (since I think Chromium uses Skia everywhere). For Gecko, I assume you'd still need to decide how to handle platforms where the rendering engine doesn't have the feature.

See also discussion on the SVG WG list, about moving forward with this feature: https://lists.w3.org/Archives/Public/www-svg/2020Jul/0011.html