On Thu, Aug 29, 2013 at 3:05 AM, Robert O'Callahan rob...@ocallahan.org wrote:
I can't think of any good reason to support createObjectURL(MediaStream) ---
except for compatibility with existing content, which may be an issue
already.
As I understand it, we have the createObjectURL() design
As currently specified File's name property seems to be a code unit
sequence. In zip archives the resource's path is a byte sequence. I
don't really know what popular file systems do. Given that a File has
to be transmitted over the wire now and then, including it's name
property value, a code
On Thu, Aug 29, 2013 at 9:48 AM, Anne van Kesteren ann...@annevk.nl wrote:
As currently specified File's name property seems to be a code unit
sequence. In zip archives the resource's path is a byte sequence. I
don't really know what popular file systems do. Given that a File has
to be
On Thu, Aug 29, 2013 at 4:10 PM, Glenn Maynard gl...@zewt.org wrote:
I don't think it makes sense to expect filenames to round-trip through
File.name, especially for filenames with a broken or unknown encoding.
File.name should be a best-effort at converting the platform filename to
something
On Thu, Aug 29, 2013 at 10:14 AM, Anne van Kesteren ann...@annevk.nlwrote:
On Thu, Aug 29, 2013 at 4:10 PM, Glenn Maynard gl...@zewt.org wrote:
I don't think it makes sense to expect filenames to round-trip through
File.name, especially for filenames with a broken or unknown encoding.
On Thu, Aug 29, 2013 at 4:46 PM, Glenn Maynard gl...@zewt.org wrote:
All constructing a File does is give a name (and date) to a Blob. It
doesn't create an association to an on-disk file, and shouldn't be
restricted to filenames the local platform's filesystem can represent.
Yes, but it can
On Thu, Aug 29, 2013 at 10:51 AM, Anne van Kesteren ann...@annevk.nlwrote:
On Thu, Aug 29, 2013 at 4:46 PM, Glenn Maynard gl...@zewt.org wrote:
All constructing a File does is give a name (and date) to a Blob. It
doesn't create an association to an on-disk file, and shouldn't be
On Aug 28, 2013, at 9:48 AM, Dominique Hazael-Massieux wrote:
Hi WebApps WG,
The Media Capture Task Force (responsible for specs that deal with
MediaStream objects [1]) has been considering whether one should be able
to assign a MediaStream to video and audio elements via an URL
obtained
