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 25708 - Queue getSettings, getNativeSettings, applyConstraints
Summary: Queue getSettings, getNativeSettings, applyConstraints
Status: RESOLVED WONTFIX
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-14 12:19 UTC by Stefan Hakansson LK
Modified: 2014-05-19 18:21 UTC (History)
1 user (show)

See Also:

Attachments

Description Stefan Hakansson LK 2014-05-14 12:19:01 UTC 
getSettings, getNativeSettings, applyConstraints should have an operations queue defined in the same way as PeerConnection has for every call to createOffer, setLocalDescription, createAnswer and setRemoteDescription in order to avoid reading out settings related to old constraints immediately after applying new ones.
Comment 1 Stefan Hakansson LK 2014-05-19 18:21:44 UTC 
as getSettings etc. can be synchronous this is not needed.