Just look at how many revisions the W3 spec has had. It had even more churn that wasn't visible there... IIRC it originally shipped with synchronous audio decoding on the main thread for some reason. Chrome has also shipped multiple p0/p1 level bugs in Web Audio that users had to wait weeks or months for fixes to, like a while back when they introduced a priority inversion while rewriting their whole mixer so audio was just completely broken for a double-digit % of their userbase.

They also treated basic use cases like 'pause a piece of playing audio' as out of scope, which is simply bizarre.

Every web app or port I've ever touched had issues caused by the poor design and quality of the API.