[Bug 24416] Ambiguous support for native in-band captioning.

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

--- Comment #2 from Graham <graham.clift@am.sony.com> ---
(In reply to Silvia Pfeiffer from comment #1)

> 
> What is "optimized native captioning"?
> 

As described in the first paragraph, optimized native captions relieves the
application from having to handle the captions or the user agent from having to
convert them, both of which can suffer from performance loss and captioner's
intent.


> If none of the browser-provided captioning functionality works for you
> (WebVTT, the <track> element, TextTracks, inband tracks, etc) you are always
> free to run your own captioning feature fully through JavaScript.
>

Are you suggesting to run a captioning feature fully through JavaScript without
creating an API to control or test this feature? How would an application know
that a user agent can support closed captions in this native fashion without
this?

> 
> Assuming that "display native captioning" means that some other application
> on the platform has caption support, then there is no such thing as "a
> browser displaying native captions" - unless you use the <embed> tag, which
> doesn't make use of <track> and TextTrack features.
> 
> > Also, if the native cues can be passed to application level in 'hidden' mode
> > how can we convey that timing accuracy is not guaranteed but the data can be
> > used by the application for other non-critical timing sensitive uses (like
> > caption content search)? In this case, what type of 'hidden' TextTrackCue
> > would we use..dataCue?
> 
> You can use DataCue to expose any inband timed data, yes. But the browser
> won't magically expose it - you have to get browsers to implement it.

This is being raised from a browser implementer, TV manufacturer and TV
standards perspective as opposed to an web application developer perspective.
We need a standard way of allowing in-band captions to be handled natively that
doesn't conflict with the existing specification and allows the application to
assess that these captions are being handled even though they are not cued.

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

Received on Tuesday, 28 January 2014 00:41:57 UTC