- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Aug 2011 17:24:30 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13359
Glenn Adams <glenn@skynav.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|NEEDSINFO |
--- Comment #3 from Glenn Adams <glenn@skynav.com> 2011-08-19 17:24:29 UTC ---
(In reply to comment #2)
> EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
> satisfied with this response, please change the state of this bug to CLOSED. If
> you have additional information and would like the editor to reconsider, please
> reopen this bug. If you would like to escalate the issue to the full HTML
> Working Group, please add the TrackerRequest keyword to this bug, and suggest
> title and text for the tracker issue; or you may create a tracker issue
> yourself, if you are able to do so. For more details, see this document:
> http://dev.w3.org/html5/decision-policy/decision-policy.html
>
> Status: Did Not Understand Request
> Change Description: no spec change
> Rationale: I don't understand. What is the concrete use case where a script
> would be doing anything with a kind=metadata track and not know what the
> metadata is but yet would still be able to do something useful with it?
My understanding (Bob may wish to correct) is as follows:
Page origin O exposes video/audio from a 3rd party P, which contains/refers to
a metadata track sourced by P or sourced by a 4th party M.
Page origin O provides JS for interpreting metadata tracks with media types M1,
M2, or M3.
If Page author O is provided with content type information for the metadata
track contained in response headers (or by other means if fetched via
non-HTTP), then O's JS can select appropriate handling of metadata content
exposed to JS via TextTrackCue.getCueAsSource().
This information could be exposed to JS via a new TextTrack.type IDL attribute.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 19 August 2011 17:24:32 UTC