[sensors] Fix flakiness in generic sensors tests

third_party/WebKit/Source/modules/sensor/SensorProviderProxy.h

Index: third_party/WebKit/Source/modules/sensor/SensorProviderProxy.h
diff --git a/third_party/WebKit/Source/modules/sensor/SensorProviderProxy.h b/third_party/WebKit/Source/modules/sensor/SensorProviderProxy.h
index f328e7c378232d3416dce12d29cbaf951ef1eced..e9c770150757e30dc3a9077aaa27b01bb2b210d5 100644
--- a/third_party/WebKit/Source/modules/sensor/SensorProviderProxy.h
+++ b/third_party/WebKit/Source/modules/sensor/SensorProviderProxy.h
@@ -39,12 +39,14 @@ class SensorProviderProxy final
   DECLARE_VIRTUAL_TRACE();
 
  private:
-  friend class SensorProxy;  // To call sensorProvider().
+  friend class SensorProxy;  // To call getSensorProvider().

[Reilly Grant (use Gerrit), 2016/11/28 19:40:33]

If this class expects someone to call getSensorProvider() on it why isn't it a
public function?

[shalamov, 2016/11/29 09:02:23]

It is private just to make interaction between mojom::SensorProvider interface
and rest of the blink code little stricter / manageable. The SensorProxy is the
only class that can request sensor instance from the platform and all
communication with mojom::Sensor is done thru SensorProxy.

 
   explicit SensorProviderProxy(LocalFrame*);
   static const char* supplementName();
+  void initialize(LocalFrame*);
+  bool isInitialized() const { return m_sensorProvider; }
 
-  device::mojom::blink::SensorProvider* sensorProvider() const {
+  device::mojom::blink::SensorProvider* getSensorProvider() const {
     return m_sensorProvider.get();
   }