I am fully aware of this, Chrome doesn't represent the HTML5 standard, as Russell pointed out.
True, but I didn't claim that Chrome did represent the standard. You said "GM supports HTML5, yet HTML5 doesn't support the GM audio engine". I was merely pointing out that while certain browsers do not support WebAudio, Chrome does. It doesn't matter though, they left the legacy functionality in for a reason, this happens to be one of them I'm sure.
Also it would have been nice if the docs mentioned the browser issues rather than making a bunch of users find out though trial-and-error until finally reporting to the forums.
You will most likely be in for many more surprises than just audio once you get to testing heavily. Yoyo cannot cover all the bases, that's nearly impossible. There are a lot of issues for a lot of different reasons. Some do pertain to GameMaker's HTML5 implementation, but just as many don't. Each browser controls it's own implementation of HTML5, heck I believe Firefox only has HTML5 partially implemented! Since there are so many different implementations, it's hard to keep some sort of stable anything!
I'm just saying I want the engine I invested in to be stable.
Of course! I respect that, but like I mentioned above, who's fault is it really? Should GameMaker re-write the engine to comply and or operate the best for each and every browser? Or should all the browser developers just implement their HTML5 better, like Google did with Chrome?
EDIT: Also note, I'm not against you. It's just that I have looked into other game engines. I've tested games created in other engines on different browsers and almost all of them behave differently in one form or another. It's ridiculous. Trust me, I feel your pain, I wish there was some sort of standardization. Until then, I will only focus on the browser that works and inform my players.
Edited by MonkeyMaw, 22 October 2012 - 08:41 PM.