[foms] WebVTT implementation in browsers

[Joey Parrish]

The lack of complete and consistent VTTCue support in browsers led the
Shaka Player team to develop both a plugin system for caption display and
an internal cue structure (which is a superset of VTTCue with
accommodations for TTML concepts).  Even the browsers that support VTTCue
don't seem to implement it fully.

Although the work for all of this has already been done, less code would
always be better than more code.  If I could rely on browser rendering for
cues (and on a full implementation of VTTCue as spec'd), we could delete a
lot of code.


On Fri, Apr 6, 2018 at 8:03 PM, Silvia Pfeiffer <silviapfeiffer1 at gmail.com>
wrote:

> Hi everyone,
>
> I am collecting opinions about the need for better support of WebVTT
> in browsers. Please speak up for or against it.
>
> This is on the background of getting WebVTT to become a W3C
> recommendation, which is what we are working on in the Timed Text
> Working Group (TTWG) right now.
>
> In my experience, having a spec at recommendation status is a key
> motivator to get browsers to implement features interoperably. Basic
> support is in all browsers, but interoperability is so poor that it's
> basically unusable for normal Web publishing.
>
> I'd like to hear from browsers if a stable published specification of
> WebVTT would encourage them to implement support.
>
> I'd like to hear from video player developers if they would drop their
> polyfills if browsers supported WebVTT in its completeness. (Browsers
> want to know this also.)
>
> And I'd like to hear from video publishers if native WebVTT support
> would encourage them to publish more captions.
>
> If you have any opinion, please reply for yourself and/or your
> company. I'm collecting feedback for the TTWG mailing list.
>
> Cheers,
> Silvia.
>
>
> P.S. The WebVTT version in preparation for the standards track can be
> inspected at https://htmlpreview.github.io/?https://github.com/w3c/
> webvtt/blob/gh-pages/archives/2018-04-15/Overview.html
> (some links won't work because it's rendered through htmlpreview).
> _______________________________________________
> foms mailing list
> foms at xiph.org
> http://lists.xiph.org/mailman/listinfo/foms
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/foms/attachments/20180407/aa03b7de/attachment-0001.html>