desktopCapture extension: Multiple sharing of tabs/windows possible |
|||||
Issue descriptionVersion: Chrome M51 51.0.2704.2 OS: Linux 14.04, Windows 7 What steps will reproduce the problem? Precondition: Have multiple Chrome tabs and windows open (1) Download the desktopCapture extension from https://drive.google.com/a/google.com/folderview?id=0B__Tc1GKZkEXNEp3bWVxZ0hFaWs&usp=sharing_eid&ts=570ec782 (2) In chrome://extensions, click developer mode and click button 'Load Unpacked Extensions' (3) Launch the "Desktop Capture Example" extension (4) Click "Start" (5) Select "Entire screen" and Share (6) Verify that the Entire screen is indeed shared (7) Now, without clicking "Stop sharing" in the overlay dialog at the bottom of the page, click Start again in the desktop capture example dialog (8) Select a tab/window and Share (9) Verify that now you see 2 overlay text dialogs - one for entire screen and one for tab/window Screenshot attached What is the expected output? 1. At any given time, either entire screen/tab/window can be shared 2. Even if the user attempts to share multiple tabs (for instance), earlier sharing attempts should be canceled What do you see instead? multiple sharing of tabs/windows at the same time Please use labels and text to provide additional information.
,
Apr 13 2016
Have seen this in previous versions as well.
,
Apr 15 2016
> Have seen this in previous versions as well. gyzhou@ - do you think this is an issue with the desktopCapture extension, or is it an issue with the screenshare code in Chrome itself? In any case, I'm setting this to available since this doesn't sound like a regression in M51; or at least that's how I'm interpreting comment #2.
,
Apr 15 2016
This should be an issue of desktopcapture extension instead of chrome. The extension should release the stream when it doesn't need the stream anymore. I guess chrome.desktopCapture.cancelChooseDesktopMedia() should be for this purpose but it doesn't work.
,
Apr 15 2016
Updating summary and removing milestone label per #4. However, because this impacts testing, I'm increasing the priority from P3 to P2.
,
Apr 17 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 21 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by srnarayanan@chromium.org
, Apr 13 2016Labels: M-51