e2e tests: clicks are not working when using mobileOptions capabilities

[tbosch]

Calls to browser.click() are doing nothing when I run benchmarks / e2e tests using protractor and have the capabilities below. There are no errors in the browser log, clicking on the buttons manually works, and removing the mobileEmulation entry from the capabilities also makes the tests work again.

This is probably a bug in chromedriver, but needs more investigation and a simple reproduction case to file an issue there.

{
  browserName: 'chrome',
  chromeOptions: {
    'mobileEmulation':   {
      'deviceMetrics': {
        'width': 600,
        'height': 960,
        'pixelRatio': 2
      }
    }
  }
}

[juliemr]

Note that this works for chrome 43 and 45 (canary).

[tbosch]

I am using the following command:

./node_modules/.bin/protractor protractor-js.conf.js --benchmark --specs=dist/js/cjs/benchmarks/e2e_test/tree_perf.js

Note that the benchmarks don't throw, but just don't click on the button, i.e. the tree does not show and hide while the benchmark is running.

[juliemr]

Reproduced with plain old selenium-webdriver using selenium-webdriver node module 2.45, selenium 2.45, and chromedriver 2.14, and Chrome > 43. See https://github.com/juliemr/webdriver-bugs/blob/master/mobileclick.js

New versions of selenium and chromedriver are out today. I'm going to try updating and see if that fixes.

[juliemr]

See angular/protractor#2245

[juliemr]

With updated selenium and chromedriver, this passes on Chrome 44 beta but fails on Chrome 45 canary because the click goes to the wrong element.

Issue submitted to ChromeDriver: https://code.google.com/p/chromedriver/issues/detail?id=1127

[juliemr]

Closing since the issue is now filed with chromedriver.

[nexstreamray]

Hey @juliemr, the clicks are still not working on current chrome driver.
Any updates for this issue?

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}