Issue metadata
Sign in to add a comment
|
extension background muted videos no longer working
Reported by
m...@proctorio.com,
May 30 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Linux; Android 8.0.0; SM-N950U Build/R16NW) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.158 Mobile Safari/537.36 Steps to reproduce the problem: 1. Use desktop capture api 2. Set stream to video source, video dom is muted. 3. Desktop capture only captures black 4. Remove muted and it works What is the expected behavior? What went wrong? New auto play policy requiring a gesture shouldn't impact extension background elements. Did this work before? Yes 66 Chrome version: 67 Channel: stable OS Version: Flash Version:
,
May 31 2018
,
May 31 2018
Unable to reproduce the issue on reported chrome version 67.0.3396.62 and latest chrome 69.0.3445.2 using Windows 10. Attaching Screencast for reference. Steps -------- 1. Launched Chrome. 2. Enabled screencsatify extension and disabled microphone. 3. Navigated to some video and Muted video also system volume. 4. Recorded video though screencastify. Observed that the video rendering is not black and it rendered normally. @Reporter: As we are unable to reproduce the issue from our end. Could you please review the attached screen-cast and confirm if anything being missed here and if possible could you please provide screencast for better triaging this issue. Thanks!
,
Jun 17 2018
our implementation looked like this
background.js
navigator.webkitGetUserMedia({
audio: {
mandatory: {
chromeMediaSource: 'system'
}
},
video: {
mandatory: {
chromeMediaSource: 'desktop',
chromeMediaSourceId: ACCESS_CODE
}
}
}, function (stream)
{
// always check the stream
if (stream)
{
// get the html5 video dom element
desktopvideo_dom = document.getElementById('screenvideo');
// set this to muted so we dont double play audio
desktopvideo_dom.muted = true;
// generate the url stream
desktopvideo_dom.src = window.URL.createObjectURL(stream);
}
when desktopvideo_dom.muted = true; was commented out it worked just fine with the new update
,
Jun 17 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 18 2018
@Reporter: As per your comment #4 (was commented out it worked just fine with the new update) could you please confirm can we close this issue? Thanks.!
,
Nov 29
As there is no update from the reporter since a long time, marking this issue as WontFix. Please feel free to raise a new bug if any issues are observed on the latest Chrome builds. Thanks... |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by cbiesin...@chromium.org
, May 30 2018