Rob Walch

Hi @mtoczko, Thanks for the fixes. I missed this one before cutting v1.2.3. However, I closed #4898 as I was not able to reproduce the `payload` exceptions using the stream...

[Not a Contribution](https://www.apache.org/licenses/LICENSE-2.0) > newDetails.age is a value in seconds Good catch. > I get a similar behavior where it refreshes the playlist at the same increasing rate of 333ms...

[Not a Contribution](https://www.apache.org/licenses/LICENSE-2.0) > To make sure I'm understanding, if newDetails.age was changed to milliseconds, then you are saying that the rest of the behavior is intentional? HLS.js will attempt...

Related #3900

Hi @MaximumRGB, If the error event is not fatal then you don't need to do anything: HLS.js will keep trying. Fatal network error events (`event.fatal === true`) occur when the...

[Not a Contribution](https://www.apache.org/licenses/LICENSE-2.0) > I looked into it. In fact, the solution to this problem is to create a css: Thanks for looking into it @mtoczko. Looks like markup details...

> Here there would be one exception if we add support for style blocks in WebVTT. Maybe tighter vtt.js integration? That's one way to get more consistent rendering across browsers....

Sample stream is no longer available. There is a new branch available for testing DRM support which you can check out here: [feature/drm-fairplay-key-system](https://github.com/video-dev/hls.js/compare/feature/drm-fairplay-key-system)

Hi @nochev, Thanks for taking a look and for providing the sample stream. These changes are slated for v1.3.0 which has an expected release date of October 18th: https://github.com/video-dev/hls.js/milestone/50

Please include as part of each bug report: - Actual hls.js version (not "latest") - Test stream/page that can be used to reproduce the issue