Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 2:16 PM, Rik Cabanier wrote: > > > On Mon, Nov 16, 2015 at 10:54 AM, Justin Novosad wrote: > >> >> >> On Mon, Nov 16, 2015 at 1:40 PM, Rik Cabanier wrote: >> >>> >>> >>> On Mon, Nov 16, 2015 at 9:41 AM, Justin Novosad >>> wrote: >>> Also, the part about "repeating

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 10:54 AM, Justin Novosad wrote: > > > On Mon, Nov 16, 2015 at 1:40 PM, Rik Cabanier wrote: > >> >> >> On Mon, Nov 16, 2015 at 9:41 AM, Justin Novosad wrote: >> >>> Also, the part about "repeating the last (possibly implied) moveTo() >>> call" doesn't make much sense if w

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 1:40 PM, Rik Cabanier wrote: > > > On Mon, Nov 16, 2015 at 9:41 AM, Justin Novosad wrote: > >> Also, the part about "repeating the last (possibly implied) moveTo() >> call" doesn't make much sense if we assume that closePath() applies to the >> new sub path that was start

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 9:41 AM, Justin Novosad wrote: > Also, the part about "repeating the last (possibly implied) moveTo() call" > doesn't make much sense if we assume that closePath() applies to the new > sub path that was started by the last moveTo() call. > It *is* super confusing. I compl

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

Also, the part about "repeating the last (possibly implied) moveTo() call" doesn't make much sense if we assume that closePath() applies to the new sub path that was started by the last moveTo() call. On Mon, Nov 16, 2015 at 12:38 PM, Justin Novosad wrote: > That makes sense, but the text for cl

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

That makes sense, but the text for closePath() talks about "the last subpath", which I guess is a bit unclear. On Mon, Nov 16, 2015 at 12:30 PM, Rik Cabanier wrote: > > > On Mon, Nov 16, 2015 at 9:02 AM, Justin Novosad wrote: > >> Hi All, >> >> The text in the spec: >> >> >> >> The closePath()

Re: [whatwg] Interpretation of CanvasRenderingContext2D.closePath()

On Mon, Nov 16, 2015 at 9:02 AM, Justin Novosad wrote: > Hi All, > > The text in the spec: > > > > The closePath() method must do nothing if the object's path has no > subpaths. Otherwise, it must mark the last subpath as closed, create a new > subpath whose first point is the same as the previo

[whatwg] Interpretation of CanvasRenderingContext2D.closePath()

Hi All, The text in the spec: The closePath() method must do nothing if the object's path has no subpaths. Otherwise, it must mark the last subpath as closed, create a new subpath whose first point is the same as the previous subpath's first point, and finally add this new subpath to the path.