W3C home > Mailing lists > Public > www-svg@w3.org > October 2013

Re: Missing values in SVGPathElement API: What to do?

From: Dirk Schulze <dschulze@adobe.com>
Date: Thu, 24 Oct 2013 20:06:40 -0700
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: "www-svg@w3.org" <www-svg@w3.org>
Message-ID: <B09B43DC-4426-4919-B6C3-73AADF6BBB4D@adobe.com>

On Oct 24, 2013, at 7:07 PM, Boris Zbarsky <bzbarsky@MIT.EDU> wrote:

> On 10/24/13 11:33 AM, Stephen Chenney wrote:
>> I just came across some undefined behavior in the spec that could easily
>> be defined. An example is the
>> http://www.w3.org/TR/SVG/paths.html#InterfaceSVGPathElement spec. It has
>> absolutely nothing to say about cases where the calling script does not
>> provide all of the necessary parameters.
> As Cameron noted, WebIDL requires this method to throw if too few 
> arguments are passed, so to the extent that the spec is defined with 
> WebIDL the behavior is completely defined.
> A related question is what should happen if undefined is passed for some 
> of the arguments.
> See also https://www.w3.org/bugzilla_public/show_bug.cgi?id=23532 for 
> some interesting discussion.

Well, it uses float and not unrestricted float. Therefore NaN values shouldn’t be accepted. Am I wrong?


> -Boris
Received on Friday, 25 October 2013 03:07:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:46 UTC