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

[web-audio-api] Empty interfaces serve no purpose (#212)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:04 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/212@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17324](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17324) Tue, 05 Jun 2012 11:16:37 GMT
> Reported by Philip J├Ągenstedt
> Assigned to 

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.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/212
Received on Wednesday, 11 September 2013 14:29:33 UTC

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