bluetooth: Remove BluetoothDevice.paired

bluetooth: Remove BluetoothDevice.paired

It looks like CoreBluetooth has no way to get this information, so we can't expose it universally. It's a holdover from chrome.bluetooth.

BUG=421668
Committed: https://crrev.com/612a2f8cdee39bd57a9cc214c744ece855e2813d
Cr-Commit-Position: refs/heads/master@{#368605}

[fbeaufortchromium, 2016-01-07 12:31:02]

Description was changed from

==========
bluetooth: Remove BluetoothDevice.paired

BUG=421668
==========

to

==========
bluetooth: Remove BluetoothDevice.paired

It looks like CoreBluetooth has no way to get this information, so we can't
expose it universally. It's a holdover from chrome.bluetooth.

BUG=421668
==========

[fbeaufortchromium, 2016-01-07 12:38:01]

fbeaufort@chromium.org changed reviewers:
+ fbeaufort@chromium.org, jyasskin@chromium.org

[fbeaufortchromium, 2016-01-07 12:38:01]

Hey Jeffrey, can you have a look at this CL?

I think I'm missing some owners... who would you recommend?

[Jeffrey Yasskin, 2016-01-09 00:43:23]

jyasskin@chromium.org changed reviewers:
+ ortuno@chromium.org
- fbeaufort@chromium.org

[Jeffrey Yasskin, 2016-01-09 00:43:23]

LGTM. +Giovanni as an FYI.

[fbeaufortchromium, 2016-01-11 10:44:57]

The CQ bit was checked by fbeaufort@chromium.org

[commit-bot: I haz the power, 2016-01-11 10:45:18]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1564953003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1564953003/1

[commit-bot: I haz the power, 2016-01-11 10:52:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-11 10:52:47]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[fbeaufortchromium, 2016-01-11 10:54:07]

fbeaufort@chromium.org changed reviewers:
+ tsepez@chromium.org

[fbeaufortchromium, 2016-01-11 10:54:08]

tsepez@chromium.org: Please review changes in
content/common/bluetooth/bluetooth_messages.h

[Tom Sepez, 2016-01-11 16:51:51]

RS LGTM on deleting a member.

[François Beaufort, 2016-01-11 16:53:58]

The CQ bit was checked by beaufort.francois@gmail.com

[commit-bot: I haz the power, 2016-01-11 16:54:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1564953003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1564953003/1

[commit-bot: I haz the power, 2016-01-11 16:59:35]

Description was changed from

==========
bluetooth: Remove BluetoothDevice.paired

It looks like CoreBluetooth has no way to get this information, so we can't
expose it universally. It's a holdover from chrome.bluetooth.

BUG=421668
==========

to

==========
bluetooth: Remove BluetoothDevice.paired

It looks like CoreBluetooth has no way to get this information, so we can't
expose it universally. It's a holdover from chrome.bluetooth.

BUG=421668
==========

[commit-bot: I haz the power, 2016-01-11 16:59:35]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-11 17:00:32]

Description was changed from

==========
bluetooth: Remove BluetoothDevice.paired

It looks like CoreBluetooth has no way to get this information, so we can't
expose it universally. It's a holdover from chrome.bluetooth.

BUG=421668
==========

to

==========
bluetooth: Remove BluetoothDevice.paired

It looks like CoreBluetooth has no way to get this information, so we can't
expose it universally. It's a holdover from chrome.bluetooth.

BUG=421668

Committed: https://crrev.com/612a2f8cdee39bd57a9cc214c744ece855e2813d
Cr-Commit-Position: refs/heads/master@{#368605}
==========

[commit-bot: I haz the power, 2016-01-11 17:00:33]

Patchset 1 (id:??) landed as
https://crrev.com/612a2f8cdee39bd57a9cc214c744ece855e2813d
Cr-Commit-Position: refs/heads/master@{#368605}

[ortuno, 2016-01-11 20:36:13]

In the future it would be nice if changes like this had a corresponding change
in the spec. If we change our implementation without changing the spec people
are going to run into different behavior in each browser.

[fbeaufortchromium, 2016-01-12 12:16:36]

On 2016/01/11 20:36:13, ortuno (OOO until Jan 10th) wrote:
> In the future it would be nice if changes like this had a corresponding change
> in the spec. If we change our implementation without changing the spec people
> are going to run into different behavior in each browser.

There is already one: https://github.com/WebBluetoothCG/web-bluetooth/issues/189