Obsolete
This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.
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, simply 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
| Desktop | Mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
peeridentity event | Chrome No support No | Edge No support ≤18 — 79 | Firefox Full support 22 | IE No support No | Opera Full support 43 | Safari ? | WebView Android No support No | Chrome Android No support No | Firefox Android Full support 44 | Opera Android Full support 43 | Safari iOS ? | Samsung Internet Android Full support 6.0 |
Legend
- Full support
- Full support
- No support
- No support
- Compatibility unknown
- Compatibility unknown
- Deprecated. Not for use in new websites.
- Deprecated. Not for use in new websites.