The arcTo method got updated in canvas v5 and adds a rotation argument (and thus radiusX and radiusY, too). void arcTo(double x1, double y1, double x2, double y2, double radiusX, double radiusY, double rotation); Spec: https://html.spec.whatwg.org/multipage/scripting.html#dom-context-2d-arcto Blink issue: https://code.google.com/p/chromium/issues/detail?id=277212 MDN: https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D.arcTo
Florian, you want to give this a try (as well)? In the spirit of "never let a good deed go unpunished" and your work on bug 1119527 :)
I had a look at this. The arcTo overload seems to hit bug 1020975. Apparently there has been a discussion about the name some time ago, but I don't see a resolution nor has the spec been changed since then. A thread proposing ellipseTo instead of 7-arg arcTo overload starts here: http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Sep/0220.html. I don't know what our opinion is here. There seems to be similar/duplicated code and I found bug 931587 which does some code cleaning. I guess it would be handy to have that first (as arcTo is present on CanvasRenderingContext2D and CanvasPath).
Since no one has implemented this after four years and its value isn't obvious, the Chrome team decided to WONTFIX their bug in March, and filed a motion to have it removed from the spec. That motion hasn't gone anywhere since (https://github.com/whatwg/html/issues/878), but I thought it bore mentioning in case this bug should likewise be WONTFIXed, or anyone here wanted to chime in to save the feature.
You need to log in before you can comment on or make changes to this bug.