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

Issue 709931 link

Starred by 7 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 1
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Task


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

Support for nonstandard constraints using the standard constraint syntax

Project Member Reported by guidou@chromium.org, Apr 10 2017

Issue description

Change description:
Support chrome-specific constraints using the new spec-compliant constraint syntax. They are already supported using an older syntax.

Changes to API surface:
Add the following fields to MediaTrackConstraintSet and MediaTrackSupportedConstraints.

Audio and video:
* chromeMediaSource

Video only:
* googPowerLineFrequency
* googNoiseReduction

Audio only:
* chromeRenderToAssociatedSink
* googAutoGainControl
* googExperimentalAutoGainControl
* googNoiseSuppression
* googHighpassFilter
* googTypingNoiseDetection
* googExperimentalNoiseSuppression
* googBeamforming
* googArrayGeometry
* googAudioMirroring
* googNoiseReduction


Links: https://w3c.github.io/mediacapture-main/
Public standards discussion: 

Support in other browsers:
Internet Explorer: No
Firefox: Has support for nonstandard constraints specific to firefox.
Safari: No

 
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 13 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fe1505549280fe1b7e4b7a4c5907a71b66a8c809

commit fe1505549280fe1b7e4b7a4c5907a71b66a8c809
Author: guidou <guidou@chromium.org>
Date: Thu Apr 13 17:31:05 2017

Count usage of mediastream audio and video constraints.

This will help ascertain which nonstandard constraints are good
candidates for standardization.

BUG= 709931 

Review-Url: https://codereview.chromium.org/2810233003
Cr-Commit-Position: refs/heads/master@{#464454}

[modify] https://crrev.com/fe1505549280fe1b7e4b7a4c5907a71b66a8c809/third_party/WebKit/Source/core/frame/UseCounter.h
[modify] https://crrev.com/fe1505549280fe1b7e4b7a4c5907a71b66a8c809/third_party/WebKit/Source/modules/mediastream/UserMediaRequest.cpp
[modify] https://crrev.com/fe1505549280fe1b7e4b7a4c5907a71b66a8c809/tools/metrics/histograms/histograms.xml

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

Cc: jansson@chromium.org srnarayanan@chromium.org guidou@chromium.org
 Issue 605673  has been merged into this issue.

Comment 3 by owe...@chromium.org, Sep 12 2017

Labels: migrated-launch-owp Type-Task
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge
Status: WontFix (was: Assigned)
We will not implement nonstandard constraints with standard syntax.
If necessary, we will request standardization of some of the old goog constraints. 

Sign in to add a comment