Fix default initialization for DeviceMotionEvent.interval.

third_party/WebKit/Source/modules/device_orientation/DeviceMotionEvent.cpp

Index: third_party/WebKit/Source/modules/device_orientation/DeviceMotionEvent.cpp
diff --git a/third_party/WebKit/Source/modules/device_orientation/DeviceMotionEvent.cpp b/third_party/WebKit/Source/modules/device_orientation/DeviceMotionEvent.cpp
index 1975a4963a52b3e27bd5563f661f5d9e91a12a8c..ec5505cded9ee941b1200598d5cd20164fbd3111 100644
--- a/third_party/WebKit/Source/modules/device_orientation/DeviceMotionEvent.cpp
+++ b/third_party/WebKit/Source/modules/device_orientation/DeviceMotionEvent.cpp
@@ -81,11 +81,7 @@ DeviceRotationRate* DeviceMotionEvent::rotationRate() {
 }
 
 double DeviceMotionEvent::interval(bool& isNull) const {
-  if (m_deviceMotionData->canProvideInterval())
-    return m_deviceMotionData->interval();
-
-  isNull = true;
-  return 0;
+  return m_deviceMotionData->interval();

[timvolodine, 2017/03/22 17:05:27]

isNull = false; ?

also likely the isNull etc can be removed altogether if the idl is updated..
maybe a follow-up patch?

[Reilly Grant (use Gerrit), 2017/03/22 17:13:33]

The generated bindings code initializes isNull to false before calling this
function.

I have submitted a pull request to the deviceorientation spec which makes this
attribute non-nullable.

[timvolodine, 2017/03/22 18:27:26]

In that case perhaps add a this as a comment? Otherwise think not very clear
what happens with this by reference parameter (and why it's needed at all)
yes, thanks, I've merged it.

[Reilly Grant (use Gerrit), 2017/03/22 18:38:03]

It is required by the bindings code because the attribute is nullable. I've
added a line to explicitly set it to false though my next patch will delete it
since it changes the IDL to make the attribute non-nullable.

 }
 
 const AtomicString& DeviceMotionEvent::interfaceName() const {