Re: [whatwg] API for encoding/decoding ArrayBuffers into text

2012-03-14 Thread Cedric Vivier
Hi, On Wed, Mar 14, 2012 at 06:49, Jonas Sicking wrote: > Something that has come up a couple of times with content authors > lately has been the desire to convert an ArrayBuffer (or part thereof) > into a decoded string. Similarly being able to encode a string into an > ArrayBuffer (or part ther

[whatwg] Proposal to change getContext to support unavailable context at run-time.

2011-05-01 Thread Cedric Vivier
Hello group, For WebGL, we need getContext to possibly fail whereas the browser supports contextId "webgl". Indeed it is possible the browser fails creating a new 3D context for many different reasons at run-time, which means a given contextId might not be available at any given time. This is in

Re: [whatwg] Canvas.getContext error handling

2011-04-13 Thread Cedric Vivier
On Thu, Apr 14, 2011 at 09:01, Kenneth Russell wrote: > Adding support for asynchronous initialization of WebGL is a good > idea, and should be proposed on public_webgl, but this discussion > should focus solely on improving the specification of the existing > synchronous initialization path, and

Re: [whatwg] Canvas.getContext error handling

2011-04-13 Thread Cedric Vivier
On Wed, Apr 13, 2011 at 05:16, Kenneth Russell wrote: > (...) > To sum up, in general I think that whenever getContext("webgl") > returns null, it's unrecoverable in a high quality WebGL > implementation. Makes sense. Applications could detect all possible context creation failure scenarios with

Re: [whatwg] Cryptographically strong random numbers

2011-02-16 Thread Cedric Vivier
On Thu, Feb 17, 2011 at 08:29, Allen Wirfs-Brock wrote: >  Array.randomFill= function (length){...}; > > This would create a new array of the specified length where each element is a > random value in some range.  I propose that this range be 0..65535 as these > are easily manipulatable (and opt

Re: [whatwg] Cryptographically strong random numbers

2011-02-11 Thread Cedric Vivier
On Sat, Feb 12, 2011 at 04:40, Adam Barth wrote: >> Is there a specific reason for this limitation? >> Imho it should throw only for Float32Array and Float64Array since >> unbounded random floating numbers does not really make sense >> (including because of NaN and +inf -inf). > (...) > I went wit

Re: [whatwg] Cryptographically strong random numbers

2011-02-11 Thread Cedric Vivier
On Fri, Feb 11, 2011 at 19:38, Adam Barth wrote: > Just to followup on this thread, I've landed this feature in WebKit. > I'm not sure whether it made it into tonight's nightly, but it should > be in a nightly shortly. Nice! > interface Crypto { >  void getRandomValues(in ArrayBufferView array)

Re: [whatwg] Cryptographically strong random numbers

2011-02-05 Thread Cedric Vivier
On Sun, Feb 6, 2011 at 11:34, Roger Hågensen wrote: > But getRandomValues(in ArrayBufferView data) seem to indicate that each byte > (value) is random, limited to an array of 8bit data?. In the context of typed arrays, a value depends of the type of the ArrayBufferView. ArrayBufferView are interc

Re: [whatwg] Cryptographically strong random numbers

2011-02-04 Thread Cedric Vivier
Hi, On Sat, Feb 5, 2011 at 08:42, Adam Barth wrote: > interface Crypto { >  Float32Array getRandomFloat32Array(in long length); >  Uint8Array getRandomUint8Array(in long length); > }; I think the API would be more flexible and more future-proof defined as : interface Crypto { void getRandom