-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(NamingInconsistency): Interface naming inconsistency #219
Comments
Here is a suggested re-naming which is more consistent. Using this naming, "Audio" is still present in AudioBufferSourceNode because "AudioBuffer" is the name of the object used by this node. "Audio" is still present in MediaElementAudioSourceNode and MediaStreamAudioSourceNode because it's important to distinguish audio from video. AudioBufferSourceNode |
(In reply to comment #1) Sounds good to me. |
Thanks Marcus, fixed: |
OP and editor happy with changes. |
Audio-ISSUE-25 (NamingInconsistency): Interface naming inconsistency [Web Audio API]
http://www.w3.org/2011/audio/track/issues/25
Raised by: Marcus Geelnard
On product: Web Audio API
The naming of interfaces, such as different types of audio nodes, is quite inconsistent.
For instance:
The text was updated successfully, but these errors were encountered: