New issue
Advanced search Search tips

Issue 628671 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

WebRTC should not close source when external monitor mirroring primary screen is unplugged

Reported by jboer...@clearslide.com, Jul 15 2016

Issue description

Chrome Version       : 51.0.2704.103
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: untested
    Firefox: FAIL (but in a different way)
         IE: untested

What steps will reproduce the problem?
(1) Attach an external monitor (like a physical screen) and have the additional monitor mirror the primary screen (as opposed to extending the desktop)
(2) Start some sort of webrtc screenshare, and share the screen
(3) Unplug the external monitor

What is the expected result?
I would expect the webrtc source to be the same and to be able to continue sharing

What happens instead?
The media stream source is closed, and I need to create a new one (including having the user select a source again)

Please provide any additional information below. Attach a screenshot if
possible.

 
Components: Blink>WebRTC
Cc: sprang@chromium.org
Labels: Needs-Feedback
That sounds like by design or a limitation of the underlying screen capture OS API's to me. sprang@ WDYT?
sprang: ping!

Comment 4 by sprang@chromium.org, Aug 17 2016

Cc: niklase@chromium.org
Not sure what the right thing here is.
+niklase, any opinion from a capturer standpoint?
Cc: qiangchen@chromium.org
Status: Available (was: Unconfirmed)
I agree this is not the desired behavior, but it could be hard to fix if the OS tears down the whole capture sessions. We would need to take a closer look and see what happens. P3 seems right.
Components: -Blink>WebRTC Blink>GetUserMedia>Desktop
Labels: -Needs-Feedback
Project Member

Comment 7 by sheriffbot@chromium.org, Sep 11 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)

Sign in to add a comment