Closed
Bug 781647
Opened 12 years ago
Closed 11 years ago
Can't set onXxxx handlers in mozPeerConnection (on alder)
Categories
(Core :: WebRTC, defect)
Core
WebRTC
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jesup, Assigned: anant)
References
Details
(Whiteboard: [WebRTC], [blocking-webrtc-])
Setting an onXxxx attribute (such as onAddTrack) fails with NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN: Cannot modify properties of a WrappedNative This appears to be caused by IPeerConnectionObserver's methods being instantiated by xpconnect and added to mozPeerConnection (it appears).
|
Assignee | |
Comment 1•12 years ago
|
||
When we are able to extend EventTarget in JS, we should be able to solve this.
Depends on: 731746
|
||
Updated•12 years ago
|
Whiteboard: [WebRTC], [blocking-webrtc+]
|
Reporter | |
Comment 2•12 years ago
|
||
marking non-blocking. I believe we've worked around this, at most we have some leakage of unsettable properties into mozRTCPeerConnection - and I'm not sure it's still even visible to the outside world.
Whiteboard: [WebRTC], [blocking-webrtc+] → [WebRTC], [blocking-webrtc-]
|
|
Reporter | |
Comment 3•11 years ago
|
||
Fixed long ago
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•