Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats

If the test is written correctly, browsers should pass when not implementing audioLevel, when implementing audioLevel according to the old spec, and when implementing audioLevel according to the new spec - because "missing" is a legal value under the test conditions we can generate using the present test framework.
It would be correct to test the negative - contributingSource MUST NOT be present when the source is another browser.

GitHub Notification of comment by alvestrand
Please view or discuss this issue at using your GitHub account

Received on Friday, 26 January 2018 08:05:42 UTC