- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Apr 2017 22:43:38 +0000
- To: public-webrtc-logs@w3.org
@taylor-b Did something get lost in refactoring in https://github.com/w3c/webrtc-pc/pull/1016 ? That PR is titled "Ensure that "track" event is only fired for "send" direction m-sections." which sounds like a spec change to me. [Before](https://rawgit.com/w3c/webrtc-pc/c77e984fe0fb94b76f79f51fc1761d845b63592c/webrtc.html#set-description), 2.2.7. said: *"If description is set as a remote description with new media descriptions [JSEP] (section 5.7.2.), the User Agent MUST dispatch a receiver for all new media descriptions."* - where *dispatch a receiver* would always fire a track event. This is why [the following](https://jsfiddle.net/jib1/qx3esnb3/) works in both Firefox and Chrome today. [After](https://rawgit.com/taylor-b/webrtc-pc/78d828dd972b22aaf0905eaaf3618767b3b3cf5c/webrtc.html#set-description) the refactor, the spec no longer seems to fire the track event in this case. Was that intentional? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1128#issuecomment-294617162 using your GitHub account
Received on Monday, 17 April 2017 22:43:45 UTC