| commit | ffb8706267743f92faa5314e1e61c7c76c65e0dd | |
| author | sammc@chromium.org <sammc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 29 Aug 2013 10:02:25 +0000 (29 10:02 +0000) | ||
| committer | sammc@chromium.org <sammc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 29 Aug 2013 10:02:25 +0000 (29 10:02 +0000) | ||
| tree | 4aa4841c888e7fb0a518850d9b383506a693b75e | treesnapshot (tar.gz zip) |
| parent | a39dcb42c9cc46fa6598744d043f3461c542d967 | commitdiff |
Use only app permissions to decide if file entries should be writable.
Previously, apps with the fileSystem.write permission could choose to
obtain read-only files and file entries provided as launch data were
always read-only.
With this change, all file entries obtained using the chrome.fileSystem
API or provided as launch data are writable, for apps with the
fileSystem.write permission.
This makes getWritableEntry unnecessary, other than for files obtained
through other means (e.g., drag and drop).
BUG=148486
Review URL: https://chromiumcodereview.appspot.com/23202006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220254 0039d316-1c4b-4281-b951-d872f2087c98
Previously, apps with the fileSystem.write permission could choose to
obtain read-only files and file entries provided as launch data were
always read-only.
With this change, all file entries obtained using the chrome.fileSystem
API or provided as launch data are writable, for apps with the
fileSystem.write permission.
This makes getWritableEntry unnecessary, other than for files obtained
through other means (e.g., drag and drop).
BUG=148486
Review URL: https://chromiumcodereview.appspot.com/23202006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220254 0039d316-1c4b-4281-b951-d872f2087c98
24 files changed: