New issue
Advanced search Search tips
Starred by 86 users

Issue metadata

Status: Verified
Closed: Sep 13

issue 2571

Sign in to add a comment

Issue 2144: Test testClickElement from MobileEmulationCapabilityTest class fails on Chromium for all platforms

Reported by, Nov 20 2017 Project Member

Issue description

Test testClickElement from MobileEmulationCapabilityTest class fails on Chromium for all platforms,
Test fails with the following error message:

ERROR: testClickElement (__main__.MobileEmulationCapabilityTest)
Traceback (most recent call last):
  File "E:\b\build\slave\chromedriver_win7\build\src\chrome\test\chromedriver\test\", line 2139, in testClickElement
  File "E:\b\build\slave\chromedriver_win7\build\src\chrome\test\chromedriver\test\..\client\", line 38, in Click
  File "E:\b\build\slave\chromedriver_win7\build\src\chrome\test\chromedriver\test\..\client\", line 18, in _Execute
    return self._chromedriver.ExecuteCommand(command, params)
  File "E:\b\build\slave\chromedriver_win7\build\src\chrome\test\chromedriver\test\..\client\", line 291, in ExecuteCommand
    response = self._ExecuteCommand(command, params)
  File "E:\b\build\slave\chromedriver_win7\build\src\chrome\test\chromedriver\test\..\client\", line 281, in _ExecuteCommand
    response = self._executor.Execute(command, params)
  File "E:\b\build\slave\chromedriver_win7\build\src\chrome\test\chromedriver\test\..\client\", line 193, in Execute
    response = self._http_client.getresponse()
  File "E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib\", line 1045, in getresponse
  File "E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib\", line 409, in begin
    version, status, reason = self._read_status()
  File "E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib\", line 365, in _read_status
    line = self.fp.readline(_MAXLINE + 1)
  File "E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib\", line 476, in readline
    data = self._sock.recv(self._rbufsize)
timeout: timed out

Comment 1 by, Nov 20 2017

Description: Show this description

Comment 2 by, Nov 20 2017

Project Member
Status: Assigned (was: Available)
Hi Joel,

A ChromeDriver test case has been broken by your change After this change, when mobile emulation and touch emulation are turned on, ChromeDriver isn't receiving response to some of its Input.dispatchMouseEvent command. Please see the attached log files. 493595.log used Chrome without your change, and the test worked correctly. 493596.log used Chrome with your change, and the test was hang. The logs showed that after an Input.dispatchMouseEvent command of type mousePressed, the older Chrome sends a response quickly, while the newer Chrome never sends a response back.

Could you please take a look? To repro this issue, please first build with "ninja -C out/Default chrome chromedriver", and then run the following test:

chrome/test/chromedriver/test/ --chromedriver=out/Default/chromedriver --filter=__main__.MobileEmulationCapabilityTest.testClickElement

25.1 KB View Download
25.3 KB View Download

Comment 3 by, Nov 21 2017

Project Member
The following revision refers to this bug:

commit 283a2848221d80b4ef41e400459c739169d34b9d
Author: Artur Khachatryan <>
Date: Tue Nov 21 02:02:56 2017

[ChromeDriver] test MobileEmulationCapabilityTest.testClickElement is disabled

Test testClickElement from MobileEmulationCapabilityTest class fails on Chromium for all platforms.

Bug:  chromedriver:2144 
Change-Id: Ia2da75d51208693c43e528b3650af2523afe6bf3
Reviewed-by: John Chen <>
Commit-Queue: Artur Khachatryan <>
Cr-Commit-Position: refs/heads/master@{#518056}

Comment 4 by, Dec 5 2017

Status: Started (was: Assigned)

Comment 5 by, Dec 6 2017

There is sort of a fundamental issue with how we have been handling touch event acks. Touch events can cause mouse events to be generated, but we haven't been waiting for those events to be fired into the page. Due to a combination of race conditions that have been fixed, this test started failing. I am working on a fix, but it doesn't look like it is going to be easy.

Comment 6 by, Dec 6 2017

Project Member
Thanks for looking into this. If there are any changes we can make in ChromeDriver to make the fix easier, please let us know.

Comment 8 by, Dec 18 2017

I ran into this Issue while looking for some info about similar problem - I think it relates: 
We are working with chrome emulator for automation for sometime now.
Once Chrome got automatically updated to v62 (and above), simple click stopped working - we use selenium so we got a timeout.
we tried different versions of chromedriver as 2.33 and 2.34 but nothing helps but downgrade chrome to v61.

This workaround won't hold for long time of course.
Hope it relates and this issue will be solved soon.


Comment 9 by, Dec 19 2017

Project Member
 Issue 2187  has been merged into this issue.

Comment 10 by, Dec 22 2017

73 bytes Download

Comment 11 by, Jan 4 2018

 Issue 2145  has been merged into this issue.

Comment 12 by, Jan 9 2018

Project Member
einbinder@: Do you have any update on this bug? Thanks.

Comment 13 by, Jan 9 2018

Project Member
The following revision refers to this bug:

commit c606e09fbd39ab08befe00b5f14f0ba0fe2bf878
Author: John Chen <>
Date: Tue Jan 09 19:38:27 2018

[ChromeDriver] Temporarily disable touch emulation

Bug  is causing ChromeDriver and
Chrome to stop responding under some scenarios. Temporarily disabling
touch emulation feature until this bug can be resolve.

Bug:  chromedriver:2144 
Change-Id: I216235aa909aafa5cb44e7519c89056e2caee29d
Reviewed-by: Caleb Rouleau <>
Commit-Queue: John Chen <>
Cr-Commit-Position: refs/heads/master@{#528070}

Comment 14 by, Jan 11 2018

 Issue 2219  has been merged into this issue.

Comment 15 by, Jan 11 2018

Hi, Can we please get a faster resolution/update regarding this as this is blocking entire automation

Comment 16 by, Jan 11 2018

Waiting on the fix as well. Would love to see this get resolved soon. Thanks.

Comment 17 by, Jan 23 2018

Any updates here ?

Comment 18 by, Mar 9 2018

Reported by, Nov 20
almost 4 months passed w/o resolution and disabled test is still disabled and touch still doesnt work :(

Comment 19 by, Mar 9 2018

dimundo.., could you please try with Chrome 65 and Chromedriver 2.36?

Comment 20 Deleted

Comment 21 by, Mar 9 2018

Still same - not fixed
win 10 + chromedriver 2.36.540470 + chrome 65.0.3325.146

last working combo - 2.33.506120 + 61.0.3163.79

Comment 22 by, Mar 9 2018

As for  issue 2306 , everything worked until we used ChromeDriver 2.33.506120 and Chrome 61.0.3163.79. Since then, it goes down the hill.

Comment 23 by, Mar 22 2018

Any progress? 

Currently we cannot upgrade chrome above 61 and chromedriver above 2.33.

Actually it is not possible to combine the runs/work between emulator and actual devices because of this bug with emulator (we prefer the emulator due to speed).

Comment 24 by, Mar 30 2018

Preciso de emprego
Em 22/03/2018 4:57 AM, "climbing… via monorail" <> escreveu:

Comment 25 by, Mar 30 2018

einbinder@: Do you have an update ?

Comment 26 by, Mar 31 2018

1.4 MB View Download

Comment 27 by, Mar 31 2018

Capacidade de plataforma

Em 31/03/2018 1:24 AM, "yohe… via monorail" <> escreveu:

Comment 28 Deleted

Comment 29 by, Apr 2 2018

 Issue 2365  has been merged into this issue.

Comment 30 by, Apr 19 2018

new chrome 65.0.3325.181 and new ChromeDriver 2.38.551601 are released -touch still not working (obviously, as this issue is not fixed)
Any plans on this ?

Comment 31 by, Apr 24 2018

and same fail for 2.38.551601 + 66.0.3359.117 :(

Comment 32 by, Apr 26 2018

any updates? quite annoying issue

Comment 33 by, Apr 26 2018

Labels: Needs-Feedback, do you have an update on this issue?

Comment 34 by, May 10 2018

Any updates on this issue? We also need this fix very much

Comment 35 by, May 10 2018

Guys, the whole page is obsolete due to the issue:

Touches don't work.
Is there some progress?

Comment 36 by, May 22 2018

 Issue 2322  has been merged into this issue.

Comment 37 by, May 30 2018

2.39.562718 + 67.0.3396.62 still bad
Any hope on fixing this?

Comment 38 by, Jun 12 2018

Project Member
 Issue 2459  has been merged into this issue.

Comment 39 by, Jun 12 2018

For context, I started working on this at

I am trying to find a way to fix it that won't be horribly flaky.

Comment 40 by, Jun 12 2018

Thank you Joel for working on it. It is much appreciated.

Comment 41 by, Jun 12 2018

 Issue 2450  has been merged into this issue.

Comment 42 by, Jun 15 2018

 Issue 2467  has been merged into this issue.

Comment 43 by, Jun 20 2018

 Issue 2478  has been merged into this issue.

Comment 44 by, Jul 5 2018

Any updates on the click issue? Thanks!

Comment 45 by, Jul 5 2018

plus 1 to Adrian question. Thank you!

Comment 46 by, Jul 6 2018

This basically killed our mobile automation. We don't want to implement workarounds if the fix will be available soon, is anyone working on fix?


Comment 47 Deleted

Comment 48 Deleted

Comment 49 by, Jul 12 2018

Might help: in my scenario when mobile emulation is on WRONG element receives click. I.e. seleniums's findElement returns correct element but when I call 'Click' on it other element receives it. Clicks happens but on wrong element.

Comment 50 by, Jul 13 2018

Hi guys,

This issue is getting me crazy as well, I am only having problems with this while using Windows 10 and Windows Server Virtual Machines, the issue is not present while using Windows 10 physical machine or Windows 7 physical or Virtual Machines.

As comment49 said, I have noticed click is done in different coordinates that the element is currently in, not sure why as Selenium is retrieving the correct element coordinates, I am able to click using Javascript click and also Javascript click on coordinates but Selenium click is not working.

The issue is only present on mobile emulation, responsive with screen size set is working fine while using not emulation.

Resume from my side is I am only having this issue while using Windows 10 kind  Virtual Machine (Windows 10 or Windows Server 2016).

Best regards,

Comment 51 by, Jul 13 2018

Use JavascriptExecutor to click on the element:

WebElement element = driver.findElement("test123"));
JavascriptExecutor executor = (JavascriptExecutor)driver;
executor.executeScript("arguments[0].click();", element);

Comment 52 by, Jul 13 2018

just to remind - this ticked ( opened in november) initially was about broken TOUCH not click. Not sure if it is ok to mix different issues into this one

Comment 53 by, Jul 13 2018


Comment 54 by, Jul 18 2018

any ideas how to workaround this , anyone ?

Comment 55 by, Jul 18 2018

Currently just setting window size through normal browser settings and user agent in the mobile emulation settings, although this doesn't simulate touchevents which is where the issue is and doesn't set the window scale this is probably the best option for testing responsive design in the meantime.

Comment 56 by, Jul 30 2018

Any updates on the click issue?  I still having this problem on mobile emulation. Thanks!

Comment 57 by, Jul 30 2018

We are also not sure what to do. Our pipeline is stuck on an old version of Chromium from last October!

The the issue then was marked fixed:
And the follow up issue for chrome was also marked fixed:

But the issue is still the same. We can't (or don't know how to) emulate touch events via selenium.

Comment 58 by, Aug 10

Hi guys,

This issue is very frustrating, I am only having this problems with the MAC OS.
with chrome version 67 and 68 only. Same thing is working fine on windows and ubuntu.

Comment 59 Deleted

Comment 60 by, Aug 21

Project Member
The following revision refers to this bug:

commit e4e4440f89bd318d228713278a9486a184680972
Author: Joel Einbinder <>
Date: Tue Aug 21 22:05:44 2018

ChromeDriver: Convert mouse events into touch events

This patch uses Input.dispatchTouchEvent instead of
Emulation.setEmitTouchEventsForMouse. This gives more predictable
behavior and allows for each touch event to be awaited.

Bug:  chromedriver:2144 
Change-Id: Ic243c216e2f832844a64f8f2af894eb6cc4234d1
Commit-Queue: Joel Einbinder <>
Reviewed-by: John Chen <>
Reviewed-by: Dmitry Gozman <>
Cr-Commit-Position: refs/heads/master@{#584904}

Comment 61 Deleted

Comment 62 Deleted

Comment 63 by, Sep 4

Blocking: 2571

Comment 64 by, Sep 13

Project Member
Labels: -Needs-Feedback ToBeReleased ChromeDriver-2.42
Status: Fixed (was: Started)

Comment 65 by, Sep 14

Project Member
Labels: -ToBeReleased

Comment 66 by, Sep 21

It still doesn't work with Chromedriver 2.42 and Chrome Version 69.0.3497.92 (Official Build) (64-bit) - Mac OSX

Comment 67 by, Sep 21

Project Member
Artur, can you please check to see whether or not this is truly fixed?

Comment 68 by, Sep 21

confirming - win + ubuntu fixed, but macOs still fails

chromedriver versions
win 2.42.591088 (7b2b2dca23cca0862f674758c9a3933e685c27d5)
mac 2.42.591059 (a3d9684d10d61aa0c45f6723b327283be1ebaad8)
linux 2.42.591071 (0b695ff80972cc1a65a5cd643186d2ae582cd4ac) 

browser versions
win 69.0.3497.92 XP
mac 69.0.3497.92 MAC
linux 69.0.3497.92 LINUX

win - windows 10
mac - high sierra 10.13.6
linux - ubuntu 16.04.5 LTS

Comment 69 by, Sep 21

Yes Caleb, this test is passing on all platforms.
You can see on WaterFall builds.

ChromeDriver 2.42.593063
testClickElement (__main__.MobileEmulationCapabilityTest) ... ok

phuongnd08... could you please share your repro code so we could run on our side.
Please also attach ChromeDriver verbose log file.

Comment 70 by, Sep 21

I can confirm this issue is still happening for me, 2.42 + Windows Virtual Machine.

Comment 71 by, Sep 21

hellpine.., please share your repro code and attach ChromeDriver verbose log file.

Comment 72 by, Sep 24

I'm not using chromedriver directly, but through capybara + chromedriver-helper which are ruby gems. Would a repro code in ruby be accepted here?

Comment 73 by, Sep 24

Sure we can use Ruby code as well. Please share your code.

Comment 74 by, Sep 24

Status: Verified (was: Fixed)
The fix is verified in Chromedriver 2.42

Comment 75 Deleted

Comment 76 Deleted

Comment 77 by, Sep 28

I can confirm it is failing in Mac with the same data as Comment 68
I have just downloaded de chromedriver (via ./node_modules/protractor/bin/webdriver-manager update) and I got version 2.42.5910 instead of 2.42.5930 as stated at Comment 69

Comment 78 by, Sep 28

Reproduced for me as well. Chromedriver 2.42, Mac OS 10.13.6.

Comment 79 by, Sep 28

Hi guys, we experienced that this issue is not happening always, it has something related with driver creation, so we implemented a conditional that kills the driver and starts it again at the beginning of our suite in BeforeSuite annotation.
Some notes: We use the same driver across all the suite so once click issue is not happening, driver is valid for the whole suite. If you create a driver in each test case probably this conditional should be placed in beforeClass annotation.
I hope this will be useful for you.

Comment 80 by, Sep 28

I am facing this issue every time. Below are the details-
OS- Windows server 2016
chrome-68.0.3440.75   Tried with chrome 69 also.

Comment 81 by, Sep 28

Project Member
For anyone still experiencing similar issue, could you please post code to repro the issue? The particular test mentioned in the title of this issue is now working very reliably in our internal testing. We are aware that some similar problems still exist, e.g., issue #2599. We can investigate any issues you are encountering only if repro code is provided.

Comment 82 by, Oct 1


In my case I think there is a problem with the readonly tag for the "Fly Out" and "Fly Back" fields

I'm attaching two features. 
The first one opens RyanAir home page and fills the trip airports and then enters a 20 second sleep. You can try to click on both input fields at the browser and you will see no reaction. 
The second feature, instead of the sleep command, sends the click command to the Fly Out field

You can have several logs at bugs  2322 ,  2323  and  2324
24.3 KB Download

Comment 83 by, Oct 1

tongilcoto... like it was stated in comment #81, let's all the issues related to click/tap on mobile emulation track with the issue #2599

I'll update the bugs  2322 -2324.

Sign in to add a comment