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

Issue 804763 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

android apps on secondary display do not register clicks on some parts

Project Member Reported by uekawa@google.com, Jan 23 2018

Issue description

Chrome Version: 64.0.3282.101 beta
OS: CrOS

What steps will reproduce the problem?
(1) have more than 2 displays connected and in docked mode.
(2) open termux, or google play music app 
(3) try to drag the window to reposition on the secondary external display

What is the expected result?

I can drag the window

What happens instead?

click is registered behind the window.

(seems like hangouts app works, but play music app and termux app fails)

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

84961910211
 

Comment 1 by uekawa@google.com, Jan 23 2018

Components: Platform>ARC
What ARC version? Multi-display mode was broken in M64 before 4557572, which was built 2 days ago.

Comment 3 by uekawa@google.com, Jan 24 2018

Labels: -Pri-3 M-64 ReleaseBlock-Stable Pri-1

	10176.54.0	64.0.3282.101	4548206 -- this is the current live beta
	10176.58.1	64.0.3282.110	4555316 -- this is the next beta which is stable candidate.


Comment 4 Deleted

Comment 5 by uekawa@google.com, Jan 25 2018

I believe today's M64 binary is the first version with Dom's changes in

	2018-01-24 09:20	10176.60.0	64.0.3282.117	4561070 

I haven't tested it.

Comment 6 by uekawa@google.com, Jan 25 2018

Cc: elijahtaylor@chromium.org kbleicher@chromium.org
Can we verify per #5, triage, assign ownership, remove the block....
Owner: uekawa@chromium.org
Status: Assigned (was: Untriaged)
Junichi, please test on the new build and re-assign or close if not reproducible

Comment 9 by uekawa@google.com, Jan 30 2018

so far on 64.0.3282.122 things look good.


Cool; can we remove the stable block if confirmed in the later 64?
Labels: -ReleaseBlock-Stable
Status: Fixed (was: Assigned)
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-64; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-64 label, otherwise remove Merge-TBD label. Thanks.
Labels: -Merge-TBD
removing merge label because this was handled elsewhere

Sign in to add a comment