Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the PR for the
v3.33.1
the last v3 release considered aslatest
on npm.The official
v4.0.0
will be released just after, and will mark our transition to a stablev4
, now considered our main version.v3 will still be maintained, and potential v3 releases may still be made (for bug fixes and minor improvements) under the
legacy-v3
tag on npm.To note that this release only brings minor bug fixes on top of the
v3.33.0
, none being regressions (those issues have been here since the corresponding features have been introduced). This reassure us that the v3 is stable enough for it to be reliable for people not having the time budget to make the switch to a v4 yet.Left issues we know we have on v3 are:
niche issues on Tizen (Samsung TVs).
For example we are aware of some live pre-roll use cases with weird player behavior. This has been fixed in v4 but the ""fix"" (more of a work-around really) is too complex to be backported to the v3 easily. We would have to re-do the development and testing there, for what seems to be very rare issues just on Tizen TVs.
The usual trail of DRM compatibilities issues.
The "Encrypted Media Extensions" API allowing media decryption in a browser is notorious to break every other day on a random device when relying on specific configurations. Those issues come and go, sometimes they are fixed without any action on our part after a firmware update, other times we bring a work-around (on top of a work-around on top of a work-around, which may sometimes break legitimate use cases, yay!). Just yesterday we again noticed and fixed an issue arising in very specific conditions with the PlayStation 5 (we're trying a solution only for Canal+ applications for now).
Most of those issues should be fixed in future
v3
maintenance releases.Changelog
Bug fixes
<UTCTiming>
resources at each refresh if it failed for the first request of the Manifest [Don't re-load a Manifest's optional external resource each time if initial failed #1370]DASH_WASM
feature do not rely on WebAssembly's sign-extension operators anymore as that is poorly supported on older Samsung and LG TVs [WASM: Temporarily rollback on wasm-opt dependency for release builds to make it work on some LG + Samsung TVs #1372]Other improvements