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

add visual indication that chrome has muted #2

Open
ajoslin103 opened this issue Feb 18, 2020 · 7 comments
Open

add visual indication that chrome has muted #2

ajoslin103 opened this issue Feb 18, 2020 · 7 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@ajoslin103
Copy link

add visual indication that chrome has muted

then you can mute&unmute the site to get the sound back.

(god I love this thing 🥇

@nickdotht
Copy link
Owner

Hey there, thanks for the feedback. And yeah, I'm loving it too :)

If I understand correctly, you want it to display some kind of badge that indicates whether the current tab is muted or not. Correct?

@nickdotht nickdotht self-assigned this Feb 18, 2020
@nickdotht nickdotht added the enhancement New feature or request label Feb 18, 2020
@ajoslin103
Copy link
Author

ajoslin103 commented Feb 18, 2020 via email

@nickdotht
Copy link
Owner

Ah, yeah, I noticed this error. It's about the AudioContext API. Chrome pauses the sound by default until the user interacts with the page. I'll find a turnaround for this. Meanwhile, I added this to the TODO list on the README.

@nickdotht nickdotht added the bug Something isn't working label Feb 18, 2020
@ajoslin103
Copy link
Author

ajoslin103 commented Feb 18, 2020 via email

@nickdotht
Copy link
Owner

Ah, this is possible, sort of. It only shows up if the page is muted AND is playing a sound tho.

You can mute a page/tab by right clicking on the tab and selecting "Mute Site", but it won't show up the muted speaker icon until the tab starts playing a sound.

@ajoslin103
Copy link
Author

ajoslin103 commented Feb 18, 2020 via email

@nickdotht
Copy link
Owner

I believe it's because I'm using the AudioContext API the wrong way for now. I'll try to fix this issue on my next iteration and hopefully you won't have to do this anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants