- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Sep 2019 23:52:38 +0000
- To: public-webrtc-logs@w3.org
Does this only affect `MediaStreamTrack` from `getUserMedia()`? Chromium does provide `resizeMode` constraint when the track is derived from `HTMLVideoElement.captureStream()` though AFAICT no value that is set has any impact on the resulting video track. Further, Chromium provides `getSettings()` for tracks derived from `HTMLVideoElement.captureStream()` which ultimately outputs incorrect results for `width` and `height` when the underlying file is a WebM file having variable resolution frames output by `MediaRecorder` then replayed at HTML `<video>` element at Chromium, only the initial `width` and `height` are output. For example, given a 2 second WebM video where the first 1 second is 400x300 and the second second is 300x150 `getSettings()` `width` and `height` output `400`, `300` for the duration of the video. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/584#issuecomment-531424377 using your GitHub account
Received on Friday, 13 September 2019 23:52:40 UTC