While I agree that the article does a poor job at explaining why they are affected by the changes in the Audio API, I advise you to visit the chromium bug tracker issue [1] and check for yourself how many user/libraries/pages are affected by the problem:
No comments yet.