New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 914890 link

Starred by 1 user
Status: Assigned
Owner:
█ djmk@chromium.org
Last visit > 30 days ago
Cc:
█ marc...@chromium.org
ricardoq@chromium.org
nya@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

screenshot command does not capture HW overlayed windows

Project Member Reported by ricardoq@chromium.org, Dec 13 
Steps to reproduce it:

1) Open at least one ARC++ window
2) DUT# screenshot --internal image.png

And image will have a black screen where the ARC++ window is supposed to be.

See screenshot.
hw_overlay_screenshot.png
1.0 MB View Download

Comment 1 by ricardoq@chromium.org, Dec 13

Labels: -Pri-3 Pri-2

Comment 2 by ricardoq@chromium.org, Dec 13

Cc: ricardoq@chromium.org

Comment 3 by ricardoq@chromium.org, Jan 2

Cc: nya@chromium.org

Comment 4 by ricardoq@chromium.org, Jan 8 

screenshot.CaptureChrome() seems to be working Ok, but screenshot.Capture() has the bug.
lowering the priority since CaptureChrome() satisfies my needs.

Comment 5 by ricardoq@chromium.org, Jan 8

Labels: -Pri-2 Pri-3

Comment 6 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment