Rob Walch

- [ ] Rebase over #7527

I think `track.details = undefined` should be removed and the warning downgraded to a log message like `subtitle playlist ends @{details.fragmentEnd} with currentTime @{media.currentTime}`.

Loading the first fragment `foundFrag = fragments[0]` when segments are ahead would also be acceptable. But, if they are ahead with no overlap of the playhead, that suggests an issue...

Fix is up in #7626. branch test: https://bugfix-low-latency-webvtt-pa.hls-js-4zn.pages.dev/demo/

This is not possible unless the browser supports negative values for `HTMLMediaElement playbackRate`. Safari, Chrome, and Firefox throw `NotSupportedError` exceptions when attempting this.

> I would like to share the problematic live stream via a Slack direct message. Please do. The logs show detection of audio timestamp gaps and video timestamp overlap. This...

You can set [`maxAudioFramesDrift`](https://github.com/video-dev/hls.js/blob/master/docs/API.md#maxaudioframesdrift) to a higher number to prevent HLS.js from inserting silence when it detects missing audio samples.

Does changing the NAME attribute of one of the options workaround the issue (NAME="English CC" for example)?

`hls.allSubtitleTracks` and `hls.subtitleTracks` only list subtitle tracks. Captions tracks are not exposed in this interface. If you want to select between them, use the `HTMLMediaElement.textTracks` interface:  Set one of...

`startPTS`, `endPTS`, and the like have not and cannot be changed for span of hls.js version 1.x. There are integrations that depend on these timestamps being relative to the HTMLMediaElement...