Replace sets with vectors when storing file handlers.

chrome/browser/chromeos/extensions/file_manager/file_browser_handler.cc

Index: chrome/browser/chromeos/extensions/file_manager/file_browser_handler.cc
diff --git a/chrome/browser/chromeos/extensions/file_manager/file_browser_handler.cc b/chrome/browser/chromeos/extensions/file_manager/file_browser_handler.cc
index e145b76f8c3f04151b867950b08846840b2f4d43..c946103e6921d9ffc9c1cfb7ca3aadf563415f9f 100644
--- a/chrome/browser/chromeos/extensions/file_manager/file_browser_handler.cc
+++ b/chrome/browser/chromeos/extensions/file_manager/file_browser_handler.cc
@@ -182,12 +182,11 @@ FileBrowserHandler* LoadFileBrowserHandler(
   }
 
   // Initialize file filters (mandatory, unless "create" access is specified,
-  // in which case is ignored).
+  // in which case is ignored). The list can be empty.
   if (!result->HasCreateAccessPermission()) {
     const ListValue* file_filters = NULL;
     if (!file_browser_handler->HasKey(keys::kFileFilters) ||
-        !file_browser_handler->GetList(keys::kFileFilters, &file_filters) ||
-        file_filters->empty()) {

[hashimoto, 2013/05/24 11:15:51]

You are going to change the behavior of a public API.
(http://developer.chrome.com/extensions/fileBrowserHandler.html)
I don't think allowing empty file filters as an alternative to "filesystem:*" is
a good idea, can't we go as strict as possible?

[mtomasz, 2013/05/27 01:20:20]

I don't think it changes the api. This change allows an empty list, which is not
forbidden in the provided link.

Empty filter list means that this handler does handle any specific files. It is
used internally only.

+        !file_browser_handler->GetList(keys::kFileFilters, &file_filters)) {
       *error = ASCIIToUTF16(errors::kInvalidFileFiltersList);
       return NULL;
     }