- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 13 Dec 2011 18:54:25 -0800
- To: Jarred Nicholls <jarred@webkit.org>
- Cc: Charles Pritchard <chuck@jumis.com>, Adrian Bateman <adrianba@microsoft.com>, "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>, Feras Moussa <ferasm@microsoft.com>
I agree we should remove it from spec! I think we'd be fine with removing it from the Firefox implementation. / Jonas On Tue, Dec 13, 2011 at 6:33 PM, Jarred Nicholls <jarred@webkit.org> wrote: > +1 though it won't likely go away from implementations as easily. > > On Dec 13, 2011, at 8:22 PM, Charles Pritchard <chuck@jumis.com> wrote: > >> Seems quite reasonable to me. We've got data URL strings for people who need inefficiency (or portable strings). >> >> >> >> On Dec 13, 2011, at 4:52 PM, Adrian Bateman <adrianba@microsoft.com> wrote: >> >>> Another topic that came up at TPAC was readAsBinaryString [1]. This method >>> predates support for typed arrays in the FileAPI and allows binary data >>> to be read and stored in a string. This is an inefficient way to store >>> data now that we have ArrayBuffer and we'd like to not support this method. >>> >>> At TPAC I proposed that we remove readAsBinaryString from the spec and >>> there was some support for this idea. I'd like to propose that we change >>> the spec to remove this. >>> >>> Thanks, >>> >>> Adrian. >>> >>> [1] http://dev.w3.org/2006/webapi/FileAPI/#readAsBinaryString >>> >>> >> >
Received on Wednesday, 14 December 2011 02:55:23 UTC