Text tracks with kind=chapter have different rules for processing.

Hi Ray, could you take this bug? I think it is better to implement it in the video control. Our goal is that: show a chapter menu on the video control for user selection. 1. We need a UI button/box/area to show the chapters. 2. When user press/hover the button, we need to do: 2.1 Get the chapter texttracks through video element 2.2 Run the algorithm to construct a nested tree. https://html.spec.whatwg.org/multipage/embedded-content.html#text-tracks-describing-chapters:text-track-rules-for-extracting-the-chapter-title 2.3 Display the tree at UI 3.If user select one chapter, do a seek.

sure, though I am not quite sure we could just move forward without UX/UI spec. Perhaps, we need to clarify how many implementable VTT features and how to integrate them (maybe?)...otherwise, video control might run out of room for each function/button. Tim, what do you think about this? Thanks.

Bobby, Vance, per discussed, let's evaluate the priority of this feature in Platform team and schedule UX effort accordingly.

As discussion with media team, media team is already starting platform works (non-UI related). However, we are still working on UX and frontend planning. No ETA so far.

Attaching chapter button icon here so that we don't need to look for visual resource if we pick up this bug again after quite a while.