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

[mediacapture-main] Stop a remote track has no effect

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Fri, 12 Feb 2016 11:20:51 +0000
To: public-media-capture@w3.org
Message-ID: <issues.opened-133215445-1455276050-sysbot+gh@w3.org>
alvestrand has just created a new issue for 
https://github.com/w3c/mediacapture-main:

== Stop a remote track has no effect ==
The current description of track's stop:

When a MediaStreamTrack object's stop() method is invoked, the User 
Agent must run following steps:
- Let track be the current MediaStreamTrack object.
- If track is sourced by a non-local source, then abort these steps.
- Notify track's source that track is ended so that the source may be 
stopped, unless other MediaStreamTrack objects depend on it.
- Set track's readyState attribute to ended.

This seems wrong to me. Stopping a track should cause the track to 
stop, no matter where it comes from. If it's a non-local source, its 
handler may choose to ignore the notification or not; this spec does 
not have to say.

Suggested fix:

- Delete step 2
- Modify step 3 to be "Notify track's source that track is ended."
- Add a sentence under the description that says "For local sources 
that are notified of a track ending, the source will be stopped if no 
other MediaStreamTrack objects depend on it," 




Please view or discuss this issue at 
https://github.com/w3c/mediacapture-main/issues/314 using your GitHub 
account
Received on Friday, 12 February 2016 11:20:53 UTC

This archive was generated by hypermail 2.3.1 : Friday, 12 February 2016 11:20:54 UTC