W3C home > Mailing lists > Public > public-html-media@w3.org > May 2021

[media-source] MSE-in-Workers: Consider adding a "closing" readyState to explain new `InvalidStateError` exception when closing underway (#276)

From: wolenetz via GitHub <sysbot+gh@w3.org>
Date: Wed, 26 May 2021 20:33:55 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-902889997-1622061233-sysbot+gh@w3.org>
wolenetz has just created a new issue for https://github.com/w3c/media-source:

== MSE-in-Workers: Consider adding a "closing" readyState to explain new `InvalidStateError` exception when closing underway ==
MSE-in-Workers feature issue is #175 

This issue tracks discussing an additional `readyState` usable by apps to understand when a worker MediaSource object is in the process of being closed or detached-from by the formerly-attached `HTMLMediaElement`. Implementations may choose to throw `InvalidStateError` exception when servicing requests on a worker-owned MediaSource or SourceBuffer that require `readyState` to not be `closed`, yet the implementation has begun but not yet fully completed the steps involved in reaching `closed` readyState.

For example, setting the `mode` attribute of a SourceBuffer requires essentially that the parent `MediaSource` not be `closed` nor `updating`. But if it knows that it will be closing imminently due to some internal notification from the implementation of its attachment to `HTMLMediaElement`, then it may throw exception. Having a distinct `readyState` for this scenario would assist worker API usage debugging (see an example of such at https://github.com/w3c/media-source/issues/175#issuecomment-742132101).

Please view or discuss this issue at https://github.com/w3c/media-source/issues/276 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 May 2021 20:33:57 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 26 May 2021 20:33:58 UTC