This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11615 - save text from an editor in a file system
Summary: save text from an editor in a file system
Status: RESOLVED WORKSFORME
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Web Storage (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: public-webapps-bugzilla
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-29 13:11 UTC by contributor
Modified: 2011-01-23 20:48 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-12-29 13:11:32 UTC 
Specification: http://dev.w3.org/html5/webstorage/
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#top

Comment:
save text from an editor in a file system

Posted from: 41.238.110.138
Comment 1 Tab Atkins Jr. 2010-12-29 17:51:02 UTC 
This use-case is handled by the File System API, which is a javascript API separate from HTML5.
Comment 2 Ian 'Hixie' Hickson 2011-01-23 20:48:31 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: no spec change
Rationale: This can already be done in a variety of ways, either by just generating a data: URL with the data and having the user interact with it via a link as you would normally, or by redirecting the user to that data: URL, or by letting the user drag a File object out of the page, having created that object using the File Writer API, or by letting the user interact with a link based on a File object created that way, etc...