diff options
author | keybuk@chromium.org <keybuk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-21 02:37:42 +0000 |
---|---|---|
committer | keybuk@chromium.org <keybuk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-21 02:37:42 +0000 |
commit | 524203498d81fce05e2bd368f6c014e2a570b368 (patch) | |
tree | 770fca0731954ebdcb67f58c2e873e190dc3deb4 /testing/gtest_mac.mm | |
parent | e93a86a64fbc064c3e6e1d428d6cb5613ce25c46 (diff) | |
download | chromium_src-524203498d81fce05e2bd368f6c014e2a570b368.zip chromium_src-524203498d81fce05e2bd368f6c014e2a570b368.tar.gz chromium_src-524203498d81fce05e2bd368f6c014e2a570b368.tar.bz2 |
Bluetooth: remove DismissDisplayOrConfirm
This pairing delegate method never really made any sense, since the
outgoing call to Connect() has callbacks for the success and error
cases which indicate completion of the pairing and thus the right
point to hide down the dialog.
As part of the clean-up make the 'Accept' button return the dialog
to the 'Connecting...' state, as the 'Connect' button on the
PIN/Passkey prompts does, rather than closing the dialog.
This means that the positive buttons (Connect, Accept) keep the dialog
open, while the negative buttons (Cancel, Reject) dismiss the dialog.
Thus the API is now cleaner for implementing notifications/JavaScript.
BUG=338492
TEST=device_unittests, unit_tests, browser_tests and run through the
various 'fake' interactions
Review URL: https://codereview.chromium.org/172953006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252471 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'testing/gtest_mac.mm')
0 files changed, 0 insertions, 0 deletions