Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

constraint properties should not be scoped to "source" only #69

Closed
ShijunS opened this issue Nov 8, 2014 · 0 comments
Closed

constraint properties should not be scoped to "source" only #69

ShijunS opened this issue Nov 8, 2014 · 0 comments
Assignees

Comments

@ShijunS
Copy link
Contributor

ShijunS commented Nov 8, 2014

[Section 14.1] In the “video” property table, the spec has the following for the "width" property, “The width or width range, in pixels, of the video source.”

Since constraints can be applied to track (not directly to the “source”), I’d suggest removing “of the video source”, so the definition becomes, "The width or width range in pixels."

There are two other places in the table, i.e. for "height" and "frameRate", which have the same issue.

dontcallmedom added a commit to dontcallmedom/mediacapture-main that referenced this issue Nov 24, 2014
dontcallmedom added a commit to dontcallmedom/mediacapture-main that referenced this issue Nov 24, 2014
instead describe members of MediaTrackConstraints dictionary
close w3c#30 and w3c#69 (supersedes w3c#84)
burnburn added a commit that referenced this issue Feb 6, 2015
constraint properties should not be scoped to 'source' only; close #69
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants