youennf

In Safari, capture tracks are ended when going to page cache and the ended event is enqueued. It may only fire on revival. There is no specific handling for other...

> ```idl > Promise unmute(); > ``` `unmute()` method seems fine. I wonder whether we should not try to introduce a `mute()` method as well. This would allow the website...

`track.unmute()` makes sense if we think this is useful for all source types. For WebRTC or canvas tracks, this does not make sense. For screen sources, I am unclear yet...

Alternative to `InputDeviceInfo` is `navigator.mediaDevices.requestUnmute(deviceId)`

I am not sure how much we need a mute reason. Distinct requestUnmute failures might be sufficient.

The mute reasons may vary within the muted period and firing mute events when only the reason is changing is not really appealing. The flow of user trying to unmute...

> Does this mean you support the approach of having an attribute for the mute cause? I see this as a potential improvement while I see an API to request...

@guidou and I seem to agree on focusing on the following items (sorted by priority): - Expose something like `requestUnmute` as this is required to solve double-mute. - Evaluate the...

Exposing mute reasons may expose private information that the user may not want to expose, for instance the fact that the user will take a phone call in the middle...

We should first decide the long term goal. In general, it seems we want universal transferability and user agents already have the infrastructure to efficiently transfer audio and video cross...