Geometry: Reimplement DOMPoint using V8 extras.

third_party/WebKit/Source/modules/vr/VREyeParameters.idl

Index: third_party/WebKit/Source/modules/vr/VREyeParameters.idl
diff --git a/third_party/WebKit/Source/modules/vr/VREyeParameters.idl b/third_party/WebKit/Source/modules/vr/VREyeParameters.idl
index 5a83da523d60fde77fc9ba7f8ce04db208d2f466..7d4747a06bff71deb5adca1792e6186918602c4e 100644
--- a/third_party/WebKit/Source/modules/vr/VREyeParameters.idl
+++ b/third_party/WebKit/Source/modules/vr/VREyeParameters.idl
@@ -11,9 +11,9 @@
   readonly attribute VRFieldOfView minimumFieldOfView;
   readonly attribute VRFieldOfView maximumFieldOfView;
   readonly attribute VRFieldOfView recommendedFieldOfView;
-  readonly attribute DOMPoint eyeTranslation;
+  [CallWith=ScriptState] readonly attribute any eyeTranslation;

[zino, 2016/02/18 16:25:33]

I used 'any' keyword but I'm not sure if this is a right way.

[domenic, 2016/02/18 19:04:41]

That has been what we have been doing so far, but as more V8 extras start
appearing we'll probably want to change the bindings generator in some way.
haraken@ might have more thoughts. Maybe for now it'd be worth adding a comment
like `// spec says DOMPoint, but we use any since it is implemented with V8
extras`

[zino, 2016/02/22 09:51:01]

Done.

 
   /* These values will vary after a FOV has been set */
   readonly attribute VRFieldOfView currentFieldOfView;
   readonly attribute DOMRect renderRect;
-};
+};