Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Didn't the whole creative coding community pitch a fit when Chrome did this?


view as:

Because Chrome had bugs in how it worked, and didn't make it trivial for people to re-enable when they want audio.

I wouldn't say "bugs". It was deliberate behavior.

Chrome simply broke a lot of content on the Web, while Firefox just mutes it and lets you unmute.


Legal | privacy