This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
as getSettings etc. can be synchronous this is not needed.