Joey Parrish

PR #4407 fixed native browser rendering, but not the DOM-based rendering of our UI. Reopening.

Here's the quick repro in JS console of the demo app: ```js data = shaka.util.StringUtils.toUTF8(` Harry Potter n'est pas stupide. `); uri = `data:application/ttml+xml;base64,${shaka.util.Uint8ArrayUtils.toBase64(data)}`; player = video.ui.getControls().getLocalPlayer(); track = await...

Now fixed in both contexts.

The major change from v3.1 to v3.2 is the MediaCapabilities API. It went from opt-in on 3.1 to required in 3.2+. My guess is that Tizen's has an implementation of...

I'll cherry-pick @avelad's fix to all the branches we are currently maintaining (v3.2, v3.3, v4.0, v4.1). See also https://github.com/shaka-project/shaka-player/blob/main/maintained-branches.md

I believe we are driving the tracks API from the metadata in the HLS playlist. Can your playlist be fixed to signal the presence of the CC data?

Then I'll convert this into an "enhancement" issue to build CC metadata on-the-fly as captions are discovered in the content. Note that this would only work for TS content, and...

The CAF team have their own release schedule, which I can't predict. But it would have to be in a Shaka Player release first, and this is not scheduled for...

If anyone is interested in contributing a PR for this, please let us know! (Tagging @arturparkhisenko based on discussions in #2466.)

I don't believe anyone is working on this at the moment. Would you like me to assign it to you?