Open
Bug 1363815
Opened 8 years ago
Updated 2 years ago
RTCPeerConnection: Attempting to view RTCPeerConnection.prototype contents in web console results in TypeError
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Core
WebRTC: Audio/Video
Tracking
()
NEW
People
(Reporter: rwaldron, Unassigned)
Details
Attachments
(1 file)
70.75 KB,
image/png
|
Details |
In Firefox Nightly's Web Console, I typed `RTCPeerConnection.prototype`, hit enter and then clicked on `34 more...` to expand the list. The list does not expand, instead a TypeError exception is thrown:
`TypeError: 'get peerIdentity' called on an object that does not implement interface RTCPeerConnection.`
Here's a screen shot: https://i.gyazo.com/e07f29617336329ca39e9d046efa91d0.png
Reporter | ||
Comment 1•8 years ago
|
||
Clarification: the list of properties does show in the panel on the right. The bug is ONLY the TypeError
Updated•8 years ago
|
Rank: 29
Priority: -- → P2
Comment 2•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
I'm seeing a very similar issue, the following error is printed to the console when the React DevTools extension attempts to display an RTCPeerConnection object in the sidebar.
TypeError: 'get localDescription' called on an object that does not implement interface RTCPeerConnection.
The backtrace isn't particularly useful:
backend.js:formatted
value backend.js:5238
forEach (index):262
value backend.js:5237
value backend.js:5156
value (index):974
e backend.js:3753
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•