Make DeviceOrientationEvent.prototype.absolute non-nullable

content/browser/device_sensors/data_fetcher_shared_memory_win.cc

Index: content/browser/device_sensors/data_fetcher_shared_memory_win.cc
diff --git a/content/browser/device_sensors/data_fetcher_shared_memory_win.cc b/content/browser/device_sensors/data_fetcher_shared_memory_win.cc
index 709c25b595c2b791df6ea7733f8828f47ba4c690..142de2cf47514f7efbb5c226ffcc2e19f05dbb85 100644
--- a/content/browser/device_sensors/data_fetcher_shared_memory_win.cc
+++ b/content/browser/device_sensors/data_fetcher_shared_memory_win.cc
@@ -130,7 +130,6 @@ class DataFetcherSharedMemory::SensorEventSinkOrientation
       buffer_->data.gamma = gamma;
       buffer_->data.hasGamma = has_gamma;
       buffer_->data.absolute = true;
-      buffer_->data.hasAbsolute = has_alpha || has_beta || has_gamma;

[philipj_slow, 2016/02/26 03:54:01]

Same as for Android, do you think I should make the above `has_alpha || has_beta
|| has_gamma` instead of true?

[timvolodine, 2016/03/01 22:36:25]

the spec doesn't really specify the value of absolute in case of a 'all-null'
event and I don't think it's important. However for consistency maybe do add
has_alpha || ... as you suggest to the absolute property above.

[philipj_slow, 2016/03/02 07:30:42]

This data comes directly from ISensorDataReport and I can't tell if it makes any
guarantees, but it seems possible in principle for all of these to be null.
Since the old code was defensive enough to check for it, I'll do it too.

       buffer_->data.allAvailableSensorsAreActive = true;
       buffer_->seqlock.WriteEnd();
     }