You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: