RTCPeerConnection: peeridentity event

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 peeridentity event is sent to the connection concerned when peer identity has been set and verified on it. The new identiy can be access using the RTCPeerConnection.peerIdentity property. An event handler for this event can be added via the RTCPeerConnection.onpeeridentity property.

Bubbles No
Cancelable No
Interface Event
Event handler property onpeeridentity

Important: This event and its event handler have been removed from the specification and are no longer available. Instead of using this event to detect when an identity is available, wait for the Promise returned by RTCPeerConnection.peerIdentity to be resolved. Once resolved, its value is the new identity.

Examples

For the correct way to detect a new peer identity, see RTCPeerConnection.peerIdentity.

Specifications

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

Browser compatibility

BCD tables only load in the browser

See also