[whatwg] Rename the 7-arg arcTo() to ellipseTo()?

Rick Waldron waldron.rick at gmail.com
Mon Sep 24 06:59:09 PDT 2012

On Sun, Sep 23, 2012 at 11:25 PM, Tab Atkins Jr. <jackalmage at gmail.com>wrote:

> On Sun, Sep 23, 2012 at 3:57 PM, Ian Hickson <ian at hixie.ch> wrote:
> > On Fri, 21 Sep 2012, Tab Atkins Jr. wrote:
> >> So, can we rename the 7-arg arcTo to ellipseTo?  That seems to support
> >> your "always [require] all the arguments" recommendation. ^_^
> >
> > Just have one arcTo command, that takes all the arguments. Why split it
> > into two, if you always require all the arguments?
> Oh, that's what you meant.
> That seems silly.  It's more convenient and simple for authors to have
> a circular form, separate from the elliptical form.  It lets you omit
> the second radius and the rotation, as they're irrelevant.


Has there been any discussion about moving newly emerging APIs to a single
"options object" formal parameter?


> >> > In general, though, I wouldn't recommend trying to do this at all. The
> >> > SVG path syntax is its own thing, and it already supports arcs and so
> >> > forth. Adding a whole new redundant set of commands that work slightly
> >> > differently is just bloat asking for interop issues, IMHO. The design
> >> > of the path syntax makes sense, it's terse. Embrace its strengths,
> >> > don't second-guess its design.
> >>
> >> The existing SVG "A" command is one of the largest source of complaints
> >> from hand-authors. While it's *occasionally* useful as stated, it often
> >> requires you to do trig to get the effect you want. The Canvas arc
> >> commands, with their use of an angle to sweep across, are exactly what
> >> authors want a lot of the time, and commonly ask for.
> >
> > So introduce a new one-letter command that fixes specifically the
> problems
> > with A, don't drag in the entire canvas path API. :-)
> We're not, we're pulling in the two/four useful arc commands.
> ~TJ

More information about the whatwg mailing list