-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Safari 11 MediaSource failures #1048
Labels
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
Milestone
Comments
|
The failure of the "trims content at appendWindowEnd" test is caused by a bug we've been working around in Safari 10: https://bugs.webkit.org/show_bug.cgi?id=165342 We can apply the same polyfill to Safari 11. |
shaka-bot
pushed a commit
that referenced
this issue
Oct 3, 2017
One of the Safari 10 bugs we work around is still present in Safari 11. Issue #1048 Change-Id: I54e146bcce9770f980a0dabd477a86b482a6c901
New MediaSource bug filed against Safari 11: https://bugs.webkit.org/show_bug.cgi?id=177884 |
Cherry-picked to v2.2.3. |
joeyparrish
added a commit
that referenced
this issue
Oct 16, 2017
One of the Safari 10 bugs we work around is still present in Safari 11. Issue #1048 Change-Id: I54e146bcce9770f980a0dabd477a86b482a6c901
joeyparrish
pushed a commit
that referenced
this issue
Oct 16, 2017
SourceBuffer.remove, when told to remove exactly up to a keyframe, will also remove that keyframe and all of the content till the next keyframe. This results in far too much content being deleted, and is breaking our tests on Safari 11. Patching this by offseting the end of the removal range by 1ms seems to be a viable workaround. Closes #1048 Change-Id: I062b2dc2617f1372f885f4ccbc906d77c65412d7
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
Safari 11 fails several MediaSourceEngine tests. We need to:
The text was updated successfully, but these errors were encountered: