summaryrefslogtreecommitdiffstats
path: root/device/bluetooth/bluetooth_gatt_service.h
diff options
context:
space:
mode:
authortim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-07-30 01:20:51 +0000
committertim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-07-30 01:20:51 +0000
commitc8c1c1fc1371d366b338136d657ac8998070fc91 (patch)
treebc30aed72d9400792c66cb63cb6e38f39961b8ce /device/bluetooth/bluetooth_gatt_service.h
parent7c3775573dcc149a3fd34d15063de5ffd0c1ae6c (diff)
downloadchromium_src-c8c1c1fc1371d366b338136d657ac8998070fc91.zip
chromium_src-c8c1c1fc1371d366b338136d657ac8998070fc91.tar.gz
chromium_src-c8c1c1fc1371d366b338136d657ac8998070fc91.tar.bz2
mojo: shell::Context should outlive the shell MessageLoop
Make sure tests and mojo_mains all work the same way by handing control of MessageLoops in test to ShellTest{Base, Helper}. This ensures Applications that live as part of the shell (ViewManager) can rely on MessageLoop destruction happening first (before their own destruction) for cleaning up, similar to how this typically works for real apps (mojo_main_{chromium, standalone}. BUG=394477 Review URL: https://codereview.chromium.org/420143003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@286370 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'device/bluetooth/bluetooth_gatt_service.h')
0 files changed, 0 insertions, 0 deletions