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

Issue 783224 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

1Password Android App is all black on external display on Kevin

Project Member Reported by diand...@chromium.org, Nov 9 2017

Issue description

When I try to run the 1Password Android app on kevin, it normally works fine.  ...unless I'm connected to an external display.  Then the app is all black when it's running on the external display and works fine when I drag it over to the internal display.

Other apps, like Hangouts for Android or Super Mario Run for Android, work fine on either display.

---

My kevin is currently on:
  10032.21.0 (Official Build) beta-channel kevin

 
That sounds like 1Paswsword Android app is marking its buffers as secure output only.
Visualizing those buffers as black on non secure displays is a feature.

Can you verify that taking a screenshot of that app on the embedded display also produces a black quad? If that's the case, this is working as intended.
@1: Yeah, I've confined that it's also a black box on a screenshot.

Even if this is working as intended, it still seems sub-optimal.  I could imagine 1Password wanting to avoid screen captures and the like, but it seems really non-ideal that it doesn't show up on my external monitor...  Is there some other mode that they should be using?
Owner: ddorwin@chromium.org
Status: Assigned (was: Untriaged)
I don't think we have anything better than that on ARC++ right now.

An external display without HDCP is as easy to capture as taking a screenshot. Why would they want to prevent it to show up in a screenshot and not on an external monitor?

The situation might improve once we get HDCP support.

I'd say this is working as intended.
We might want to talk with ddorwin@ regarding an alternative mode, since he originally drafted and then agreed with the current secure output design for ARC++.
Cc: jkardatzke@chromium.org
Yes, this is WAI per the Android APIs.
Status: WontFix (was: Assigned)

Sign in to add a comment