Questions about chapters API

[hochhaus]

Have you read the Tutorials?
Yes

Have you read the FAQ and checked for duplicate open issues?
Yes

What version of Shaka Player are you using?
v3.3.0

Please ask your question
I'm experimenting with the chapters API referencing the code, tests and comments (#3538 (comment)). Could you clarify my understanding of the following items?

1. Why is the chapterURL provided via player.addChaptersTrack() instead of being included in the manifest? This isn't the end of the world but it seems unintuitive to me.
2. Why does the addChaptersTrack() promise resolve before the chapters file has been downloaded and parsed by the browser? This seems to unnecessarily increase the complexity of correctly using chapters.
3. Why does shaka.extern.Chapter not include the cue identifier (shaka.extern.Cue.id)? The calling code can pull this information directly out of the cue but it seems to unnecessarily complicate certain use cases.

[hochhaus]

Why does the addChaptersTrack() promise resolve before the chapters file has been downloaded and parsed by the browser? This seems to unnecessarily increase the complexity of correctly using chapters.

To add a bit more context here, when shaka downloads a captions VTT file it appears to do so from a JS fetch(). However, when shaka downloads a chapters VTT file it appears to do so by appending a <track> element to the DOM. Possibly this is necessary for some reason. However, if it is not, possibly the API could be cleaned up by directly fetch()ing the chapters VTT as well?

[avelad]

Hi @hochhaus

1. We would be happy to support it directly in HLS and DASH, but as far as I know it is not specified how they should be included, if you have the information, please open an enhancement issue so we can do it in the future.
2. This sounds like a bug, please open a bug and we'll fix it.
3. I think it can be easily fixed.

[hochhaus]

Thanks @avelad. I opened a dedicated issue per your comments so I will close this issue.

[hochhaus]

We would be happy to support it directly in HLS and DASH, but as far as I know it is not specified how they should be included, if you have the information, please open an enhancement issue so we can do it in the future.

I also am not able to find this documented and the current implementation is not problematic. Should I find HLS / DASH documentation in the future I will open a dedicated issue.