New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 605673 link

Starred by 4 users
Status: Duplicate
Merged: issue 709931
Owner:
guidou@chromium.org
Closed: Apr 2017
Cc:
jansson@chromium.org
█ srnarayanan@chromium.org
guidou@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

WebRTC constraints: Need to decide on the non-standard constraints.

Project Member Reported by hta@chromium.org, Apr 21 2016 
At the moment, the constraint code for MediaStreamTracks handles the following non-standard constraints:

chromeMediaSource
chromeMediaSourceId
sourceId
chromeRenderToAssociatedSink
googHotword  // see crbug/577627
googEchoCancellation
googEchoCancellation2
googAutoGainControl
googAutoGainControl2
googNoiseSuppression
googNoiseSuppression2
googBeamforming
googArrayGeometry
googHighpassFilter
googTypingNoiseDetection
googAudioMirroring
googDAEchoCancellation
googNoiseReduction
DtlsSrtpKeyAgreement
RtpDataChannels
googDscp
googIPv6
googSuspendBelowMinBitrate
googNuMUnsignalledRecvStreams
googCombinedAudioVideoBwe
googScreencastMinBitrate
googCpuOveruseDetection
googCpuUnderuseThreshold
googCpuOveruseThreshold
googCpuUnderuseEncodeRsdThreshold
googCpuOveruseEncodeRsdThreshold
googCpuOveruseEncodeUsage
googHighStartBitrate
googPayloadPadding
googLeakyBucket  // parsed but ignored - crbug.com/579729
googPowerLineFrequency

For all of these, we must decide:

- Delete them or keep them (some have already been deleted)
- Keep them only in "old style constraints" or migrate them to full-fledged, IDL-supported constraints

Today, these are only accessible in the "mandatory/optional, name=value", backwards-compatible form of constraints.

Comment 1 by tnakamura@chromium.org, Apr 22 2016

Cc: srnarayanan@chromium.org jansson@chromium.org
Labels: -Pri-3 Pri-2
Status: Available (was: Untriaged)
Setting to Available on the assumption that hta@ will drive the final decision(s) and find appropriate owner/owners. (or at least there doesn't appear to be anything the testing team needs to do at this time from a triaging perspective)

Comment 2 by ktsaregr...@atlassian.com, Jun 16 2016 

FF currently uses "moz" prefix for couple of filters: mozAutoGainControl, mozNoiseSuppression.
Those constraints are also returned by navigator.mediaDevices.getSupportedConstraints()

Comment 3 by lafo...@chromium.org, Sep 29 2016

Components: -Blink>Webrtc>GetUserMedia Blink>GetUserMedia

Comment 4 by guidou@chromium.org, Mar 6 2017

Owner: guidou@chromium.org
Status: Assigned (was: Available)

Comment 5 by guidou@chromium.org, Apr 18 2017

Mergedinto: 709931
Status: Duplicate (was: Assigned)
This will be tracked on  issue 709931 .
►

Sign in to add a comment