Fix WebRTCPeerConnection set_local_description doc
ice_candidate_created should be emitted after set_local_description no
matter the type of the description (assuming no error is returned of
course).
(cherry picked from commit 39bcbf5690
)
This commit is contained in:
parent
ae67ec3ece
commit
0db5315f8a
1 changed files with 1 additions and 1 deletions
|
@ -120,7 +120,7 @@
|
||||||
</argument>
|
</argument>
|
||||||
<description>
|
<description>
|
||||||
Sets the SDP description of the local peer. This should be called in response to [signal session_description_created].
|
Sets the SDP description of the local peer. This should be called in response to [signal session_description_created].
|
||||||
If [code]type[/code] is [code]answer[/code] the peer will start emitting [signal ice_candidate_created].
|
After calling this function the peer will start emitting [signal ice_candidate_created] (unless an [enum Error] different from [constant OK] is returned).
|
||||||
</description>
|
</description>
|
||||||
</method>
|
</method>
|
||||||
<method name="set_remote_description">
|
<method name="set_remote_description">
|
||||||
|
|
Loading…
Reference in a new issue