-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Spec for MSC3077 #1602
Spec for MSC3077 #1602
Conversation
@@ -171,18 +171,34 @@ In response to an incoming invite, a client may do one of several things: | |||
|
|||
##### Streams |
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.
can we add something to https://pr1602--matrix-spec-previews.netlify.app/client-server-api/#common-fields about the new field?
Clients implementing this specification will ignore any streamless tracks. Note | ||
that in the JavaScript WebRTC API, this means `addTrack()` must be passed two | ||
parameters: a track and a stream, not just a track, and in a video call the | ||
stream must be the same for both audio and video track. |
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.
I know this is existing text, but it now seems even more confusing than before, so I think we need to clarify.
- What is the mechanism by which streamless tracks are ignored? Or is this an instruction to clients to ignore such tracks?
- what is that to do with
addTrack
's parameters? - is it related to
sdp_stream_metadata
? if not, it should probably not be in the middle of the text about it?
closing in favour of #1735 |
Specs matrix-org/matrix-spec-proposals#3077
Preview: https://pr1602--matrix-spec-previews.netlify.app