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

Issue 794005 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 715426
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

[gFeedback Prestable] Unable to select elements on extensions on secondary monitor

Project Member Reported by jainabhi...@chromium.org, Dec 12 2017

Issue description

Chrome Version: M63
OS: Win 10

What steps will reproduce the problem?
(1) Launch Chrome on secondary monitor
(2) Click on an extension (tested with lastpass)
(3) Try to click a button

What is the expected result?
User should be able to hover and select relevant touch targets.

What happens instead?
Running extension on a multi monitor setup causes touch targets to behave incorrectly on the extension - touch targets for buttons/links/etc work fine on primary monitor, but not secondary monitor.

http://feedback/#/Report/76019274968

Video (contains PII) : https://drive.google.com/file/d/1fvl9vXEcABOVj99PTUA4BHtSYVA6RZ0c/view?usp=sharing - Restricted to Google.com
 

Comment 1 by gov...@chromium.org, Dec 12 2017

Cc: ranjitkan@chromium.org
Labels: M-63 Needs-Triage-M63
Another report : https://listnr.corp.google.com/report/84651267978

For Chrome add-ins like Last Pass, if you have a multi-monitor setup (Windows 10 in my case) and your main screen (ID #1) is set to scale up to 125% or 150% while the other screens are left at 100% scale, trying to select items on the Chrome add-in does not work properly as the highlighted option on the menu does not align with the mouse cursor.

Comment 3 by gov...@chromium.org, Dec 12 2017

Cc: brajkumar@chromium.org
Labels: M-61
I can reproduce this on M63 but we have reports about this issue since M61
Mergedinto: 715426
Status: Duplicate (was: Untriaged)
Able to reproduce this issue on Windows with chrome Stable #63.0.3239.84, Beta #63.0.3239.84 but not on Dev #64.0.3282.24 

This looks similar to  Issue 715426 , hence merging into it.


Sign in to add a comment