Remove 'drive-enabled-status-changed' event.
commit2ca7c971186207ce362fd3f7f60ecb9b5bc3973a
authorhidehiko@chromium.org <hidehiko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 17 Sep 2013 20:29:10 +0000 (17 20:29 +0000)
committerhidehiko@chromium.org <hidehiko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 17 Sep 2013 20:29:10 +0000 (17 20:29 +0000)
treebc686192bc043187429dbde402576c10309b1a47
parent751338aaf7f7700ea93be87e42b1886aa1b86695
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/23465019

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223674 0039d316-1c4b-4281-b951-d872f2087c98
chrome/browser/resources/file_manager/js/directory_model.js
chrome/browser/resources/file_manager/js/volume_manager.js