Add VTTCue and WEBVtt support

Site Outreach Issue #14623778

Details

Author
Oren M.
Created
Nov 11, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

WebVTT: https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API
VTTCue: https://w3c.github.io/webvtt/#the-vttcue-interface

Supported by all other browser vendors in Chrome, FF, Safari.
Also implement ::CUE pseudo-element to enable support in CVAA.

Currently all player developers need to create their own subtitles/captions implementations due to browser having fragmented support in all of the above which makes supporting accessibility very hard and cumbersome.
Having you support this will ensure better interoperability.
Please consider migrating the solution to IE11 as well as you still have it on platforms which are widely supported and EOL is not near as it seems.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

      Changed Status to “Site Outreach”

    • Please use the uservoice for feature requests

    • Francois, already did https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/32226955-add-vttcue-and-webvtt-support
      Saw the user voice only after I opened this.

      Do you know if this is something on your table?

      thanks,

      Oren M.

    • According to a report from encoding.com , 30% of content transcoded/encoded by encoding.com is in WebVTT format. WebVTT is now in CR at the W3C. All other browsers implement the VTTCue object.
      Video player vendors (incl. video.js, Kaltura, Brightcove, JWplayer) would prefer not having to write their own code for rendering WebVTT captions and subtitles on top of videos (according to participants at the FOMS Workshop).

      It would be very useful to have VTTCue object support in MS Edge!

    • I second Silvia’s comment.

      At JW Player, we’ve never been able to rely on Edge’s rendering because of the lack of support for WebVTT and the VTTCue interface. These are needed in order to ensure our customers (broadcasters) are in compliance with FCC guidelines for displaying closed captions.

    • I third Silvia and Evol.
      Not only do we need VTTcue support, we also need voice spans, and style rendering.
      At Ellation we are already outputting WebVTT segments that look like the following:

      WEBVTT

      STYLE
      ::cue(v[voice="sign_2067_43_High_School_Divi"]) {
      color: #4e483e00;
      font-family: "Times New Roman", sans-serif;
      font-size: 014px;
      text-shadow: #fdfbf500 -3px 0px, #fdfbf500 0px 3px, #fdfbf500 0px -3px, #fdfbf500 3px 0px, #00000000 0px 0px 0px;
      }

      STYLE
      ::cue(.strike) {
      text-decoration: solid line-through;
      }

      c0000000
      00:00:00.000 --> 00:00:07.350 position:008% size:060% line:01 align:left
      This Text is Bold, no strike-through.

      c0000001
      00:00:10.000 --> 00:00:13.000 position:050% size:096% line:12 align:center
      This text should show with Strike Through.

    You need to sign in to your Microsoft account to add a comment.

    Sign in