Issue metadata
Sign in to add a comment
|
Single clicks dont work, need to click multiple times to get it to "take"
Reported by
b...@portraitsreno.com,
Sep 28 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: Trying to use Chrome at all What is the expected behavior? Expect clicking on something to work What went wrong? Have to click 2, 3 sometimes 6 or 7 times on any link to get it to work... on any page... I have two macs on High Sierra, and it's ONLY limited to the High Sierra OS, all others work as expected. Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.13.0 Flash Version: Shockwave Flash 27.0 r0 Hoping for a fix soon, this really makes Chrome unusable
,
Sep 28 2017
,
Sep 28 2017
,
Sep 28 2017
Here is my screencast from CodePen. I have been having the same issue the past two days. I am having to click elements sometimes 3-4 times before it executes an action.
,
Sep 29 2017
From the video it appears as though multiple clicks are being sent by the OS. Can you screencast the result of clicking in https://jsfiddle.net/tapted/kpu6wzh4/ ? Can you try in Safari as well? Are you using a physical mouse or touchpad? I couldn't repro this on High Sierra 10.13.1 (17B25c) with Chrome 61.0.3163.100 or 63.0.3226.0. This could be a High Sierra regression for your mouse driver.
,
Sep 29 2017
Actually, this sounds like Issue 763642 do you have Magnet or BetterTouchTool installed?
,
Sep 29 2017
I do have magnet installed. It worked fine in Sierra. I'll disable it and see if it continues. I'll report back.
,
Oct 2 2017
I have confirmed that everything works fine without Magnet. Is this on the Magnet developers to fix or is this a Chrome issue? The added functionality with Magnet is extremely helpful because I am running 4 external displays from my MBP.
,
Oct 2 2017
,
Oct 2 2017
The problem is the API that these apps use causes the event stream from OSX to be inconsistent which is causing the issues. We might be able to add a work around in Chrome but ultimately this is an OSX issue with the API. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by meh...@chromium.org
, Sep 28 2017