Extract external file systems handling from isolated context.

webkit/fileapi/file_system_types.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef WEBKIT_FILEAPI_FILE_SYSTEM_TYPES_H_
 #define WEBKIT_FILEAPI_FILE_SYSTEM_TYPES_H_
 
 #include "third_party/WebKit/Source/WebKit/chromium/public/platform/WebFileSystem.h"
 
 namespace fileapi {
@@ skipping 39 matching lines @@
 
   // Indicates a local filesystem where we can access files using native
   // local path.
   kFileSystemTypeNativeLocal,
 
   // Indicates a local filesystem where we can access files using native
   // local path, but with restricted access.
   // Restricted native local file system is in read-only mode.
   kFileSystemTypeRestrictedNativeLocal,
 
+  // Indicates a isolated local filesystem where we can access files using
+  // native local path.
+  kFileSystemTypeIsolatedNativeLocal,

[kinuko, 2013/01/09 16:37:12]

Why do we need this separate type?

[tonibarzic, 2013/01/09 17:09:46]

I don't think we need.. I wanted to check something and forgot to undo this
change  before upload

+
   // Indicates a transient, isolated file system for dragged files (which could
   // contain multiple dragged paths in the virtual root).
   kFileSystemTypeDragged,
 
   // Indicates media filesystem which we can access with same manner to
   // regular filesystem.
   kFileSystemTypeNativeMedia,
 
   // Indicates media filesystem to which we need special protocol to access,
   // such as MTP or PTP.
   kFileSystemTypeDeviceMedia,
 
   // Indicates a Drive filesystem which provides access to Google Drive.
   kFileSystemTypeDrive,
 
   // Indicates a Syncable sandboxed filesystem which can be backed by a
   // cloud storage service.
   kFileSystemTypeSyncable,
 };
 
 }  // namespace fileapi
 
 #endif  // WEBKIT_FILEAPI_FILE_SYSTEM_TYPES_H_