- From: <bugzilla@jessica.w3.org>
- Date: Wed, 11 Sep 2013 18:27:25 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23113 --- Comment #2 from Graham <graham.clift@am.sony.com> --- I think the mode='showing' approach is really a band-aid that helps but doesn't solve all the problems. So maybe the starting point here is to define some of the problems that I believe we need to solve: Problem1: App needs to know whether the UA is already showing these captions by itself. Currently the app can set mode='showing' and not know the result in the UA. Problem2: App needs to know whether the UA is capable of showing these captions if requested to turn them on. There is no way interrogate the UA capabilities in order to, say,allow for loading a captioning display library in advance. Problem3: App needs to know whether the platform supports native captioning in one type and and whether it is capable of and whether it does convert these to another format when presenting to JS. For example: A UA might be able to leverage the platform's native display of CEA-708 captions when the video is presented fullscreen but not in partial screen mode. Support for captioning in the partial screen mode might be done by converting captions to WebVTT or TTML cues in order to make use of the UA's native captioning ability. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 11 September 2013 18:27:27 UTC