It is truly annoying that you have to totally whitelist their domain even after step D in order to see the site. Some of us want to selectively enable each flash applet, dangit. #KidsGetOffMyLawn
It's actually going to be a pretty common problem as we see more and more interfaces being built _visually_ for HTML5, while audio will lag behind due to the non-standard implementations in everything but Chrome. We'll start seeing more and more libraries that do audio heavy lifting in Flash, but expose their functionality over ExternalInterface. So where do you put a small Flash applet that Flash-blocking power users might need to click on, but otherwise shows no graphics whatsoever? How do you make it easy/big-enough for Flash blockers to click, but unobtrusive enough to not intercept any DOM elements?
I'd love to see a replacement for SWFObject that just brings up a modal dialog in the case where Flash is blocked, allowing you to click-to-enable the applet.
Indeed. I'm very much looking forward to ditching flash on beatlab.com when I can.
The HTML WebAudio API isn't quite there yet, but it's making great progress. It is already deployed in Chrome, with releases in Safari and iOS on the way. I actually have a branch going that uses the WebAudio API to mix sounds and doesn't rely on flash at all.
