- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 15 Nov 2012 10:51:44 -0800
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: Marcos Caceres <w3c@marcosc.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Thu, Nov 15, 2012 at 8:37 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > Frankly, I think the prior API art here is broken, and I think the WebAudio > spec editors think that too. Now obviously for existing APIs that's water > under the bridge... I see. It was a deliberate choice to make these not throw. E.g. if you add new values later on, they would start throwing in older browsers which would not necessarily be an improvement for the end user. Adding this conditional also gives choice, which will fragment the platform a little more as people will just pick differently depending on their preference. Having said that, it seems that is happening already. -- http://annevankesteren.nl/
Received on Thursday, 15 November 2012 18:52:12 UTC