Chromium Code Reviews| Index: webkit/fileapi/isolated_mount_point_provider.cc |
| diff --git a/webkit/fileapi/isolated_mount_point_provider.cc b/webkit/fileapi/isolated_mount_point_provider.cc |
| index 160a71c189aeb5c2752402c8278d7139b49e7000..07771eb898b1ca4045f51c7670f379fcc0261ffe 100644 |
| --- a/webkit/fileapi/isolated_mount_point_provider.cc |
| +++ b/webkit/fileapi/isolated_mount_point_provider.cc |
| @@ -72,17 +72,6 @@ base::FilePath IsolatedMountPointProvider::GetFileSystemRootPathOnFileThread( |
| return base::FilePath(); |
| } |
| -bool IsolatedMountPointProvider::IsAccessAllowed(const FileSystemURL& url) { |
| - return true; |
| -} |
| - |
| -bool IsolatedMountPointProvider::IsRestrictedFileName( |
| - const base::FilePath& filename) const { |
| - // TODO(kinuko): We need to check platform-specific restricted file names |
| - // before we actually start allowing file creation in isolated file systems. |
| - return false; |
| -} |
| - |
| FileSystemFileUtil* IsolatedMountPointProvider::GetFileUtil( |
| FileSystemType type) { |
| switch (type) { |
| @@ -125,7 +114,7 @@ FilePermissionPolicy IsolatedMountPointProvider::GetPermissionPolicy( |
| const FileSystemURL& url, int permissions) const { |
| if (url.type() == kFileSystemTypeDragged && url.path().empty()) { |
| // The root directory of the dragged filesystem must be always read-only. |
| - if (permissions != kReadFilePermissions) |
| + if (permissions &~ fileapi::kReadFilePermissions) |
|
ericu
2013/02/05 21:51:57
Same again.
|
| return FILE_PERMISSION_ALWAYS_DENY; |
| } |
| // Access to isolated file systems should be checked using per-filesystem |