Bug 144088
| Summary: | CreatePeerConnection API cannot pass null server argument | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Adam Tiamiou <adam.tiamiou> |
| Component: | Bindings | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | jonlee, youennf |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Adam Tiamiou
When we do, in the minibrowser, the instruction "new RTCPeerConnection(servers, pcConstraint);" with "servers = null;" the inspector show "TypeError: RTCPeerConnection argument must be a valid Dictionary"
We have found that this error was raised in JSRTCPeerConnectionCustom.cpp line 59. We think the problem is related to the instruction "rtcConfiguration.isObject()" Line 58.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jon Lee
Spec has changed a bit since this was first reported.
youenn fablet
Instead of doing "new RTCPeerConnection(servers, pcConstraint);", you might need to use https://www.w3.org/TR/webrtc/#dom-rtcconfiguration dictionary.
That would end-up with something like: "new RTCPeerConnection({iceServers: servers, ... });"
Also "servers" must use "urls" and not "url" as per https://www.w3.org/TR/webrtc/#dom-rtciceserver.