Updating the GATT connection device address when it changes.

device/bluetooth/bluetooth_gatt_connection_chromeos.cc

Index: device/bluetooth/bluetooth_gatt_connection_chromeos.cc
diff --git a/device/bluetooth/bluetooth_gatt_connection_chromeos.cc b/device/bluetooth/bluetooth_gatt_connection_chromeos.cc
index b0551cff1dc16295e7f991ee756e9cbd13568087..7dd8bdc7f33c7a3c6edabc9a2292fdece960129a 100644
--- a/device/bluetooth/bluetooth_gatt_connection_chromeos.cc
+++ b/device/bluetooth/bluetooth_gatt_connection_chromeos.cc
@@ -99,6 +99,11 @@ void BluetoothGattConnectionChromeOS::DevicePropertyChanged(
   if (property_name == properties->connected.name() &&
       !properties->connected.value())
     connected_ = false;
+
+  // The remove device's bluetooth address may change if it is paired while

[armansito, 2015/09/23 06:46:59]

nit: "The removed device's.."

[sacomoto, 2015/09/23 11:27:41]

Done.

+  // connected.
+  if (property_name == properties->address.name())
+    device_address_ = properties->address.value();

[armansito, 2015/09/23 06:46:59]

Won't you need to update the BluetoothDevice object as well?

[sacomoto, 2015/09/23 11:27:41]

No. Only the DBus |object_path_| (not changed when a device is paired) is cached
on the BluetoothDevice object. The address is queried from the DBus API using
the |object_path_|.

On the other hand, the |DeviceMap| on the BluetoothAdapter should be updated
(see crbug.com/507699 and crbug.com/497841). I'll fix it in a next CL.

 }
 
 }  // namespace chromeos