The spec description of abort() is somewhat confusing â consider for example step 1 of reset parser state. The MSE API is fully asynchronous, but this step seems to suggest a synchronous (blocking) operation, which doesn't make sense.
Saying that, current implementations can be useful in certain situations, when you want to stop the current append (or whatever) operation occurring on a source buffer, and then immediately start performing operations on it again. For example, consider this code:
sourceBuffer.addEventListener("updateend", (ev) => {
// â¦
});
sourceBuffer.appendBuffer(buf);
Let's say that after the call to appendBuffer BUT before the updateend event fires (i.e., a buffer is being appended but the operation has not yet completed) a user "scrubs" the video seeking to a new point in time. In this case you would want to manually call abort() on the source buffer to stop the decoding of the current buffer, then fetch and append the newly requested segment that relates to the current new position of the video.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4