Issue 412345 in chromium: w3c stream-api/introduction/disabled-audio-silence.html checks audio immediately

[chro...@googlecode.com]

Status: Untriaged
Owner: phog...@chromium.org
Labels: Type-Bug Pri-2 Cr-Blink-WebRTC OS-All

New issue 412345 by pe...@chromium.org: w3c
stream-api/introduction/disabled-audio-silence.html checks audio immediately
https://code.google.com/p/chromium/issues/detail?id=412345

It looks like this test immediately checks the current audio buffer for
silence.

Shouldn't the test use WebAudio to produce an input MediaStream to make
sure it has an input signal and wait for x buffers after disabling the
audio track that audio is silent?

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Issue 412345: w3c stream-api/introduction/disabled-audio-silence.html

checks audio immediately
https://code.google.com/p/chromium/issues/detail?id=412345

This issue is now blocking issue chromium:405520.
See https://code.google.com/p/chromium/issues/detail?id=405520

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: Duplicate

Comment #7 on issue 412345 by h...@chromium.org: w3c

stream-api/introduction/disabled-audio-silence.html checks audio immediately
https://code.google.com/p/chromium/issues/detail?id=412345

Full link to source:

https://github.com/w3c/web-platform-tests/blob/master/mediacapture-streams/stream-api/introduction/disabled-audio-silence.html

Filed https://github.com/w3c/web-platform-tests/issues/2311 to track the
issue in the W3C repo; closing the issue here. ("Duplicate" is a bit odd
given that the duplicate is in another repo, but seems the least
inappropriate status.)