> There might be some benefit from a central definition for the concept of a **tainted** track For simplicity, I would prefer we stick with muted/ended notions in specs. Adding another tainted notion adds extra complexity. muted/ended also have the nice property to be exposed to web pages. I would be ok with a tainted notion if we have good enough use cases. So far, it seems that: - Isolated streams could well be muted. Sending a received isolated stream does not seem very appealing. - video element tainted content track seems to be implemented very similarly to muted in Firefox. Safari does not implement it. Not sure about Chrome. > Other sources of media could - at least in theory - change origin and later become readable _to someone_, so they provide a stream. muted could well handle that. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/529#issuecomment-722942299 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Friday, 6 November 2020 08:14:30 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:52 UTC