Posted 5 months ago. Visible to the public.

Clicking issues with chromedriver

ChromeDriver clicking works by simulating a mouse click in the middle of the element's first client rect (or bounding client rect if it doesn't have a first client rect). (Clicking issues)

So if you are trying to click on an element, chrome driver tries to click at the position where it first finds that element.

This can lead to some problems and unexpected behavior like:
- Element is not clickable at point ... erros
- Another element which is now located at this position receives the click

A step which finds and clicks the desired link via javascript may solve the problem:

When(/^I search and click on "([^"]*)"$/) do |text| page.execute_script("$(\":contains('#{text}'):not(:has(:contains('#{text}')))\").click()") end

- "Clicking" via JavaScript might click elements which are actually not clickable, e.g. because a modal overlay covers them. Use with caution.
- spreewald steps cause this error, too. You may need to override the according steps or write a custom step like above.

The bug seemed to appear in chromedriver versions > 2.12

By refactoring problematic code and creating automated tests, makandra can vastly improve the maintainability of your Rails application.

Author of this card:

Natalie Krehan
Last edit:
2 months ago
by Natalie Krehan
About this deck:
We are makandra and do test-driven, agile Ruby on Rails software development.
License for source code
Posted by Natalie Krehan to makandropedia