- From: Anne van Kesteren <annevk@opera.com>
- Date: Tue, 09 Mar 2010 10:17:52 +0100
- To: public-device-apis@w3.org
On Tue, 09 Mar 2010 03:49:49 +0100, Eric Uhrhane <ericu@google.com> wrote: > On Mon, Mar 8, 2010 at 6:42 AM, Anne van Kesteren <annevk@opera.com> > wrote: >> It is not defined how the constructor for BlobBuilder ought to work. > > I can flesh that out, but there's not a lot to say. Do you mean > something more than a line like this? > "When the BlobBuilder() constructor is invoked, the user agent MUST > return a new BlobBuilder object." If that's all there is to it that would be enough, yes :-) Maybe we should change Web IDL so that this is the default unless otherwise specified... >> Why is endings needed? Can't the author handle that himself? > > He can emulate a specific platform. If we want him to be able to > emulate "native", we'd have to tell him what filesystem he's actually > writing to, which I'd like to avoid. I'm trying to make it easy to > share files with apps external to the browser. I missed the native option, but given that files can be moved around very easily outside the browser too it seems you would always need to use CRLF if you want to be compatible. Having said that, how many normal files being used by typical end users are plain text these days anyway? It seems like a feature that almost nobody will need, but maybe I am not seeing something here. >> Could we get away with not having encoding at all? I.e. always writing >> UTF-8 octets? > > That's certainly an easy place to start. Anybody have strong feelings > about it? I do feel somewhat strongly about keeping as much encoding related features away from the platform. They are way complicated and ideally would have never been needed if only we came across UTF-8 a little sooner. -- Anne van Kesteren http://annevankesteren.nl/
Received on Tuesday, 9 March 2010 09:18:24 UTC