Skip to content
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

media-source/mediasource-errors.html: Invalid test #3727

Open
jyavenard opened this issue Sep 15, 2016 · 0 comments
Open

media-source/mediasource-errors.html: Invalid test #3727

jyavenard opened this issue Sep 15, 2016 · 0 comments

Comments

@jyavenard
Copy link
Contributor

The test "Signaling 'decode' error via segment parser loop algorithm after initialization segment and partial media segment has been appended."

loads an init data, followed by half a media segment (which does contain invalid frames).

Why would that generate a media element error?
The track buffer does contain valid frames.
We are to fire "error" when "Fatal errors in decoding the media data that occur after the user agent has established whether the current media resource is usable (i.e. once the media element's readyState attribute is no longer HAVE_NOTHING) must cause the user agent to execute the following steps:"

I understand fatal as meaning that we can't recover playback of the media. As the element does contain valid frames, it can be argued that the error is not fatal and can be recovered.

Neither Chrome, Safari or Firefox will produce an error there, and all we go over the error.

This test should be either removed, or modified so that we really have a fatal error in the content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants