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:40 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/115/24244298@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=19902#2) by Chris Rogers on W3C Bugzilla. Fri, 16 Nov 2012 18:41:46 GMT

(In reply to [comment #2](#issuecomment-24244293))
> We're considering enabling Web IDL enum attribute setters to throw if passed
> an invalid value, which would mean that we'll get what I'm asking for here
> for free.  And yes, I still think that using Web IDL enums would be a good
> change because of the increase in code readability and the possibilities of
> using the IDL parser to do various sorts of checking for the implementers.
> However I don't think that it would be very good for us to allow setting
> these both as integers and strings...  How did WebKit deal with the other
> breaking changes that was recently made in the spec (such as renaming
> functions, etc.)?

For the recent name changes such as noteOn() -> start(), WebKit continues to provide legacy support, which can eventually be phased out during a transition period.  I added a section in the spec called "Deprecation Notes" to make note of these types of changes.  Different implementations may choose to support or not support the legacy names, and for how long they would be supported.

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