>>Yeah, Since my apps don't work if the browser doesn't support Web Audio API, I have the luxury of designing for HTML5 only and thus the vast majority of browser quirks are none of my concern :-).
>
>>My heart goes out to web designers that have to support Internet Explorer
>
>Hmm. I'm also working on a 'HTML5 only' site at the moment (needs GeoLocation) but I'm not going to assume that there are no quirks on some browsers.

True, and the Web Audio is maybe a good example of that. It's a changing spec, I think supposed to approved around 2020?

So older iPhones have audioContext.noteOn() whereas newer implementations have audioContext.start(), because the spec changed.

So there are definitely some quirks. Write once, debug everywhere still applies.

But at least when it comes to having a standard DOM, and consistent CSS I'm in the clear completely.

I only have to focus on the code that is unique to my app.


>And are you saying your not going to support IE when it gets Web Audio API - IE9,10 & 11 combined have ~30% of the market ?

Well, 9 10 and 11 won't get it:

http://connect.microsoft.com/IE/feedback/details/799529/web-audio-api-support#

If IE12 does, the eleven people left using IE by then will be supported!

But what I'm saying is, if the browser supports Web Audio, it will be current enough with HTML/CSS/JS that I won't have to explicitly support it, it will be modern and consistent and supported implicitly.