W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2012

Re: [whatwg] canvas miterLimit property

From: Rik Cabanier <cabanier@gmail.com>
Date: Tue, 11 Sep 2012 11:30:21 +0200
Message-ID: <CAGN7qDB3P18XSdwU_yxygtXU3c6fOKBQ4Wrsq=OO8ZKd3o3HRQ@mail.gmail.com>
To: Michael Day <mikeday@yeslogic.com>
Cc: whatwg@lists.whatwg.org
Good catch!
I'm unsure why SVG is different.

This is a problem with the new Path object [1] that takes an SVG path
string. A user will have to remember to set the miter limit to the SVG
default otherwise the path might render differently in Canvas.
If we ever harmonize the path object so it can be shared by SVG and Canvas,
we will need to account for this.

Rik

1:
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#path

On Tue, Sep 11, 2012 at 9:11 AM, Michael Day <mikeday@yeslogic.com> wrote:

> Hi,
>
> The canvas miterLimit property has a default value of 10, while the SVG
> stroke-miterlimit property has a default value of 4. Is there a reason for
> this inconsistency?
>
> For reference, the PDF rendering model also has a default value of 10 for
> miterLimit, making SVG apparently the odd one out here.
>
> Cheers,
>
> Michael
>
Received on Tuesday, 11 September 2012 09:30:58 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:45 UTC