Bug 1643027 Comment 8 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I'm not saying it would be impossible, but would require a clear model of how it should work, and likely spec support and buy-in from other vendors.

E.g. we might be able to experiment with *user-gesture* + `track.enabled = true` to unmute browser-mute, but since browsers aren't allowed to touch the `track.enabled` state, it would still require site involvement today, e.g. minimally
```js
track.onmute = () => updateMyIndicators(track.enabled = false);
```
Revision 1 by
on 
I'm not saying it would be impossible, but would require a clear model of how it should work, and likely spec support and buy-in from other vendors.

E.g. we might be able to experiment with *user-gesture* + `track.enabled = true` to unmute browser-mute, but since browsers aren't allowed to touch the `track.enabled` state, it would still require site involvement today, e.g. minimally
```js
track.onmute = () => updateMyIndicators(track.enabled = false);
track.onunmute = () => updateMyIndicators(track.enabled = true);
```
Revision 2 by
on 
I'm not saying it would be impossible, but would require a clear model of how it should work, and likely spec support and buy-in from other vendors.

E.g. we might be able to experiment with *user-gesture* + `track.enabled = true` to unmute browser-mute, but since browsers aren't allowed to touch the `track.enabled` state, it would still require site involvement today, e.g. minimally
```js
track.onmute = () => updateMyIndicator(track.enabled = false);
track.onunmute = () => updateMyIndicator(track.enabled = true);
```
Revision 3 by
on 
I'm not saying it would be impossible, but would require a clear model of how it should work, and likely spec support and buy-in from other vendors.

E.g. we might be able to experiment with *user-gesture* + `track.enabled = true` to unmute browser-mute, but since browsers aren't allowed to touch the `track.enabled` state, it would still require site involvement today, e.g. minimally
```js
track.onmute = () => updateMyIndicator(track.enabled = false);
track.onunmute = () => updateMyIndicator(track.enabled = true);
button.onclick = () => updateMyIndicator(track.enabled = !button.checked);
```

Back to Bug 1643027 Comment 8