summaryrefslogtreecommitdiffstats
path: root/webkit/fileapi/isolated_context_unittest.cc
Commit message (Collapse)AuthorAgeFilesLines
* Add FilePath to base namespace.brettw@chromium.org2013-02-021-23/+23
| | | | | | | This updates headers that forward-declare it and a few random places to use the namespace explicitly. There us a using declaration in file_path.h that makes the rest compile, which we can do in future passes. Review URL: https://codereview.chromium.org/12163003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180245 0039d316-1c4b-4281-b951-d872f2087c98
* New FileSystemURL crackingtbarzic@chromium.org2013-01-241-1/+75
| | | | | | | | | | | | | | | | | | | follow up on https://codereview.chromium.org/11648027/ Instead of cracking FileSystemURL in its ctor (somewhat magically, using singleton IsolatedContext and SystemExternalMountPoints), require FileSystemURL to be cracked explicitly. The FileSystemURL can be cracked using specific MountPoints implementation or using specific FileSystemContext which will select available MountPoints implementation that should be used to crack the url. (CrackURL/CreateCrackedFileSystemURL methods). Modify FileSystemURL usages to use new cracking methods. BUG=158837 TEST=content_unittests: IsolatedContextTest.* ExternalMountPointsTest.* FileSystemContextTest.* Review URL: https://chromiumcodereview.appspot.com/11787028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@178664 0039d316-1c4b-4281-b951-d872f2087c98
* Extract external file systems handling from isolated context.tbarzic@chromium.org2013-01-181-6/+6
| | | | | | | | | | | | | | | Move mount point info bookeeping from CrosMountPointProvider to ExternalMountPoints. Add some tests for CrosMountPointProvider. BUG=158837 TEST=content_unittests:CrosMountPointProvider* TBR=benwells@chromium.org Review URL: https://chromiumcodereview.appspot.com/11648027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177578 0039d316-1c4b-4281-b951-d872f2087c98
* Lint fixes in webkit/fileapikinuko@chromium.org2012-10-291-2/+0
| | | | | | | | | | | | | | | | - add necessary std includes - TODO: -> TODO(user): - fix indentation / spacing / empty lines - avoid unnamed parameters - avoid non-recommended functions BUG=none TEST=existing tests Review URL: https://chromiumcodereview.appspot.com/11343005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@164620 0039d316-1c4b-4281-b951-d872f2087c98
* kFileSystemTypeIsolated should be only used in the URL exposed to rendererkinuko@chromium.org2012-08-271-4/+4
| | | | | | | | | | | Also added verbose description in file_system_types.h. BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/10879002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153498 0039d316-1c4b-4281-b951-d872f2087c98
* Add RevokeFileSystem back to IsolatedContextkinuko@chromium.org2012-08-131-1/+17
| | | | | | | | | | | | We deprecated it when we added RevokeFileSystemByPath but it looks we still want it. BUG=none TEST=IsolatedContextTest.RegisterAndRevokeTest Review URL: https://chromiumcodereview.appspot.com/10837217 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151256 0039d316-1c4b-4281-b951-d872f2087c98
* Adding RevokeFileSystemByPathkinuko@chromium.org2012-08-021-5/+28
| | | | | | | | | | | so that we can make sure we invalidate all file systems associated to a given path (e.g. for a detached device) BUG=none TEST=IsolatedContextTest.* Review URL: https://chromiumcodereview.appspot.com/10829136 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149732 0039d316-1c4b-4281-b951-d872f2087c98
* Enables internal filesystem types via Isolated filesystems.kinuko@chromium.org2012-07-251-9/+7
| | | | | | | | | | | | | | * cracks isolated path in FileSystemURL ctor * FileUtils no longer need to crack the isolated path by themselves * Make IsolatedFileUtil inherit from LocalFileUtil * Have a separate FileUtil for DraggedFileUtil, which inherits from IsolatedFileUtil BUG=134078,138022 TEST=existing tests Review URL: https://chromiumcodereview.appspot.com/10810053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148440 0039d316-1c4b-4281-b951-d872f2087c98
* Add more FS types and introduce type field into IsolatedContextkinuko@chromium.org2012-07-251-11/+24
| | | | | | | | | | | (Separated from a bigger patch: https://chromiumcodereview.appspot.com/10810053) BUG=138022 TEST=existing tests Review URL: https://chromiumcodereview.appspot.com/10817006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148291 0039d316-1c4b-4281-b951-d872f2087c98
* Make isolated file system works for a device root (e.g. X:\\)kinuko@chromium.org2012-07-101-34/+48
| | | | | | | | | | | | | * directory drag-and-drop should work for a USB drive etc * Media device intent should work on Windows BUG=134828,135010 TEST=manually tested TEST=IsolatedContext\* Review URL: https://chromiumcodereview.appspot.com/10713007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145862 0039d316-1c4b-4281-b951-d872f2087c98
* Remove ugly writable flags from IsolatedContextkinuko@chromium.org2012-06-301-24/+0
| | | | | | | | | | | | | | For regular chrome centralize the read/write permission to ChildProcessSecurityPolicy and do nothing in fileapi layer. For DRT/content_shell disable writes at SimpleFileSystem layer as well as we do in FileAPIMessageFilter for chrome. BUG=none TEST=existing tests TEST=layout tests https://bugs.webkit.org/show_bug.cgi?id=89981 Review URL: https://chromiumcodereview.appspot.com/10692005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145063 0039d316-1c4b-4281-b951-d872f2087c98
* Retry: Make Isolated file system writable only if it is configured sokinuko@chromium.org2012-06-121-0/+24
| | | | | | | | | | | | | | - CreateFileStreamWriter wiring in FSO - Add yet another write-protection at IsolatedContext (in addition to ChildProcessSecurityPolicy, so that we can make each fs read-only or writable in DRT/testing) BUG=none TEST=existing tests should pass Original review URL: https://chromiumcodereview.appspot.com/10540070 Review URL: https://chromiumcodereview.appspot.com/10532085 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141650 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 141395 - Make Isolated file system writable only if it is configured sokinuko@chromium.org2012-06-111-24/+0
| | | | | | | | | | | | | | | - Use CreateFileStreamWriter in FSO - Add yet another write-protection at IsolatedContext (in addition to ChildProcessSecurityPolicy, so that we can make each fs read-only or writable in DRT/testing) BUG=none TEST=none (will add layout_test) Review URL: https://chromiumcodereview.appspot.com/10540070 TBR=kinuko@chromium.org Review URL: https://chromiumcodereview.appspot.com/10534088 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141398 0039d316-1c4b-4281-b951-d872f2087c98
* Make Isolated file system writable only if it is configured sokinuko@chromium.org2012-06-111-0/+24
| | | | | | | | | | | | - Use CreateFileStreamWriter in FSO - Add yet another write-protection at IsolatedContext (in addition to ChildProcessSecurityPolicy, so that we can make each fs read-only or writable in DRT/testing) BUG=none TEST=none (will add layout_test) Review URL: https://chromiumcodereview.appspot.com/10540070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141395 0039d316-1c4b-4281-b951-d872f2087c98
* Add isolated file_util for directory (and file) drag-and-drop support.kinuko@chromium.org2012-04-021-8/+12
| | | | | | | | | | | patch from http://codereview.chromium.org/9204009/ BUG=99823 TEST=test_shell_tests:IsolatedFileUtil* Review URL: https://chromiumcodereview.appspot.com/9272007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130110 0039d316-1c4b-4281-b951-d872f2087c98
* Define FilePath::NormalizePathSeparators on all platformskinuko@chromium.org2012-02-101-11/+5
| | | | | | | | | | | | | I assume the method FilePath::NormalizeWindowsPathSeparators() is intentionally defined only on Windows, but recently I found myself trying to add a static method (named NormalizePathSeparators()) which calls NormalizeWindowsPathSeparators() or does nothing with platform ifdefs, and then found that there's another place defining the same static method. Maybe we could just add the common method in FilePath then? It'd at least make the code cleaner at several callsites. I don't think this has visible negative performance impact with optimization build. BUG=none TEST=FilePathTest.NormalizePathSeparators and all other existing tests Review URL: https://chromiumcodereview.appspot.com/9320059 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121380 0039d316-1c4b-4281-b951-d872f2087c98
* IsolatedContext test fix for Windowskinuko@chromium.org2012-02-061-29/+26
| | | | | | | | | BUG=none TEST=IsolatedContext.* Review URL: https://chromiumcodereview.appspot.com/9323013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120549 0039d316-1c4b-4281-b951-d872f2087c98
* Mark IsolatedContext tests failing on Windowskinuko@chromium.org2012-02-031-3/+19
| | | | | | | | | | BUG=112568 TEST=green bots TBR=ahendrickson Review URL: https://chromiumcodereview.appspot.com/9310078 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120273 0039d316-1c4b-4281-b951-d872f2087c98
* Add isolated filesystem context for directory (and file) drag-and-drop support.kinuko@chromium.org2012-02-021-0/+157
- Adding IsolatedContext class which keeps track of the isolated filesystem namespaces for dropped files/directories - Adding WebDropData.filesystem_id to send the filesystem ID to the renderer - Adding GrantAccessFileSystem() method to ChildProcessSecurityPolicy (the permission is to be revoked when the child goes away) design doc (internal): https://docs.google.com/a/google.com/document/d/1hSdCHy7qWXYSp9nlUT7JJd5Jli_fMWQxgyQBM1GhRVk/edit?hl=en_US BUG=99823 TEST=test_shell_tests:IsolatedContextTest* Review URL: https://chromiumcodereview.appspot.com/9204009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120178 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2024-09-17 21:35:55 +0000