Issue 682226 link

Starred by 6 users

Issue metadata

Status:	Available
Owner:	----
Cc:	█ ghb@google.com █ tmarek@google.com mfo...@chromium.org powerb@chromium.org
Components:	Internals>Media>ScreenCapture
EstimatedDays:	----
NextAction:	----
OS:	----
Pri:	3
Type:	Bug

cast/tabCapture doesn't include comboboxes

Project Member Reported by joaodasilva@chromium.org, Jan 18 2017

Issue description

Chrome Version: 57.0.2979.0
OS: Linux

What steps will reproduce the problem?
(1) cast a page with a <select> combobox
(2) click the combobox

What is the expected result?
- To see the dropdown from the combobox in the cast stream.

What happens instead?
- The dropdown window from the combobox isn't shown.

I've reproduced this via 3 different APIs:

1. using Hangouts and sharing my browser window. <select> boxes aren't visible by other participants.

2. using the debug API for casting (https://chromedevtools.github.io/debugger-protocol-viewer/tot/Page/#method-startScreencast)

3. using captureVisibleTab() via the tabs extension API: (https://developer.chrome.com/extensions/tabs#method-captureVisibleTab). Screenshots taken while a combobox is open don't include its contents.

(2) is used by the webtools and causes this bug when doing remote debugging too. I suspect that the tabCapture API has the same bug (https://developer.chrome.com/extensions/tabCapture)

Comment 1 by yini...@chromium.org, Jan 18 2017

Components: -Internals>Media>Capture

Comment 2 by m...@chromium.org, Jan 18 2017

Components: -Platform>DevTools -Internals>Cast Blink>GetUserMedia>Tab

Due to Chrome's architecture, it would require a lot of work to implement this. Basically, all pop-ups are separate windows on top of the browser window; and not actually rendered by the web engine. Also, there are weird edge cases to consider: e.g., what should tab capture do if part of the combo box "spills" outside of the browser window's bounds?

Expectations: Unfortunately, it's unlikely my team will ever be able to prioritize this to the point where someone will start work on it. So, this bug will just sit around until an outside developer feels strongly-enough about it to implement it.