My point is its a personal choice. I’m not fan of all the telling that goes on with music. Take one of my personal sites for instance. This was fun site I did for myself basically. Guess I just didn’t care about the people that go to libraries to surf. Plus it fits this site. Or at least that’s the type of vibe I wanted to give off. http://www.ericwwatson.com/
One other thing….If you go down the route of NOT having sound by default then then the option should be given in a special section of the page (perhaps in the header or at the top of an aside) to say something like…”We have sound…click here to enable”.
Couldn’t agree more @chanman. I’m new around here and have no wish to make enemies but I just think that, because clients are paying us money to do something, we should do it. It should be part of our responsibility to them to advise them on the best way to do things on the web and give good reasons why their original idea may be a bad move and what they could do to better serve their users. Ultimately however, if we call ourselves web designers we should do anything people want that involves developing on the web (personally I’d draw the line at table-based layout though!). Hence me providing the code I did.
I’m not going to get into the debate (I think it’s a situational thing), but if you give them an option to turn it on, also give them an option to turn it off if they *have* turned it on. Listening to the same short loop of music or the client’s radio ad gets really old after a while.
Back in the days when inflicting music on your viewers was the “in” thing, weren’t there options provided usually for turning the music on or off at will?