Protractor: Selenium Grid - Firefox - UnknownCommandError: POST /session/{sessionId}/moveto did not match a known command

[sahil1610]

Bug report

• Node Version: 8.9.1
• Protractor Version: 5.2.2
• Angular Version: 1.3.7
• Browser(s): Firefox
• Operating System and Version OS X MAC SIERRA

Meta -

OS: OSX

Selenium Grid Version: 3.8.1

Browser: Firefox

Browser Version: 57.0.4

Expected Behavior - Actions class function should work

Actual Behavior - Actions class function are not working

_This issue is specific to selenium grid only_

Grid is setup using DOCKER with the latest versions of selenium, chrome and firefox

Steps to reproduce -

Run the following protractor script in FIREFOX browser:

describe('Test', function () { 'use strict'; it('Firefox Actions class', function () { browser.get('http://www.protractortest.org/#/'); browser.actions().mouseMove(element(by.css('.github-button'))).perform(); browser.sleep(10000); }); })

_Note that the same works on Selenium grid 3.2.0_

As per https://github.com/SeleniumHQ/selenium/issues/5332 this is an issue with Protractor

[IgorSasovets]

Hi, @sahil1610! I had the same issue with Firefox. Here is my solution: https://github.com/IgorSasovets/protractor-firefox-support

[ChristianM18]

Hi!
Same issue here, ActionSequences do not work starting from Firefox 47.

• Selenium 3.9.1
• GeckoDriver 0.19.1
• Protractor 5.2.2

Thank you @IgorSasovets for your solution, I will test it when I can.

[IgorSasovets]

Hi, @CoCay ! I hope that my solution will help you. Please take a look at https://github.com/IgorSasovets/protractor-firefox-support/blob/master/tests/drag-and-drop-test.js. There are examples of usage.

[sahil1610]

Hi @IgorSasovets your solution works, but same has to be fixed within protractor. It's been more than 1 year since selenium 3 is launched and mouse move is not working since then.

[IgorSasovets]

Hi @sahil1610 ! I'm happy that my solution helped you. Hope that they will fix this problem ASAP.

[sarndt]

I still have this issue, is there any ETA when this will be fixed?

[lacymorrow]

Still having this issue

[rkrisztian]

I've been using Docker images from https://github.com/elgalu/docker-selenium, which put Chrome and Firefox into the same container (as opposed to https://github.com/SeleniumHQ/docker-selenium), thus by default it exposes a Selenium Grid port to us, rather than just a Node. However, elgalu's images can be configured to expose the ports of the Firefox- and Chrome-specific Selenium nodes directly.

=> When using the Grid, Protractor tests fail.
=> When using the Nodes directly, Protractor tests are OK.

I also did a check with the Selenium Java bindings against the same container:

new Actions(seleniumDriver)
.moveToElement(seleniumDriver.findElement(By.id("someField")), 5,5)
.moveByOffset(5, 5)
.build().perform();

=> In both cases, the action could be performed just fine.

=> Yes, this seems a bug in Protractor.

(Answering this because it wasn't trivial for SeleniumHQ/selenium#5332 ...)

[rkrisztian]

Might be fixed in Protractor 6, need to retest...

[sahil1610]

@rkrisztian It's still not fixed