- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Mon, 29 Sep 2014 06:38:21 +1000
- To: Jon Piesing <Jon.Piesing@tpvision.com>
- Cc: "alexander.adolf@condition-alpha.com" <alexander.adolf@condition-alpha.com>, "public-inbandtracks@w3.org" <public-inbandtracks@w3.org>, Nigel Megitt <nigel.megitt@bbc.co.uk>
On Thu, Sep 25, 2014 at 6:32 AM, Jon Piesing <Jon.Piesing@tpvision.com> wrote: >>If a text track never exposes any cues, we shouldn't expose its existence to browsers. That's like saying: hey, I have some data, but I won't give it to you. Or if we apply that logic to an audio or video stream: it's like announcing that a video stream exists, but not rendering it. Such tracks are not relevant to this specification. > > What about text tracks that are rendered by the (native) media player and where HTML would like to be able to enable/disable them in the same way as video & audio? If the UA renders the captions together with the video, then for all intents and purposes this is an additional video track with burnt-in captions that should be exposed in the @videoTracks attribute of the MediaElement with a kind="captions" . This way, it is listed as an available extra video track. Regards, Silvia.
Received on Sunday, 28 September 2014 20:39:08 UTC