This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22273 - "When track constraints change" should be better described, referred from applyConstraints
Summary: "When track constraints change" should be better described, referred from app...
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-04 21:43 UTC by Dominique Hazael-Massieux
Modified: 2014-04-03 13:07 UTC (History)
2 users (show)

See Also:


Attachments

Description Dominique Hazael-Massieux 2013-06-04 21:43:17 UTC
4.3.2 describes what a UA MUST and should do "when track constraints change".

At the very least, this should be referred from the applyConstraints() method description.

The said description should be following a step-by-step algorithm, and incorporate some of the conformance requirements currently described in section "The model: sources, sinks, constraints, and states" (e.g. the dispatching of an overconstrained event).

The same 4.3.2 says "Similarly, if the sourceType changes, then the user agent should perform the same actions to re-evaluate the constraints of each track affected by that source change."

It's not clear whether it is meant to be a SHOULD rather than a should, or even maybe a MUST; it's not clear to me what could make a sourceType change in the first place.
Comment 1 Adam Bergkvist 2013-10-07 07:48:25 UTC
Depends on the Constrainable interface [1].

[1] http://lists.w3.org/Archives/Public/public-media-capture/2013Oct/0027.html
Comment 2 Dominique Hazael-Massieux 2014-04-03 13:07:39 UTC
Seems to be fixed now in latest editors draft.