>>>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.

Don't see how basing your styling on bootstrap.css makes it less consistent and you'd spend a *lot* of time developing your own @media based css to achieve what bootstrap does.

And there isn't really a 'standard DOM' - there's a 'DOM standard' and the problem is that no engines support it in full and/or correctly.

I won't try to convince to use angularsjs - but it takes nothing away and you can choose to use only the features you want.


>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!

If you add IE8 to the 9,10 & 11 market share they've over 50% of the market. Admittedly the fact that so many IE users are still on 8 implies that IE users in general seem less likely to upgrade - but I doubt that that will shrink to 11 and would guess that when IE12 arrives IE users are more likely to upgrade to that than switch. I'd also like to believe otherwise but ......

>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.

I take your point - but people may look at your app using IE and if it doesn't look good there they may not consider bothering to switch to a browser supporting Web Audio ?