html5-filesystem

问题 I am trying to create a file using the File system API..i googled and i get a code function onFs(fs) { fs.root.getFile('log.txt', {create: true, exclusive: true}, function(fileEntry) { fileEntry.getMetaData(function(md) { }, onError); }, onError ); } window.requestFileSystem(TEMPORARY, 1024*1024 /*1MB*/, onFs, onError); can any one say what is the fs which is passed as function argument.. Please refer me a good example... 回答1: fs is a javascript object that allows you to make "system-like"

问题 I have the following code: chrome.runtime.getPackageDirectoryEntry(function(directoryEntry) { directoryEntry.getFile("files/test.txt", {create: true, exclusive: false}, function(fileEntry) { console.log(fileEntry); }, function(error) { console.log(error); }); }); If the file does not exist and create is true I get an It was determined that certain files are unsafe for access within a Web application, or that too many calls are being made on file resources. error. But if it does exist and

问题 I have the following code: chrome.runtime.getPackageDirectoryEntry(function(directoryEntry) { directoryEntry.getFile("files/test.txt", {create: true, exclusive: false}, function(fileEntry) { console.log(fileEntry); }, function(error) { console.log(error); }); }); If the file does not exist and create is true I get an It was determined that certain files are unsafe for access within a Web application, or that too many calls are being made on file resources. error. But if it does exist and

问题 I'm writing a web browser app (client-side) that downloads a huge amount of chunks from many locations and joins them to build a blob. Then that blob is saved to local filesystem as a common file. The way I'm doing this is by mean of ArrayBuffer objects and a blob. var blob = new Blob([ArrayBuffer1, ArrayBuffer2, ArrayBuffer3, ...], {type: mimetype}) This works ok for small and medium-sized files (until 700 MB aprox), but browser crashes with larger files. I understand that RAM memory has its

问题 I'm working on a webapp and I'm trying to access directories using the filesystem API. I need to request a quota from the user before accessing the directories according to specification. I should do something like this: ... navigator.webkitPersistentStorage.requestQuota(PERSISTENT, 1024*1024, function(gB){ window.requestFileSystem(PERSISTENT, gB, onInitFs, errorHandler); }, function(e){ console.log('Error', e); }) ... Everytime I do this I get a **TypeError: Type error** message. Please what

问题 I'm writing an extension that would ideally read files after they are downloaded (through the normal download process). Is that possible? I can get the filename through chrome.downloads operations, but I can't find ways of reading the actual bytes. I don't need to write or move them, just read. 回答1: I struggled with the exact same problem and finally found an easy workaround to read the content of downloaded files from a Chrome extension. You just need to add a permission to file://* in your

问题 I'm writing an HTML5 app to run in Chrome but it will be on the local filesystem (so they'll start it by double-clicking an html file). It is throwing an error when I try to access the filesystem and I think it's because it's a local file. Is there a way to make Chrome allow this? (NOTE: I do get the popup asking me to allow the app to store permanantly and I click "OK". It still throws this error) The below code throws the error: DOMException {message: "NotSupportedError: DOM Exception 9",

问题 I loaded a directory using file input and webkitdirectory as mentioned below. <input id="file_input" type="file" webkitdirectory directory /> After directory selected I can read file size and other information. My question is how to read this directory using DirectoryReader interface. I tried with below code, but not success. results.length becomes zero. Am I missing anything? window.requestFileSystem(TEMPORARY, 1024*1024 /*1MB*/, function(fs) { var dirReader = fs.root.createReader(); var

问题 According to Exploring the FileSystem APIs at Browser support & storage limitations You may need the --allow-file-access-from-files flag if you're debugging your app from file:// . Not using these flags will result in a SECURITY_ERR or QUOTA_EXCEEDED_ERR FileError. Launched chromium with --allow-file-access-from-files , --unlimited-storage and possibly deprecated --unlimited-quota-for-files ; also --unsafely-treat-insecure-origin-as-secure=file:///path/to/directory/* with --user-data-dir=

问题 When doing webkitRequestFileSystem in window.PERSISTENT option in Google Chrome, where on my filesystem do files get written? I'd like to drop files there and have Chrome interact with them while I'm building and debugging this app. 回答1: For me, at least on Mac OSX, they're stored under /Users/USERNAME/Library/Application Support/Google/Chrome/Default/File System for me. If you're using profiles, there will be profile directories instead of Default . However, each origin's saved files/folders