Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TAG Feedback: Support for 'muted' state? #188

Closed
travisleithead opened this issue Mar 20, 2017 · 2 comments
Closed

TAG Feedback: Support for 'muted' state? #188

travisleithead opened this issue Mar 20, 2017 · 2 comments

Comments

@travisleithead
Copy link
Member

[Filed in response to the request for TAG feedback]

@xxyzzzq @mounirlamouri

Should muted be included in the MediaSessionAction enum? e.g., many browsers have an option to 'mute' a tab--is this a scenario that should be supported?

@xxyzzzq
Copy link
Contributor

xxyzzzq commented Mar 24, 2017

Currently, we are mainly targeting mobile platforms. On mobile platforms, we should respect to the OS volume control, and controling the volumes of the media elements on the page should be rare.

For desktop, I think "muting a tab" should be still be handled by the UA instead of the page, as the page might ignore the muted action, then we need UA to have fallback steps to force muting. Also I think muted is less useful given that we already have pause.

@travisleithead
Copy link
Member Author

I think I agree with that. The only reason that a page might want to react, is to stop playing the media, which might allow the media stack to be unloaded in the browser, saving memory on mobile devices... but then the muted state goes away (as it's now in a stopped state) and that transition does seem a bit forced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants