Chome 61, ChromeDriver 2.32 Click element for mobile devices emulators throws WebDriverException: unknown error: element is not accessible for click at a point

I have tests that worked fine in Chrome 60 and ChromeDriver 2.31, but after upgrading Chrome to version 61, I had to upgrade ChromeDriver to 2.32. And now I get sporadic org.openqa.selenium.WebDriverException: unknown error: the element does not click at the point (X, Y) - in all tests that run for emulators of mobile devices, such as iPhone 6 Plus browser mode,

eg.

As a workaround, I would probably use scrolling to an element until it clicks, but this is just a quick fix, and itโ€™s better to know where this problem comes from. Is this a problem with recent releases of Chrome and drivers? Will it be fixed soon?

The problem is reproduced on both the local and the remote web server.

Stacktrace:

org.openqa.selenium.WebDriverException: unknown error: item is not clickable at point (182, 3724) (session information: chrome = 61.0.3163.91)
(Driver information: chromedriver = 2.32.498550 (9dec58e66c31bcc53a9ce3c7226f0c1c5810906a), platform = Windows NT 10.0.15063 x86_64) (WARNING: the server did not provide any stack information) Duration or timeout command: 115 milliseconds information about the collection: 115 milliseconds Information about: 3.4.0 ', version:' unknown ', time:' unknown 'System information: host:' xxx ', ip: '10 .100.8.33', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10 .0 ', java.version:' 1.8.0_131 'Driver information: Features org.openqa.selenium.chrome.ChromeDriver [{applicationCacheEnabled = false, rotatable = false, mobileEmulationEnabled = true, networkConnectionEnabled = false, chrome = {chromedriverVersion = 2.32.498550 (9dec58e66c31bcc53a9ce3c7226f0c1c5810906a), UserDataDir = C:\ Users \ xxx \ AppData \ Local \ Temp \ scoped_dir5912_31757}, takeHeapSnapshot = true, pageLoadStrategy = normal, databaseEnabled = false, handleAlerts = true, hasTouchScreen = true, version = 61.0.3163.91, platform = XP, browserConnectionEnabled = false, true, acceptSslCerts = true, locationContextEnabled = true, webStorageEnabled = true, browserName = chrome, acceptsScreenshot = true, javascriptEnabled = true, cssSelectorsEnabled = true, setWindowRect = true, unexpectedAlertBehaviour session8fivefd8fff8fd}nativeEvents = true, acceptSslCerts = true, locationContextEnabled = true, webStorageEnabled = true, browserName = chrome, accepts Screenshot = true, javascriptEnabled = true, cssSelectorsEnabled = true, setWindowRect = session1, session1, timeframe_function_function_function_function_function_function_file 257 millisecondsnativeEvents = true, acceptSslCerts = true, locationContextEnabled = true, webStorageEnabled = true, browserName = chrome, accepts Screenshot = true, javascriptEnabled = true, cssSelectorsEnabled = true, setWindowRect = session1, session1, timeframe_function_function_function_function_function_function_file 257 milliseconds

, https://bugs.chromium.org/p/chromedriver/issues/detail?id=1852

+6
6

Chrome , . ChromeDriver 2.33.

+4

chrome 59.0 (32 ), chrome. ,

+1

, . , , move_to_element() Selenium .

, python

   def scroll_to_element(element):
       self.driver.execute_script("window.scrollTo(0, %d);" % 
       element.location['y'])

- . , .

+1

:

:

driver.manage().window().maximize();

-, Action moveToElement

WebElement element = driver.findElement(By("element"));
Actions action = new Actions(driver);
action.moveToElement(element).click().perform();
0

, javascript, .

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

I have the same problem (movetoelement does nothing in movilemulation mode with chromedriver2.32 and Chrome61 +), and the only solution for me returned to Chrome60. You can get older versions of chrome at https://www.slimjet.com/chrome/google-chrome-old-version.php

When chromedriver2.33 arrives, I will check again against Chrome61 +

0
source

All Articles