- From: <bugzilla@jessica.w3.org>
- Date: Fri, 13 Apr 2012 14:50:53 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16733 Summary: Drop 'endings'? Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: File API AssignedTo: arun@mozilla.com ReportedBy: simonp@opera.com QAContact: public-webapps-bugzilla@w3.org CC: public-webapps@w3.org File API Writer says about BlobBuilder's endings: [[ Can we do without endings? Any choice other than "native" can be implemented by the app author, and most file formats don't care about line endings. "Native" would be handy for sharing certain types of text files with apps outside the browser [e.g. Makefiles on a system where make is expecting \n will have issues if they're written with \r\n]. Is it worth it? Can this be worked around if we don't supply it? ]] This bug is about the Blob constructor's 'endings'. What's the motivation for having it? Can we drop it? In BlobBuilder it only applies for DOMString, but Blob constructor doesn't say whether it applies for only DOMString or all of DOMString, ArrayBuffer and Blob. Authors who want to normalize line endings in their DOMStrings on Windows can do so manually before passing the string to the Blob constructor, by checking navigator.platform.substr(0, 3) == 'Win' and then a simple replace(). -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Friday, 13 April 2012 14:51:00 UTC