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

[web-audio-api] (HTMLMediaElementIntegration): HTMLMediaElement integration (#145)

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

Audio-ISSUE-55 (HTMLMediaElementIntegration): HTMLMediaElement integration [Web Audio API]


Raised by: Philip J├Ągenstedt
On product: Web Audio API


The section "Integration with the audio and video elements" should be merged into the definition of MediaElementAudioSourceNode. Unfortunately, the combination of the two still leaves the behavior completely undefined, with only an example given and no normative requirements for implementations.

What happens when a HTMLMediaElement

 * has readyState HAVE_NOTHING?
 * is paused?
 * is seeking?
 * has no audio channels?
 * switches the active audio channel using the AudioTrack.enabled interface.
 * is muted?
 * has volume < 1?

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:29:01 UTC

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