- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Nov 2024 11:24:59 +0000
- To: public-webrtc-logs@w3.org
> Order of creation might not be deterministic if tracks are transferable to a worker and back Order should ideally be deterministic within a context (window or worker). We cannot guarantee the order of an event fired in a window and another event fired in a worker. > * The order could be some specific [traversal](https://en.wikipedia.org/wiki/Tree_traversal) of that tree when all tracks are involved. Yes, as said above, one order is by creation time (this would make getUserMedia initial tracks to be first, and then the cloned (or transferred back) tracks. This guarantees that all tracks of a context are ordered deterministically. > * The order can be a specific node only when the UA mutes just a specific track. I'd like to move away from this single track mute approach. Muted is a state of the source and should apply to all tracks of the same source. Ideally, the spec would say something like the following: when UA detects that a source gets muted, get the ordered list of tracks associated to the source and iterate through the list to queue a task to fire the mute event. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1020#issuecomment-2467937983 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 November 2024 11:25:00 UTC