Enforce that BluetoothUUID.canonicalUUID() takes approximately an in-range integer.

Enforce that BluetoothUUID.canonicalUUID() takes approximately an in-range integer.

This was added to the spec in https://github.com/WebBluetoothCG/web-bluetooth/issues/133.

BUG=491441
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=198172

[Jeffrey Yasskin, 2015-07-01 21:25:02]

jyasskin@chromium.org changed reviewers:
+ ortuno@chromium.org, scheib@chromium.org

[Jeffrey Yasskin, 2015-07-01 21:25:03]

The behavior here is slightly odd. I've filed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28875 to fix it, but that may not
get in. Do we want the EnforceRange behavior even without that fix, or should we
wait and see?

[Jeffrey Yasskin, 2015-07-01 21:25:16]

The CQ bit was checked by jyasskin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-07-01 21:25:29]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1210173011/1

[scheib, 2015-07-01 21:45:34]

Some coverage is better than none. So I vote we take this.

Spec for canonicalUUID should be updated first, IMHO.

The inconsistency with getService()... is OK and we wait for
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28834 for those. Also, because of
the union types there we already see more type checking.

[scheib, 2015-07-01 22:43:30]

Hey look, the spec now includes this change. So LGTM.

[commit-bot: I haz the power, 2015-07-01 22:50:27]

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

[commit-bot: I haz the power, 2015-07-01 22:50:27]

Dry run: This issue passed the CQ dry run.

[Jeffrey Yasskin, 2015-07-01 23:08:54]

The CQ bit was checked by jyasskin@chromium.org

[commit-bot: I haz the power, 2015-07-01 23:09:09]

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

[commit-bot: I haz the power, 2015-07-01 23:12:53]

Committed patchset #1 (id:1) as
https://src.chromium.org/viewvc/blink?view=rev&revision=198172