This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Audio-ISSUE-21 (EmptyInterfaces): Empty interfaces serve no purpose [Web Audio API] http://www.w3.org/2011/audio/track/issues/21 Raised by: Philip Jägenstedt On product: Web Audio API There are currently a number of empty interfaces: interface AudioSourceNode : AudioNode { } interface AudioGain : AudioParam { }; interface MediaElementAudioSourceNode : AudioSourceNode { } interface AudioChannelSplitter : AudioNode { }; interface WaveTable { } (Copied verbatim, note the inconsistent indentation.) These interfaces will be visible in the global namespace (the Window object) but serve no apparent purpose. In HTML, elements that do not have any special DOM interface are simply HTMLElement, a model we suggest to follow.
Comment from Philip in http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0210.html « An example of this is AudioProcessingEvent.node, which is not readonly while the other members are, for no apparent reason. »
AudioSourceNode and AudioGain have been removed since there is no concrete object for these types. I believe it's important to keep the others mentioned since they are concrete and very specific node types where specific instances can be created. Fixed: https://dvcs.w3.org/hg/audio/rev/827140b23ed9
(Should be marked as resolved)
No objection since resolution announced. Closing.