W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: [web-audio-api] Clarify what happens if you set PannerNode.{panningModel,distanceModel} to an invalid value (#115)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:42 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/115/24244308@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=19902#4) by Chris Rogers on W3C Bugzilla. Fri, 16 Nov 2012 19:58:19 GMT

(In reply to [comment #4](#issuecomment-24244303))
> OK.  Can the same approach be taken about the numeric attributes?

Yes, for the "enum" type attributes I think so.  The only gotcha is that the "getters" would now return a string instead of an integer.  But I think the main backwards compatibility concern is people setting these attributes, so I'm not so worried about that.

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:30:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC