17324 2012-06-05 11:16:37 +0000 Empty interfaces serve no purpose 2013-05-14 10:24:08 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified PC All CLOSED FIXED P2 normal TBD 21511 1 philipj dave.null crogers olivier.thereaux public-audio dave.null oldest_to_newest 68633 0 philipj 2012-06-05 11:16:37 +0000 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. 68807 1 olivier.thereaux 2012-06-07 14:36:55 +0000 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. » 85760 2 crogers 2013-04-09 00:47:55 +0000 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 86799 3 olivier.thereaux 2013-04-25 15:57:10 +0000 (Should be marked as resolved) 87638 4 olivier.thereaux 2013-05-14 10:24:08 +0000 No objection since resolution announced. Closing.