Bluetooth API: add discovering changed events

chrome/browser/chromeos/extensions/bluetooth_event_router.cc

Index: chrome/browser/chromeos/extensions/bluetooth_event_router.cc
diff --git a/chrome/browser/chromeos/extensions/bluetooth_event_router.cc b/chrome/browser/chromeos/extensions/bluetooth_event_router.cc
index cfc13a55ac54e1682666d7df5c292ef793fcf6a4..a2101ebd7823d9ee1a1e65d7ecb4b2b43e17eb80 100644
--- a/chrome/browser/chromeos/extensions/bluetooth_event_router.cc
+++ b/chrome/browser/chromeos/extensions/bluetooth_event_router.cc
@@ -83,6 +83,14 @@ void ExtensionBluetoothEventRouter::AdapterPoweredChanged(
       has_power);
 }
 
+void ExtensionBluetoothEventRouter::AdapterDiscoveringChanged(
+    chromeos::BluetoothAdapter* adapter, bool discovering) {
+  DCHECK(adapter == adapter_.get());

[miket_OOO, 2012/07/24 16:58:50]

Sorry I'm late to this design party, but if this must be true, why have the
parameter in the signature at all?

[bryeung, 2012/07/24 17:02:09]

It has to be in the signature because it's an override.

There are cases, in general, where the adapter might not be the same.  But the
extension system only deals with the default adapter, so it should be true for
us.

Thinking about this more, maybe it should be an early NOP return if the adapters
don't match?

+  DispatchBooleanValueEvent(
+      extension_event_names::kBluetoothOnDiscoveringChanged,
+      discovering);
+}
+
 void ExtensionBluetoothEventRouter::DeviceAdded(
     chromeos::BluetoothAdapter* adapter, chromeos::BluetoothDevice* device) {
   if (!send_discovery_events_)