- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Apr 2014 17:44:12 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25353 --- Comment #7 from Eric Carlson <eric.carlson@apple.com> --- (In reply to Glenn Adams from comment #5) > (In reply to Aaron Colwell from comment #4) > > I thought DataCue > > was only intended for things the UA doesn't know how to parse which is why I > > feel like the .value property is a little strange. > > Not exactly. It is intended to be used for @kind metadata tracks, which > imply the UA doesn't know how to process (e.g., render) the content. > I wouldn't say that a UA doesn't know how to render the content, metadata is "data about data" so it isn't necessarily meant to be rendered. > My understanding of Ted's ask is that it should be possible for a UA that > does know how to parse the cue's payload into something other than a string > to expose the result of that parsing to the APP, without forcing every APP > to perform the same decoding on the APP side of the fence. > We are also suggesting this because some formats, eg. HLS, can have metadata with non-POD values. We *could* serialize these values to XML or JSON and return them from the existing .text attribute, but a script will almost always need to create an Object/Document to work with it so have a .value attribute is more efficient. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 16 April 2014 17:44:13 UTC