Closed
Bug 1215028
Opened 9 years ago
Closed 9 years ago
Implement chrome.fileSystem API
Categories
(WebExtensions :: Untriaged, defect)
WebExtensions
Untriaged
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: gkrizsanits, Unassigned)
References
(Blocks 1 open bug)
Details
Reporter | ||
Updated•9 years ago
|
Blocks: webextensions-chrome-gaps
Updated•9 years ago
|
Flags: blocking-webextensions-
Comment 1•9 years ago
|
||
This is an app API. Adding those to WebExtensions is opening up a huge can of worms that I'd rather avoid. We do already have a web API for this, though: https://developer.mozilla.org/en-US/docs/Web/API/File_System_API/Introduction
Comment 2•9 years ago
|
||
Closing based on comment 1, if that's wrong Gabor, please re-open.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Comment 3•8 years ago
|
||
(In reply to Kris Maglione [:kmag] from comment #1) > We do already have a web API for this, though: > https://developer.mozilla.org/en-US/docs/Web/API/File_System_API/Introduction Is that the right link? Mozilla's documents say that only Chrome implemented the File System API [1], and W3C says the API was abandoned in 2014 [2], yet Bugzilla suggests that something like the API is being developed [3][4]. I don't understand. Is the File System API coming back from the dead, or is there some other extension-accessible API in the offing? [1] https://developer.mozilla.org/en-US/docs/Web/API/File_System_API#Browser_compatibility [2] https://www.w3.org/TR/file-system-api/ [3] Bug 1265767 [4] https://bugzilla.mozilla.org/buglist.cgi?quicksearch=filesystem+api
Flags: needinfo?(kmaglione+bmo)
Comment 4•8 years ago
|
||
We're not implementing Chrome app APIs. We haven't decided whether to implement a filesystem API, but it's being tracked in bug 1246236.
Flags: needinfo?(kmaglione+bmo)
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•