W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > July 2016

Re: [mediacapture-main] Restore the active/inactive events on MediaStream

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Mon, 04 Jul 2016 09:44:51 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-230250348-1467625490-sysbot+gh@w3.org>
Is the readonly `active` attribute also in the category of stream 
state that doesn't matter, or does it still make sense with 
track-based everything? If it does make sense, is there a simple 
replacement for the events?

function activeChanged() {}
stream.addEventListener('active', activeChanged);
stream.addEventListener('inactive', activeChanged);
function activeMayHaveChanged() {}
stream.getTracks().forEach(function(track) {
  track.addEventListener('ended', activeMayHaveChanged);
  // and mute/unmute events?
stream.addEventListener('addtrack', activeMayHaveChanged /* and figure
 out which track is new and add listeners */);
stream.addEventListener('removetrack', activeMayHaveChanged);
// replace addTrack and removeTrack on MediaStream.prototype since 
those don't fire events?
I'm just guessing here, I've never used these APIs and want to know 
what advise a deprecation should give if they're to be removed.

GitHub Notification of comment by foolip
Please view or discuss this issue at 
 using your GitHub account
Received on Monday, 4 July 2016 09:45:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:30 UTC