- From: guest271314 <notifications@github.com>
- Date: Sun, 05 Apr 2020 11:47:30 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <heycam/webidl/issues/868/609463381@github.com>
Am not sure if it is worth investigating from a specification standpoint. The first time encountered that was probably due to user error by passing an array of arrays (of `Uint8Array`s) which were images which were retrieved at `Promise.all()` `then()` callback. The second occasion was passing a `Float32Array` (audio) directly to `Blob()` constructor, then saving that as a file with no extension set (where got string as output). FWIW, the goal is to stream video and audio as `Uint8Array` which is then converted to `Uint16Array` and `Float32Array`. Yes, experimented with `Set` passed to `Blob` during the same session where linked above testing different values passed to `Blob` and `File` constructor; probably a less user-error constructor to use where each `Blob` or `File` will be unique and to some extent prevent an array of arrays case. From a "human readable" perspective simply considered a `TypedArray` an iterable that could be passed directly to `Blob` constructor without the expectation that the output would be a string, which is what encounted when attempting to parse the `Float32Array` that saved as a file without extension. From a front-end standpoint the inclusion or omission of `[]` within `Blob` constructor can result is considerably different outputs. Will search File API for this topic and similar issues. Prefer to file bugs/issues immediately as perform a modicum of experiments at the front-end and the browser and OS could crash at any time and the experimentation, and result will be lost. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/heycam/webidl/issues/868#issuecomment-609463381
Received on Sunday, 5 April 2020 18:47:44 UTC