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
duration assignment to the MediaSource is unclear #230
Comments
Changing the mediasource's duration never remove data from the source buffer, as such, it can't change the buffered range. As such, this is an issue that needs to be lodged against chrome issue tracking. not the spec. |
Apologies.. it may not be specific to Chrome. So is it possible that the bounds of the buffer is beyond the duration and that a client adjusting the duration makes no changes to the underlying buffer? Or is it that any assignments my ultimately be ignored for whatever value is greater? |
if you set duration such that buffered data would be outside the duration of the element, then duration value will actually be set to the "highest end time". it's all described in the link I provided earlier. There's no rationale for setting the updating attribute to true simply because you set the duration. And TBH, I'd be extremely surprise if chrome did do that. |
Thanks @jyavenard for clearing this up. |
@wolenetz It appears in Chrome when assigning duration to MediaSource that the buffer's
updating
is set to true without actually dispatchingupdatestart
or the correspondingupdateend
. It makes sense that it would be updating, because the buffer may need to change it's range due to the newly assigned duration. But it's not well documented here, and the lack of events make it hard to track.The text was updated successfully, but these errors were encountered: