[Device Sensors] Remove BrowserThread knowledge

content/browser/device_sensors/device_sensor_host.cc

Index: content/browser/device_sensors/device_sensor_host.cc
diff --git a/content/browser/device_sensors/device_sensor_host.cc b/content/browser/device_sensors/device_sensor_host.cc
index f3812ceec0bc2a7b55d10e4c3f3edab01db118eb..76096def5fbf1538416649e32cb2e7add8753a69 100644
--- a/content/browser/device_sensors/device_sensor_host.cc
+++ b/content/browser/device_sensors/device_sensor_host.cc
@@ -4,8 +4,8 @@
 
 #include "content/browser/device_sensors/device_sensor_host.h"
 
+#include "base/message_loop/message_loop.h"
 #include "content/browser/device_sensors/device_sensor_service.h"
-#include "content/public/browser/browser_thread.h"

[timvolodine, 2016/11/10 16:43:04]

actually a question: so we can depend on content/public/browser in components/
but not in device/ ?

[blundell, 2016/11/15 09:09:09]

Yes, essentially. Individual components make their own decisions on whether it's
legal for them to depend on //content depending on their use case (e.g., are
they intended for use on iOS, which doesn't use //content). All of //device is
lower-level than //content.

 #include "mojo/public/cpp/bindings/strong_binding.h"
 
 namespace content {
@@ -22,9 +22,9 @@ template <typename MojoInterface, ConsumerType consumer_type>
 DeviceSensorHost<MojoInterface, consumer_type>::DeviceSensorHost()
     : is_started_(false) {
 #if defined(OS_ANDROID)
-  DCHECK_CURRENTLY_ON(BrowserThread::UI);
+  DCHECK(base::MessageLoopForUI::IsCurrent());
 #else
-  DCHECK_CURRENTLY_ON(BrowserThread::IO);
+  DCHECK(base::MessageLoopForIO::IsCurrent());
 #endif
 }