Add <track> element

[petele]

No description provided.

[petele]

@foolip - I think this is the right thing here, according to MDN this is supported, but it has a limited value. If I don't comment out the line, the whole feature is not baseline because that is apparently not supported in Chrome.

[foolip]

Does npm run dist throw an error if you include it? By non-real value we mean things like true in BCD that we can't handle and throw an error. I agree with excluding it, just want to understand.

To not have to fine tune the comment, you can just delete the lines. This whole block will go away if we move the tags to BCD.

[petele]

No, it does not throw an error.

Looking a bit deeper, this property it's not supported by Chrome, and there's no plan to support it.

I uncommented that line, and used compute_from, but I don't think that's the right answer either. Open to suggestions here. @ddbeck @captainbrosset

[foolip]

@petele can you also rename the file to text-tracks.yml in line with audio-video-tracks.yml?