- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Apr 2014 17:06:35 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25355 --- Comment #3 from Brendan Long <self@brendanlong.com> --- (In reply to Aaron Colwell from comment #1) > I'm concerned about having type strings exposed here. What is the use case > where the UA can determine the type, but not actually be able to parse the > data it is returning? If it understands the type, it seems like it should be > able to return a type specific cue for it. Something like this amplifies my > concern that unspeced protocols will be allowed because this is starting to > look like a "hash map" type interface. As far as I know, every container format has metadata to say what type of data a stream contains (stream_type for MPEG-TS, CodecID for Matroska and WebM, Ogg Skeleton has a mime type). By exposing that data, we can tell JavaScript what the track contains without knowing how to parse it. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 16 April 2014 17:06:37 UTC