I think the way that it works is that by default sound is muted, but browsers allow onClick event handlers to unmute the tab.

So if you have a page that tries to make sound after it has loaded but there has been no user interaction, it will be muted.

But as soon as you interact with the page, all bets are off.

The sound is annoying and does not add much to selecting an item. All the features look small when selecting them, so hard to to see the differences until clicking. So trying out a bunch of different ones combined with the sound was irksome. I'm not sure how you test with it on, I turned off my speaker.

Since forever. The lack of "muted by default" behaviour is very frustrating. It's also implemented per-tab rather than per-domain. What the hell? I want all sound directed to /dev/null by default with the option for me to enable it. In 100% of instances I will know whether I want sound to play before the sound actually plays.

I've a feeling they can't do it because websites would complain, though. You can use all free software and other people will still find a way to control your computer.

Hey, the developer here!

You can disable the sound by just clicking the sound icon.

Ok, but why is there sound in the first place? What does it add to the experience other than confusion and frustration?

i liked the sound.