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
trackEventInits, muteTracks, addList and removeList were added to make events firing well defined and immediate, so that the application does not get ahold of objects before they are properly updated according to the algorithm.
With regards to addList and removeList, we reference mediacapture-streams for adding and removing tracks to the stream.
This does fire the event synchronously after adding/removing the stream (good), but as is written the algorithm is supposed to be executed by queuing a "task that runs the following steps". The same goes with muting.
This means that "ontrack" will fire first, exposing tracks and streams to the application, and then after a delay the tracks will be unmuted, added to the streams, etc.
Do we need to revisit these things to not say "queue a task that"? (Leaving any necessary queuing to the caller of these algorithms)
The text was updated successfully, but these errors were encountered:
trackEventInits, muteTracks, addList and removeList were added to make events firing well defined and immediate, so that the application does not get ahold of objects before they are properly updated according to the algorithm.
With regards to addList and removeList, we reference mediacapture-streams for adding and removing tracks to the stream.
This does fire the event synchronously after adding/removing the stream (good), but as is written the algorithm is supposed to be executed by queuing a "task that runs the following steps". The same goes with muting.
This means that "ontrack" will fire first, exposing tracks and streams to the application, and then after a delay the tracks will be unmuted, added to the streams, etc.
Do we need to revisit these things to not say "queue a task that"? (Leaving any necessary queuing to the caller of these algorithms)
The text was updated successfully, but these errors were encountered: