RTCRtpTransceiver.stopped

Deprecated

This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

The read-only stopped property on the RTCRtpTransceiver interface indicates whether or not the transceiver's associated sender and receiver have both been stopped.

The transceiver is stopped if the stop() method has been called or if a change to either the local or the remote description has caused the transceiver to be stopped for some reason.

Syntax

var isStopped = RTCRtpTransceiver.stopped;

Value

A Boolean value which is true if the transceiver's sender will no longer send data, and its receiver will no longer receive data. If either or both are still at work, the result is false.

Usage notes

This property is deprecated and will be removed in the future. Instead, look at the value of currentDirection. Its value is stopped if the transceiver has stopped.

Note: Currently only Firefox implements stopped, and has not yet been updated to implement this change.

Specifications

Specification Status Comment
WebRTC 1.0: Real-time Communication Between Browsers
The definition of 'RTCRtpTransceiver.stopped' in that specification.
Candidate Recommendation

Browser compatibility

BCD tables only load in the browser

See also