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

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.

-Boris

Received on Friday, 25 October 2013 02:08:04 UTC