Skip to content

[mediaqueries] Discover muted state #5607

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

Open
Crissov opened this issue Oct 12, 2020 · 5 comments
Open

[mediaqueries] Discover muted state #5607

Crissov opened this issue Oct 12, 2020 · 5 comments

Comments

@Crissov
Copy link
Contributor

Crissov commented Oct 12, 2020

Most media queries are about graphics, video, color and other display characteristics. Since media types have been found to be too broad to be useful, the sound-related speech and aural are among the deprecated ones.

However, even if your styles only cover visual aspects, it can still be useful to know whether the user will hear any sounds on the site at all, e.g. when deciding whether (and how) to show video subtitles automatically. I therefore propose a new media query for that, e.g.:

  • sound-volume: mute | quiet | loud | auto

This is different from #3933 and #3821 which deal with the state of media elements, not the browser, window or tab as a whole.

@tabatkins
Copy link
Member

Hm, being able to automatically turn on subtitles when the tab is muted does sound like a reasonable use-case.

Do you have a good use-case for distinguishing quiet/load volume level? I can't immediately think of one, and it would definitely make the feature more complex to specify, vs just "capable of playing sound" and "muted".

@Crissov
Copy link
Contributor Author

Crissov commented Oct 13, 2020

Actually no, I have no good use-case for distinguishing quiet/loud volume levels.

@hober
Copy link
Member

hober commented Apr 16, 2021

Hm, being able to automatically turn on subtitles when the tab is muted does sound like a reasonable use-case.

It sounds like behavior that could (or maybe should) be the UA default behavior. If it's a good idea, it's a good idea even on sites where the author hasn't thought of it (which would be the vast majority of sites even in a world with this author-facing feature).

So, while I think the use case is totally legit and worth addressing, I suspect the right path forward is to simply file feature requests on the browsers to adopt this kind of behavior by default.

@tabatkins
Copy link
Member

That assumes subtitles are solely coming from the video file, and not rendered outside by a separate script, yeah?

@hober
Copy link
Member

hober commented Apr 22, 2021

That assumes subtitles are solely coming from the video file, and not rendered outside by a separate script, yeah?

Yes, I wasn't thinking of that case.

@Crissov Crissov changed the title [MQ] Discover muted state [mediaqueries] Discover muted state Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants