Extension action-view click coordinates incorrect on second monitor
Reported by
nameless...@gmail.com,
Dec 18 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Use Windows 10 Chrome 2. Use two monitors set to two different resolutions 3. Open the action view and try clicking things. Only on the main monitor will the clicks register on the thing you are pointing at. What is the expected behavior? When clicking, the click should register on the element you are pointing at. What went wrong? It seems that the extension action view uses some kind of coordinate system derived from the primary monitor, which is not necessarily the monitor being used to display itself. WebStore page: https://chrome.google.com/webstore/detail/metamask/nkbihfbeogaeaoehlefnkodbefgpgknn?authuser=2 Did this work before? No Chrome version: 63.0.3239.84 Channel: n/a OS Version: 10 Flash Version: We are tracking this at MetaMask here: https://github.com/MetaMask/metamask-extension/issues/2767#issuecomment-352589879
,
Jan 3 2018
Unable to reproduce the issue on Win-10 dual monitor using chrome stable version #63.0.3239.108 and latest canary #65.0.3309.0. Following are the steps followed to reproduce the issue. ------------ 1. Used Windows 10 Chrome 2. Used two monitors set to two different resolutions: primary was set to 1280x768 and secondary was set to 1280x960. 3. Added the extension at https://chrome.google.com/webstore/detail/metamask/nkbihfbeogaeaoehlefnkodbefgpgknn?authuser=2 and tried clicking the extension both on primary and secondary display. 4. Observed that click registered on the element for both the displays. namelessdan@ - Could you please check the issue on latest stable #63.0.3239.108 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Jan 9 2018
We have a user who insists this is still an issue, I don't have a dev setup that could reproduce: https://github.com/MetaMask/metamask-extension/issues/2767#issuecomment-355762918
,
Jan 9 2018
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 12 2018
I am able to reproduce this on Version 63.0.3239.132 (Official Build) (64-bit) - Windows 10 with uBlock Origin. Disabling chrome://flags/#enable-use-zoom-for-dsf "Use Blink's zoom for device scale factor." resolves the issue for me.
,
Jan 19 2018
As per comment#3 and #5 checked the issue on reported version 63.0.3239.84 and on latest stable by adding both extensions metamask and uBlock Origin and by making enable-use-zoom-for-dsf flag both in default and enabled state. Attaching screencast for reference. @Reporter: Could you please check the video and let us know if we miss anything. This would help in triaging the issue further.
,
Jan 26 2018
Hi sc00335, thanks for the video. The problem is not the resolution, but the scaling. I see the scaling is set to 100% for you. If you want to see the problem, you have to set the scaling to something other than 100%. Try setting it to 125%. Then move metamask to your secondary monitor or "other" monitor and if you try to hover over the "Accept" button, or any button you will notice that its not clickable because mouse position is off due to scaling.
,
Feb 9 2018
Hi were you able to reproduce the issue?
,
Nov 23
As there isn't any Feedback from reporter from long time, closing this issue and marking it as Won't Fix. @Reporter: Requesting you to file/raise a new one if the issue is seen again. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Dec 19 2017