-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
webrtc: Test legacy offerToReceiveAudio/Video options #8450
webrtc: Test legacy offerToReceiveAudio/Video options #8450
Conversation
Build PASSEDStarted: 2017-12-15 09:24:52 View more information about this build on: |
I think this won't pass on Chrome (no transceivers), but does it "work" at least to the point where the test is parsed and calls the functions that it should? |
@alvestrand ref to no transceivers? Or is this wpt related? Would like to get versed. |
It won't pass on Chrome (nor Firefox), but from what I see that's the case for all transceiver related tests. @snuggs, transceivers are part of the spec, but not yet widely implemented. |
Copy that @adam-be! That's all I needed to know to start digging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall well done. Others may want to chime in on this but I encourage a help
link to the appropriate spec. This allows contributors who may not be explicitly versed in the particular area of the spec.
This removes the need for questions like following to be answered after PR is merged. #8450 (comment)
My 2 Satoshi.
@@ -0,0 +1,85 @@ | |||
<!doctype html> | |||
<meta charset=utf-8> | |||
<title>Test legacy offerToReceiveAudio/Video options</title> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alvestrand what are our conventions for adding author & help meta tags? I have noticed this convention sprinkled throughout the wpt repo (primarily within css subset). I actually wish there were more references especially to the respective spec.
Examples
- Spec
help
example: https://github.com/w3c/web-platform-tests/blob/56ea52b8668ceee63ec196c59dd11ad7797e4f0d/html/semantics/embedded-content/the-video-element/video_initially_paused-ref.html#L5 author
example: https://github.com/w3c/web-platform-tests/blob/95eb7be62d2b5a3e9ef1165fd333d353fe3d4b30/html/rendering/bindings/the-button-element/button-type-menu-historical.html#L4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No idea about the convention for meta tags, I've not used them; this should have recommendations at the WPT project level - @foolip may want to comment, but that shouldn't block this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that shouldn't block this PR @alvestrand
Agreed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can add it if you find it useful. Myself, I never add author info because it's in git history, and add spec links only if the path and filename doesn't have all the info you need, which is often the case.
Thanks for reviewing. I've added a help link. I guess with our new "test as you commit" approach there will be situations where a test can't be linked to a section in a publicly available spec since the only place the correct section exists, is in pending PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. I think this tests the existing spec, so should be submitted without waiting for anything. In my opinion, tests that test changes not committed to the spec should be committed when the change to the spec is committed - there may be more opinions on that.
@@ -0,0 +1,85 @@ | |||
<!doctype html> | |||
<meta charset=utf-8> | |||
<title>Test legacy offerToReceiveAudio/Video options</title> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No idea about the convention for meta tags, I've not used them; this should have recommendations at the WPT project level - @foolip may want to comment, but that shouldn't block this PR.
Sounds reasonable to me. |
@jan-ivar, that was my mistake. I've updated the test now and it's all green in Firefox nightly. :) |
@snuggs, do you believe that your comments above have been addressed? |
}, `offerToReceive${capsType} option should be ignored if a non-stopped "sendrecv" transceiver exists`); | ||
}); | ||
|
||
promise_test(t => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whitespace nit: indent 2 spaces?
can fix when adding tests for w3c/webrtc-pc#1693
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
return getTrackFromUserMedia(type) | ||
.then(([track, stream]) => { | ||
pc.addTrack(track, stream); | ||
pc.createOffer(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing return?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True; will fix.
@snuggs your review is blocking this merge, and was (I think) addressed ~20 days ago. Can you unblock? |
No description provided.