W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2019

Re: [mediacapture-main] Clarification needed on HTMLMediaElement attributes that carry over (#599)

From: Andreas Pehrson via GitHub <sysbot+gh@w3.org>
Date: Fri, 31 May 2019 08:58:58 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-497633832-1559293137-sysbot+gh@w3.org>
I've updated your test fiddle to https://jsfiddle.net/pehrsons/pk8mo36d/

The async waiting for gUM also let one "ratechange" slip through that would otherwise have been cancelled (per [my 2nd comment](https://github.com/w3c/mediacapture-main/issues/599#issuecomment-496561453)).

```
    let stream = await navigator.mediaDevices.getUserMedia({video: true});
    video.onratechange = () => console.log("ratechange");
    video.defaultPlaybackRate = 0.5;
    video.playbackRate = 0.5;
    console.log(video.playbackRate);
    video.srcObject = stream;
    console.log(video.playbackRate);
    video.defaultPlaybackRate = 0.7;
    video.playbackRate = 0.7;
    console.log(video.playbackRate);
    video.srcObject = null;
    console.log(video.playbackRate);
    for (let t of stream.getTracks()) {
      t.stop();
    }
```

Firefox:
```
0.5
0.5
0.7
0.7
```

Chrome:
```
0.5
1
1
0.5
```

Safari:
```
0.5
0.5
0.7
0.7
```

Unfortunately I'm not able to test Edge.

It seems to me that only chrome attempted to implement this part of the spec, and their implementation seems to agree with what [jib outlined above](https://github.com/w3c/mediacapture-main/issues/599#issuecomment-496562096).

-- 
GitHub Notification of comment by Pehrsons
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/599#issuecomment-497633832 using your GitHub account
Received on Friday, 31 May 2019 08:59:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:23 UTC