[Bug 25261] Don't require TextTrack.kind = 'metadata' for DataCues?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25261

--- Comment #5 from Glenn Adams <glenn@skynav.com> ---
(In reply to Silvia Pfeiffer from comment #4)
> (In reply to Philip Jägenstedt from comment #3)
> > Sorry Aaron, I should have worded that more carefully.
> > 
> > I don't think anything (normative) needs to be said about DataCue rendering,
> > because there is no default rendering algorithm that could apply.
> 
> When cues are of kind captions, subtitles, chapters or descriptions, some
> kind of rendering is expected, see
> http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#attr-
> track-kind .
> 
> The only kind of cue that is not rendered is of metadata. For that reason,
> kind=metadata is appropriate for DataCues which are per definition not
> rendered.

Better to say "not automatically rendered by UA". That is, it isn't meant that
it can't be rendered (in general) or that it can't be rendered by the UA under
the direction of the app (e.g., app translates into HTML to be rendered by UA).

> 
> If we allowed DataCue to be on a caption track, for example, we'd need to
> define a rendering algorithm - likely the content of the text attribute
> being rendered verbatim on screen. Is there a use case for that?

Actually I think Brendan's suggestion is a good one, that if a DataCue is on a
track of @kind !metadata, then the UA should ignore it for the purpose of
automatic rendering.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Sunday, 6 April 2014 06:07:29 UTC