- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Jan 2025 21:46:56 +0000
- To: public-webrtc-logs@w3.org
> ... (though it is not really t2 but t2b given transferring creates a new track). > > When posting back to window `t2` and `t4`, the creation order could be `t1, t3, t2bb, t4b` Agreed. "Transfer" is misleading, implying the original object travels. It's more like a magician’s clone-and-destroy teleportation trick where the original bird dies (to [spoil a good movie](https://movies.stackexchange.com/questions/92806/is-the-bird-killing-in-the-prestige-based-on-historical-reality)). IOW, objects stay on the thread they're created on and do not travel. So their creation order is deterministic within that thread, letting us ignore transfer. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1020#issuecomment-2599269075 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 January 2025 21:46:57 UTC