W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2018

Weekly github digest (WebRTC WG specifications)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 02 Jan 2018 17:00:46 +0000
To: public-webrtc@w3.org
Message-Id: <E1eWPvj-0001Cf-06@uranus.w3.org>



Issues
------
* w3c/webrtc-pc (+2/-2/💬31)
  2 issues created:
  - example 14: render before verifying the remote fingerprint? (by fippo)
    https://github.com/w3c/webrtc-pc/issues/1709
  - Example 14 never sends any media (by stefhak)
    https://github.com/w3c/webrtc-pc/issues/1708

  15 issues received 31 new comments:
  - #1662 addTransceiver woes (11 by henbos, fippo, stefhak)
    https://github.com/w3c/webrtc-pc/issues/1662
  - #1691 When to fire events triggered by setRemoteDescription. (3 by henbos)
    https://github.com/w3c/webrtc-pc/issues/1691
  - #1708 Example 14 never sends any media (2 by alvestrand, stefhak)
    https://github.com/w3c/webrtc-pc/issues/1708
  - #1709 example 14: render before verifying the remote fingerprint? (2 by alvestrand)
    https://github.com/w3c/webrtc-pc/issues/1709
  - #1677 replaceTrack and removeTrack: Synchronous? (2 by henbos, stefhak)
    https://github.com/w3c/webrtc-pc/issues/1677
  - #1562 How to handle removing and re-adding remote streams/tracks - possible ID collisions? (2 by henbos, stefhak)
    https://github.com/w3c/webrtc-pc/issues/1562
  - #1697 replaceTrack: Never negotiate when replacing an ended track? (1 by stefhak)
    https://github.com/w3c/webrtc-pc/issues/1697
  - #1345 Make promise rejection/enqueing consistent (1 by stefhak)
    https://github.com/w3c/webrtc-pc/issues/1345
  - #1705 specify legacy onaddstream? (1 by fippo)
    https://github.com/w3c/webrtc-pc/issues/1705
  - #1706 Should rollback fire addtrack/removetrack events?  (1 by stefhak)
    https://github.com/w3c/webrtc-pc/issues/1706
  - #1707 onmute then onunmute can fire before negotiation completes (1 by alvestrand)
    https://github.com/w3c/webrtc-pc/issues/1707
  - #1499 Processing Remote MediaStreamTracks should pass on receiver when constructing track event (1 by stefhak)
    https://github.com/w3c/webrtc-pc/issues/1499
  - #1244 `parameters` not defined in `setParameters` algorithm (1 by stefhak)
    https://github.com/w3c/webrtc-pc/issues/1244
  - #1342 Consider using generic algorithm (1 by stefhak)
    https://github.com/w3c/webrtc-pc/issues/1342
  - #1279 Section 4.3.3: optional methods (1 by stefhak)
    https://github.com/w3c/webrtc-pc/issues/1279

  2 issues closed:
  - Section 4.3.3: optional methods https://github.com/w3c/webrtc-pc/issues/1279
  - `parameters` not defined in `setParameters` algorithm https://github.com/w3c/webrtc-pc/issues/1244




Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/webrtc-pc
* https://github.com/w3c/webrtc-stats
* https://github.com/w3c/webrtc-charter
Received on Tuesday, 2 January 2018 17:00:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 2 January 2018 17:00:48 UTC