Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

step-06 make Firefox compatible #33

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

limhi
Copy link

@limhi limhi commented Jun 15, 2017

No description provided.

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If your company signed a CLA, they designated a Point of Contact who decides which employees are authorized to participate. You may need to contact the Point of Contact for your company and ask to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
  • In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.

@limhi
Copy link
Author

limhi commented Jun 16, 2017 via email

@googlebot
Copy link

CLAs look good, thanks!

@nitobuendia
Copy link
Contributor

@limhi Thanks a lot for the work and sorry for the delay in the response.

I was wondering if this is trying to fix a bug on the codelab. If yes, it would be nice to document it to know why these changes are made. There's currently 56 (not linking on purpose) which is exposing some x-browser issues, so perhaps it is related, but I wanted to verify with you what you were trying to fix.

Thank you!

@limhi
Copy link
Author

limhi commented Dec 12, 2017

@nitobuendia
There is definition of RTCIceCandidate on Mozilla website

https://developer.mozilla.org/zh-TW/docs/Web/API/RTCIceCandidate
if attributes named sdpMid & sdpMLineIndex not null, candidate is associated with sdp.

Thanks!

@nitobuendia
Copy link
Contributor

Thanks a lot for the clarifications, @limhi and sorry for the delay here. I am going to add my notes on the code itself :)

Copy link
Contributor

@nitobuendia nitobuendia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@limhi Thanks a lot for the PR and the waiting time.

I have tested this and it seems to work fine. I would make some small adjustments. Adding comments on the file below.

//cc @samdutton

@@ -160,8 +160,10 @@ function signalingMessageCallback(message) {

} else if (message.type === 'candidate') {
peerConn.addIceCandidate(new RTCIceCandidate({
sdpMLineIndex: message.label,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Order properties alphabetically.

  candidate: message.candidate,
  sdpMid: message.id,
  sdpMLineIndex: message.label,

candidate: message.candidate
}));
}));// Firefox compatible
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to add "Firefox compatible". We want to make it compatible with all browsers.

@@ -160,8 +160,10 @@ function signalingMessageCallback(message) {

} else if (message.type === 'candidate') {
peerConn.addIceCandidate(new RTCIceCandidate({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This same logic is present in step-05/js/main.js -- could you add the change there as well?

@nitobuendia
Copy link
Contributor

Hello @limhi ,

Thanks a lot again for your contribution. I sent a couple of comments to make this PR better. Let me know when you have some time to have a look.

Thanks a lot!

@nitobuendia
Copy link
Contributor

Hey @limhi -- Thanks again for your work. Did you have a chance to see the comments I sent on your PR?

@platy
Copy link

platy commented Sep 29, 2018

Hey I've just found this was why the example I was trying out was flaky, any chance of a merge?

I could implement @nitobuendia 's comments and make a new PR if that would help.

@nitobuendia
Copy link
Contributor

@platy It's been almost 6mo with no activity. I think that's a fair thing. Happy to review it, but it would need to be approved by @samdutton

@samdutton
Copy link
Contributor

Approved #92.

@nitobuendia — if you're happy with that, feel free to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants