Closed
Bug 1098015
Opened 10 years ago
Closed 9 years ago
Need to not fail on seeing RTCAnswerOptions in CreateAnswer
Categories
(Core :: WebRTC: Signaling, defect, P4)
Core
WebRTC: Signaling
Tracking
()
RESOLVED
FIXED
mozilla42
Tracking | Status | |
---|---|---|
firefox42 | --- | fixed |
backlog | webrtc/webaudio+ |
People
(Reporter: bwc, Assigned: jib)
References
(Blocks 2 open bugs, )
Details
Attachments
(2 files)
Word is that W3C is moving toward having an RTCAnswerOptions param on createAnswer.
Reporter | ||
Comment 1•9 years ago
|
||
I think this boils down to support for VoiceActivityDetection.
Updated•9 years ago
|
backlog: --- → webRTC+
Comment 2•9 years ago
|
||
there is a more immediate problem, see https://github.com/webrtc/apprtc/pull/162#discussion-diff-34814044 When calling this.pc_.createAnswer({mandatory:..., optional: ...}) Firefox errors out since it interprets this as a callback and does not find an error callback. From discussion with jib on a similar issue in createOffer a while ago we concluded that webidl can't tell the difference between function and object. Even if it's a no-op, not throwing an error in that case would be good.
Assignee | ||
Comment 3•9 years ago
|
||
The error in comment 2 is: TypeError: Not enough arguments to mozRTCPeerConnection.createAnswer. I'll submit a patch here to support the optional (no-op) argument to createAnswer. I've opened Bug 1184712 to track voiceActivityDetection.
Assignee | ||
Comment 4•9 years ago
|
||
Bug 1098015 - make createAnswer tolerate (no-op) options argument.
Attachment #8634935 -
Flags: review?(docfaraday)
Attachment #8634935 -
Flags: review?(bzbarsky)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jib
Updated•9 years ago
|
Attachment #8634935 -
Flags: review?(bzbarsky) → review+
Comment 5•9 years ago
|
||
Comment on attachment 8634935 [details] MozReview Request: Bug 1098015 - make createAnswer tolerate (no-op) options argument. https://reviewboard.mozilla.org/r/13477/#review12095 Ship It!
Reporter | ||
Comment 6•9 years ago
|
||
Comment on attachment 8634935 [details] MozReview Request: Bug 1098015 - make createAnswer tolerate (no-op) options argument. https://reviewboard.mozilla.org/r/13477/#review12097 ::: dom/media/PeerConnection.js:697 (Diff revision 1) > - createAnswer: function(onSuccess, onError) { > + createAnswer: function(optionsOrOnSuccess, onError) { > + let onSuccess, options; > + if (typeof optionsOrOnSuccess == "function") { > + onSuccess = optionsOrOnSuccess; > + } else { > + options = optionsOrOnSuccess; > + } I think it would be helpful to comment why we're doing this.
Attachment #8634935 -
Flags: review?(docfaraday) → review+
Assignee | ||
Updated•9 years ago
|
Assignee | ||
Comment 7•9 years ago
|
||
https://reviewboard.mozilla.org/r/13477/#review12097 > I think it would be helpful to comment why we're doing this. It's similar to what we're already doing on createOffer, but I'll add a comment to both.
Assignee | ||
Comment 8•9 years ago
|
||
Comment on attachment 8634935 [details] MozReview Request: Bug 1098015 - make createAnswer tolerate (no-op) options argument. Bug 1098015 - make createAnswer tolerate (no-op) options argument.
Attachment #8634935 -
Flags: review?(docfaraday)
Attachment #8634935 -
Flags: review?(bzbarsky)
Attachment #8634935 -
Flags: review+
Assignee | ||
Comment 9•9 years ago
|
||
Bug 1098015 - modify a test to make sure createAnswer({}) works.
Attachment #8634976 -
Flags: review?(docfaraday)
Assignee | ||
Updated•9 years ago
|
Attachment #8634935 -
Flags: review?(docfaraday)
Attachment #8634935 -
Flags: review?(bzbarsky)
Attachment #8634935 -
Flags: review+
Reporter | ||
Comment 10•9 years ago
|
||
Comment on attachment 8634976 [details] MozReview Request: Bug 1098015 - modify a test to make sure createAnswer({}) works. r=bwc https://reviewboard.mozilla.org/r/13493/#review12181 ::: dom/media/tests/mochitest/test_peerConnection_promiseSendOnly.html:41 (Diff revision 1) > - .then(() => pc1.createOffer()) > + .then(() => pc1.createOffer({})) > .then(offer => pc1.setLocalDescription(offer)) > .then(() => pc2.setRemoteDescription(pc1.localDescription)) > - .then(() => pc2.createAnswer()) > + .then(() => pc2.createAnswer({})) Couldn't hurt to have a comment here explaining why you're doing this.
Attachment #8634976 -
Flags: review?(docfaraday) → review+
Assignee | ||
Updated•9 years ago
|
Attachment #8634935 -
Flags: review?(docfaraday)
Attachment #8634935 -
Flags: review?(bzbarsky)
Attachment #8634935 -
Flags: review+
Assignee | ||
Comment 11•9 years ago
|
||
Comment on attachment 8634935 [details] MozReview Request: Bug 1098015 - make createAnswer tolerate (no-op) options argument. Bug 1098015 - make createAnswer tolerate (no-op) options argument.
Assignee | ||
Updated•9 years ago
|
Attachment #8634976 -
Attachment description: MozReview Request: Bug 1098015 - modify a test to make sure createAnswer({}) works. → MozReview Request: Bug 1098015 - modify a test to make sure createAnswer({}) works. r=bwc
Attachment #8634976 -
Flags: review+ → review?(docfaraday)
Assignee | ||
Comment 12•9 years ago
|
||
Comment on attachment 8634976 [details] MozReview Request: Bug 1098015 - modify a test to make sure createAnswer({}) works. r=bwc Bug 1098015 - modify a test to make sure createAnswer({}) works. r=bwc
Assignee | ||
Updated•9 years ago
|
Attachment #8634935 -
Flags: review?(docfaraday)
Attachment #8634935 -
Flags: review?(bzbarsky)
Attachment #8634935 -
Flags: review+
Assignee | ||
Updated•9 years ago
|
Attachment #8634976 -
Flags: review?(docfaraday) → review+
Assignee | ||
Updated•9 years ago
|
Keywords: checkin-needed
Comment 13•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/382c04062988 https://hg.mozilla.org/integration/mozilla-inbound/rev/7d8c8896957f
Keywords: checkin-needed
Comment 14•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/382c04062988 https://hg.mozilla.org/mozilla-central/rev/7d8c8896957f
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox42:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
Assignee | ||
Updated•9 years ago
|
Summary: Need to support RTCAnswerOptions in CreateAnswer (pending standardization) → Need to not fail on seeing RTCAnswerOptions in CreateAnswer
You need to log in
before you can comment on or make changes to this bug.
Description
•