- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jun 2016 14:19:29 +0000
- To: public-media-capture-logs@w3.org
foolip has just created a new issue for https://github.com/w3c/mediacapture-main: == Restore the active/inactive events on MediaStream == They were removed in https://github.com/w3c/mediacapture-main/pull/291 This came up [on blink-dev](https://groups.google.com/a/chromium.org/d/msg/blink-dev/EHy8zm0eVy0/Jfg0vkVNAAAJ) and it appears as if 3 of 4 browser engines support these events, Gecko being the exception. Given that the `active` attribute itself is still present, the events don't seem to add much in terms of an implementation burden. IIUC, [the problem](https://lists.w3.org/Archives/Public/public-media-capture/2015Nov/0012.html) was about the timing of the attribute changing and the events firing. Assuming that the events are brought back, I see two options: * Always change state and fire the corresponding event in the same task. * Always queue a task to fire the event after the state change. This is what happens for HTML media elements, and it means that events can arrive when the state has already changed again. @adam-be @alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/370 using your GitHub account
Received on Wednesday, 22 June 2016 14:19:40 UTC