diff options
author | hidehiko@chromium.org <hidehiko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-09-19 07:17:05 +0000 |
---|---|---|
committer | hidehiko@chromium.org <hidehiko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-09-19 07:17:05 +0000 |
commit | ffe5f04a17191bc87e448fa4f35bce5755d5061d (patch) | |
tree | 058fd6d1f6afe9b5c881fa8e69745f35f5d7015a /chromeos | |
parent | 771d18a11806d71ea2bb8961c884d7d2098e804f (diff) | |
download | chromium_src-ffe5f04a17191bc87e448fa4f35bce5755d5061d.zip chromium_src-ffe5f04a17191bc87e448fa4f35bce5755d5061d.tar.gz chromium_src-ffe5f04a17191bc87e448fa4f35bce5755d5061d.tar.bz2 |
Remove 'drive-enabled-status-changed' event.
Now, Drive's mounting state, including enable/disable state is managed by
DriveIntegrationService via VolumeManager in C++. So we don't need to track
it in Files.app in most cases.
This is the first CL to clean up js-code.
BUG=268817
TEST=Ran browser_tests --gtest_filter="*FileSystemExtensionApiTest*:*FileManagerBrowserTest*:*FileBrowserPrivateApiTest*" and tested manually.
Review URL: https://chromiumcodereview.appspot.com/23437043
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224072 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chromeos')
0 files changed, 0 insertions, 0 deletions