On 10/6/14 12:39, Nils Ohlmeier wrote:
On 10/3/14 1:23 AM, [email protected] wrote:
On Sunday, September 21, 2014 3:56:32 AM UTC+8, [email protected] wrote:
Thanks Jan-Ivar for your explanation.
The warning is not a big issue by itself, nut I thought I was
missing something (I am rather new to webRTC...)
I have the other problem. When I creating offer by using
"{'mandatory': {'OfferToReceiveAudio': true, 'OfferToReceiveVideo':
true}}", FF 33 will tell me "Mandatory/optional in createOffer
options is deprecated! Use
{"offerToReceiveAudio":true,"offerToReceiveVideo":true} instead (note
the case difference)!". However, the offer is still created
successfully and function onCreateOfferSuccess is called. But if I
use "{'mandatory': {'offerToReceiveAudio': true,
'offerToReceiveVideo': true}}" to create the offer again, FF 33 will
call function onCreateSessionDescriptionError. The error is "Cannot
create SDP without any streams.".
That sounds like a bug to me, which probably got introduce when the
new constraints got implemented. If you haven't done it already I
would appreciate if you could file a bug report on Bugzilla about that.
No, this isn't a bug. What happened is that the spec for PeerConnection
no longer includes "mandatory" at al.
The string that Aslan used was "{'mandatory': {'offerToReceiveAudio':
true, 'offerToReceiveVideo': true}}"
You'll see that it still contains the word "mandatory." He didn't fix
the problem that the warning was telling him about ("Mandatory/optional
in createOffer options is deprecated").
What the error is trying to say is:
Old syntax: {'mandatory': {'OfferToReceiveAudio': true,
'OfferToReceiveVideo': true}
New syntax: {'offerToReceiveAudio': true, 'offerToReceiveVideo': true}
The new syntax has no "mandatory". It has no "optional". You just pass
the parameters you want to set. It's somewhat unfortunate that we *also*
changed the uppercase/lowercase properties of the parameter at the same
time, because it leads to this kind of confusion, but that's what happened.
Last I checked, Chrome wasn't caught up to the newest spec, and would
not accept the most recent syntax, so you may have to do some extra work
to keep your code working across both browsers.
--
Adam Roach
Principal Platform Engineer
[email protected]
+1 650 903 0800 x863
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
