Sync the DOM* geometry interfaces with the spec

Source/core/dom/DOMPoint.idl

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
+// http://dev.w3.org/fxtf/geometry/#DOMPoint
+
 [
     Constructor(optional DOMPointInit point),
+    // FIXME: The x and y arguments should be optional (See: crbug.com/462098)

[zino, 2015/02/26 12:11:32]

I'm not sure but it seems to be spec[1] bug(?).

Constructor(optional DOMPointInit point)
 - Constructor() -> **conflict**
 - Constructor(DOMPointInit point)

Constructor(optional unrestricted double x, optional unrestricted double y, ...)
 - Constructor() -> **conflict**
 - Constructor(x)
 - Constructor(x, y)
 - ...

I didn't find the case of non-parameter like this situation in web-idl spec[2]
but I believe the two constructors are not distinguishable.

[1] http://dev.w3.org/fxtf/geometry/
[2] http://www.w3.org/TR/2012/CR-WebIDL-20120419/#distinguishable-table

[zino, 2015/02/26 13:51:15]

Hi @haraken,

Could you please take a look?

[Jens Widell, 2015/02/26 14:02:56]

It's a spec bug, alright. WebIDL doesn't allow (among other things) two
overloads that support being called with zero arguments.

The most natural fix IMO would be to make the DOMPointInit argument
non-optional, and leave all the coordinate arguments to the other constructor
optional (with default values.)

     Constructor(unrestricted double x, unrestricted double y,
                 optional unrestricted double z = 0, optional unrestricted double w = 1),
+    // FIXME: Exposed=(Window,Worker)
     RuntimeEnabled=GeometryInterfaces,
 ] interface DOMPoint : DOMPointReadOnly {
+    // FIXME: The attributes should have the inherit keyword (See: crbug.com/462097)
     attribute unrestricted double x;
     attribute unrestricted double y;
     attribute unrestricted double z;
     attribute unrestricted double w;
 };