In this case the why is rather irrelevant, all the major browser has and have had their horrible sides that's made life hell for web designers and developers. While they've all generally gotten better there's still loads of quirks and differences with all of them that we have to try and account for, not to mention the number of "outdated" browser still in use.
We've been able to adapt and find working solutions in the past, that should hardly be any different now.
Sound on webpages has actually work fine, but that is also fairly irrelevant in the grand design of it all, as sound has been considered a rather annoying thing to have on webpages, games would probably one of the few exceptions where it would be acceptable.
If you want to drag out all the annoying things that browsers have had over the years i'd have to say the differences they've all made us struggle with in regards to javascripts and specially css would be far far worse. Except in a few cases they've mostly been down to older IE versions, mostly due to Microsoft wanting to dictate the path instead of the standards. IE/Microsoft has had to give up on that too in their later versions, but due to the nature of windows, IE and how updating is done and require we're still forced to struggle with all those "problems" as ppl still use all those versions.
"Newest" IE version you can get on XP is 8...neither 9 or 10 works (officially) and IE 8 has loads of issues that designers/developers have to deal with, and there's A LOT of XP users still around, who can blame them tbh, it's a stable and fairly good.
Opera has it's issues too, its javascript handling causes several issues if you try specific things, thankfully not too commonly used things, and it's cookie handling is...horrible.
Thankfully updated version at least work on any OS version so any bugs/etc is probably gonna be fixed and updating isn't an expense...same goes for most browsers with the exception of IE (os dependent and new os == cost)
Over the years i've had countless of this issues to deal with, if it's not one browser it's the other, or it's down to the bloody OS...eventually you get to a point that it's far far far less work, effort and time consuming to just fix it, work around it, or just do it in a different way than to spent time and effort to complain about it. It's rather rare that there isn't a fairly simple solution to the problems and in many cases it's as simple as: "This works 99.9%, and for the 0.1% it doesn't break, it doesn't cause any problems, they simply don't know about/see this function/look/etc, so it's not really a problem"
With how many "new" ways there's to view/access webpages now you'll eventually go crazy if you plan on having a simple "one size/design/function/whatever fits all". There's so many different OS, browsers and handling combinations it's a nightmare.
If you skipped everything else, at least read this next bit.As for games etc, i'm sure many won't care if there's sound or not, ofc it can add to the game etc, but it can also be annoying, users have different views and opinions, so regardless of format, there should be an on/off switch.
As for the format itself, while there's ways to make just about any work, but the question here has generally be between ogg and mp3.
Unless you specifically use 128kbits MP3 files, ogg would be a better format, at higher or lower bitrates ogg would be better than mp3. I'm not saying that in support of one or the other i'm just pointing it out. To me the format chosen is irrelevant.
So far everything i've ranted on about has been a general, but i want to make one small point to tlaero:
You say that developers like you've had to reencode their sounds just for firefox, i'm gonna assume your "sounds" have been in mp3, and you blame firefox for this.
There's a slightly flaw in that and it can also be twisted around. Firefox isn't the only browser that didn't support mp3, Opera didn't/doesn't either, so you can't just blame firefox for it.
The twist is that consider those on the other side, those that had their sounds in ogg...
IE, chrome and safari supported MP3...Firefox, Opera and chrome supported OGG...so that means that regardless of which of those two formats you had, you would support 3 browsers while fail for 2 others. So neither "side" can technically claim that the other is making things difficult. While this "balance" is like to change (has changed), it's been an issue for a while so your complaints and blame of firefox for it doesn't quite hold up. And the developers on the "other" side of you would face the exact same issues as you.
All in all this goes back to my point about "it's not worth the effort", we as developers will always face issues and we'll just have to learn to live with it, no sense getting worked up about it.

(Before anyone thinks to put my in any "camp", i for the most part use mp3 and my primary browser is Firefox, so i'm standing fairly well planted with one foot on either side :P)
Rant ended, hopefully...sorry about the long spam
