UnsupportedOperationError: mouseMoveTo in Firefox

[zinevych]

I'm using the latest Protractor, with Firefox 52.0.1
Stack:
UnsupportedOperationError: mouseMoveTo
Build info: version: '3.3.1', revision: '5234b32', time: '2017-03-10 09:04:52 -0800'
System info: host: 'Oleksandr-Zinevych.local', ip: '192.168.0.102', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.12.3', java.version: '1.8.0_101'
Driver info: driver.version: RemoteWebDriver

Are there any workaround for this?

[NickTomlin]

Can you share an example test that generates this error?

I'm having the same issue, has there been any progress made on this issue?

Pinging @NickTomlin

The code that generated this result, on my machine, is as follows:

.then(function() {
            return browser.actions().mouseMove(element(by.id(passwordID))).click().perform();
})

This throws the following error in the terminal: "UnsupportedOperationError: mouseMoveTo"
Seems like chromedriver understands mouseMove getting mapped to mouseMoveTo, but geckodriver doesn't.

[larskendall]

I've been having the exact same problem. It's hindering a lot of my tests in Firefox at the moment.

[jatinmakhija]

I have been facing the same issues with my setup, anyone having any workaround for the same?

I tried firefox 45, 45.0.1 and 46 as well, but all of them are giving the same error.

@juliemr your help would be appreciated.

[zinevych]

Yes, for me just ordinal mouseMove generated this issue to. No workarounds, just switched to Chrome, where everything works OK.

[jatinmakhija]

I tried checking the actions related function in the repository but did not find anything, found a mention related to mouseMove changes but I am not sure what they are..

http://selenium.10932.n7.nabble.com/geckodriver-0-15-0-released-td55613.html

[heathkit]

geckodriver support for mouse actions is still new (see mozilla/geckodriver#159). If you're on the latest geckodriver (0.15) it should work maybe? It looks like 0.16 will have some fixes.

Firefox versions less than 52 will not work with Protractor 5 or higher. Mozilla completely redid their automation for Selenium 3. There's no looking back!

[mike123vn]

Hi, selenium has confirmed that they fixed this issue. I updated to new version of selenium, gecko driver and firefox but i still get - Failed: mouseMoveTo
SeleniumHQ/selenium#3693

[tamilranj]

Hi,

I tried using the combination of FF version 53, 54 and 55. Geckodriver version 0.15.0, 0.16.1, 0.17.0 and o.18.0, Also selenium server version 3.4.0, 3.3.1, 3.0.1 and 2.53.1.

But still seeing issues on mouseMove. Can someone please help?

Failed: mouseMoveTo
Build info: version: '3.4.0', revision: 'unknown', time: 'unknown'
os.name: 'Windows 8.1', os.arch: 'x86', os.version: '6.3', java.version: '1.8.0_121'
Driver info: driver.version: RemoteWebDriver

[joelwatson]

@tamilranj I'm pretty sure that the mouseMove issue (and other related issues) are still present. The issues have been resolved on the Geckodriver side (from what I understand), but now there is an issue with Selenium Server itself, primarily (if not exclusively) related to the standalone version.

You can learn more by checking out the comments on this issue: SeleniumHQ/selenium#3693

Apparently all will finally be resolved in SS 3.5; but there is no word of when the release will be, other than "soon". :)

[tienvx]

I believe the mouseMove issue is still present in Selenium 3.5.1. I found a work around:

1. Upgrade selenium to 3.5.1
2. Upgrade firefox to 55.0.2
3. In protractor.conf.js set marionette to false

multiCapabilities: [
    {
      'browserName': 'chrome'
    },
    {
      'browserName': 'firefox',
      'marionette': false
    }
]

I'm surprised because firefox is running test cases faster this way, and no more mouseMove errors.

[timbru31]

@tienvx I vote against turning Marionette off, since WebDriver (the W3C) version is the future and you should, where possible, not rely on the old JSONWP protocol.