<div dir="ltr"><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Not relevant to WebVTT, but to the idea of using advancement as a tool to get browsers to conform....</span></div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div>> In my experience, having a spec at recommendation status is a key</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">> motivator to get browsers to implement features interoperably.</span><br><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">My experience has been close to the opposite - with WebRTC, customer pull has been the essential part of getting browsers to implement features, and that in turn has been a requirement for getting enough work done on the specs and tests to show conformance to the specs (which does help a bit towards pushing browsers to conform), and this in turn is a requirement for advancing along the standards track.</span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Apr 7, 2018 at 4:03 AM, Silvia Pfeiffer <span dir="ltr"><<a href="mailto:silviapfeiffer1@gmail.com" target="_blank">silviapfeiffer1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi everyone,<br>
<br>
I am collecting opinions about the need for better support of WebVTT<br>
in browsers. Please speak up for or against it.<br>
<br>
This is on the background of getting WebVTT to become a W3C<br>
recommendation, which is what we are working on in the Timed Text<br>
Working Group (TTWG) right now.<br>
<br>
In my experience, having a spec at recommendation status is a key<br>
motivator to get browsers to implement features interoperably. Basic<br>
support is in all browsers, but interoperability is so poor that it's<br>
basically unusable for normal Web publishing.<br>
<br>
I'd like to hear from browsers if a stable published specification of<br>
WebVTT would encourage them to implement support.<br>
<br>
I'd like to hear from video player developers if they would drop their<br>
polyfills if browsers supported WebVTT in its completeness. (Browsers<br>
want to know this also.)<br>
<br>
And I'd like to hear from video publishers if native WebVTT support<br>
would encourage them to publish more captions.<br>
<br>
If you have any opinion, please reply for yourself and/or your<br>
company. I'm collecting feedback for the TTWG mailing list.<br>
<br>
Cheers,<br>
Silvia.<br>
<br>
<br>
P.S. The WebVTT version in preparation for the standards track can be<br>
inspected at <a href="https://htmlpreview.github.io/?https://github.com/w3c/webvtt/blob/gh-pages/archives/2018-04-15/Overview.html" rel="noreferrer" target="_blank">https://htmlpreview.github.io/<wbr>?https://github.com/w3c/<wbr>webvtt/blob/gh-pages/archives/<wbr>2018-04-15/Overview.html</a><br>
(some links won't work because it's rendered through htmlpreview).<br>
______________________________<wbr>_________________<br>
foms mailing list<br>
<a href="mailto:foms@xiph.org">foms@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/foms" rel="noreferrer" target="_blank">http://lists.xiph.org/mailman/<wbr>listinfo/foms</a></blockquote></div><br></div>