The interactions API hasn't been implemented yet.

Issue 4152 has been merged into this issue.

This issue was updated by revision r17393.

Interaction API tests should be re-enabled once implemented for the SafariDriver.

I was just wondering, going through issue 2067, I ported the code sample in comment
#60 to Java and my colleague tested it out and it appears to work for mouse over in
Safari. I did the port in hopes to fix issue with FF and IE, but seems it works for
Safari too.

So then, from that, I assume as a temporary workaround, some of the interactions API
could be simulated with javascript code calls, at least for mouse and keyboard events?

I am also getting the same issue with safari browser.

Error :

Unknown command: mouseMoveTo (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 9 milliseconds
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0_30'
Driver info: driver.version: ReusableInternetExplorerDriver

Thanks,
Siva

WorkAround : 

public boolean onMouseOver(WebElement element)
    {
        boolean result = false;
        try
        {
            String mouseOverScript = "if(document.createEvent){var evObj = document.createEvent('MouseEvents');evObj.initEvent('mouseover',
true, false); arguments[0].dispatchEvent(evObj);} else if(document.createEventObject)
{ arguments[0].fireEvent('onmouseover');}";
            JavascriptExecutor js = (JavascriptExecutor) driver;
            js.executeScript(mouseOverScript, element);
            result = true;
        }
        catch (Exception e)
        {
            e.printStackTrace();
            result = false;
        }
        return result;
    }

Thanks,
Siva

Can you provide the equivalent code for this method, please?

public static void dragTo(WebElement from, WebElement to)
    {
        Actions builder = new Actions(driver);
        Action dragTo = builder.clickAndHold(from).moveToElement(to).build();
        dragTo.perform();
    }

When will this issue be released? Thanks a lot!

I am facing same issue on Safari for DragDrop element.

Any update on official Safari web driver? When we can get fix on above issue.  

Just found this today, haven't tried it out, but looks like good option for drag & drop
for Safari as well as a fallback for other browsers should the native drag & drop fail
for some reason:

Javascript based drag & drop for WebDriver...
http://ynot408.wordpress.com/2011/09/22/drag-and-drop-using-selenium-webdriver/

Issue 5046 has been merged into this issue.

Issue 5093 has been merged into this issue.

Any update? Alternatively, is there a good place to start looking into how to implement
this feature?

i've got a moderately complex set of web tests that make extensive use of drag-and-drop
to test, well, drag-and-drop behaviour of an app. These tests work fine in Chrome and
FireFox - I want to make them work in Safari as well.

FYI, if we're talking drag & drop support, the solution I mention in comment #10 works
in Safari. I tested it. 

So you'd just need to write a special wrapper method to drag & drop so that you use
the interactions API on all browsers except Safari for which you'd use javascript simulation.

Granted it's not realistic testing but it works as a workaround until this issue is
resolved.

Issue 5809 has been merged into this issue.

Anything new on this besides the JavaScript workaround?

Is there any news/updates on this issue? I am having issues with this and Safari and
am wondering if the only current workaround is to use javascript.

Same here. Presumably the JS workaround is the way to go. What I don't get is why it
is actually included in the product. It's by no means usable. 

On comment #18,

I haven't tried invoking any of the interactions API since I've come across this issue,
I just use the JS workarounds.

So what does happen when you invoke the unimplemented APIs? If it's just that nothing
happens, you have a valid point. If a some exception is thrown, that's at least ok
to me. 

I would figure some "unimplemented API" exception would be ideal to let the users know
this particular API is not yet available for use for the given driver. But all the
drivers should support (as in respond to) all the WebDriver APIs because they are driver
interfaces to it, and simply respond with an exception to indicate "I don't support
that right now" when an unsupported API is invoked, since we want a standardized way
to use the drivers.

By the way, for context, this topic seems quite important to some people. What's so
bad about javascript workaround in the meantime?

Is it because you "really must" test something with native mouse interaction, etc.?

Or you have trouble finding the right javascript workaround code to use?

It does raise an exception: "WebDriverException: Message: u"Unknown command: mouseMoveTo"

It's not that I don't want to use the javascript implementation, It's more that I wanted
to know if there are any limitations to using it (using the API's click() on a WebElement
does not always trigger javascript events and so using javascript to emulate it is
a must in some instances). 

From what I gather, there shouldn't be any limitation using the javascript route. What
I've heard (in terms of IE and maybe Firefox) though is that it may not be as realistic
in simulating actual mouse behavior (based on the internal implementation of the browser
driver) for the browser being automated. But for Safari, there's currently no difference,
you either have the functionality (through javascript) or not (without it).

Just to clarify, the SafariDriver uses 100% synthetic events.  When the interactions
API is implemented, it will be done using synthetic javascript events from Selenium's
browser automation atoms library.

Hi Selenium Team,

Is this issue fixed and what is the latest status of this issue..

Thanks,
Srinivas

Issue 7037 has been merged into this issue.

Please update us on this issue, thanks in advance.

God bless!

Safari is not a priority, sorry. But your patches are welcome!

To anyone still interested this is the workaround method I used for moveToElement -->

Tested by me and works..

public void moveToElement(WebDriver driver, WebElement element, By locator) {
        if (!(driver instanceof SafariDriver)) {
            Actions builder = new Actions(driver);
            builder.moveToElement(element).perform();
        }
        else {
            JavascriptExecutor js = (JavascriptExecutor) driver;
            String locatorType = locator.toString().substring(3);
            String elem = "var elem = document;";
            if (locatorType.startsWith("id")) {
                elem = "var elem = document.getElementById(\""+locatorType.substring(4)+"\");";
            }
            else if (locatorType.startsWith("xpath")) {
                String snippet = "document.getElementByXPath = function(sValue) { var a = this.evaluate(sValue,
this, null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null); if (a.snapshotLength > 0)
{ return a.snapshotItem(0); } }; ";
                js.executeScript(snippet);
                elem = "var elem = document.getElementByXPath(\""+locatorType.substring(7)+"\");";
            }
            else if (locatorType.startsWith("className")) {
                elem = "var elem = document.getElementsByClassName(\""+locatorType.substring(14)+"\")[0];";
            }
            String mouseOverScript = elem + " if(document.createEvent){var evObj = document.createEvent('MouseEvents');evObj.initEvent('mouseover',
true, false);" +
                    " elem.dispatchEvent(evObj);} else if(document.createEventObject) { elem.fireEvent('onmouseover');}";
            js.executeScript(mouseOverScript);
        }
    }

For #38, what code exactly is giving you issue?

Hi,

In regards to my problem :

Exception in thread "Thread-2" org.openqa.selenium.WebDriverException: Unable to uninstall
extension
Caused by: java.io.FileNotFoundException: /var/folders/9k/22zq2y2x1mj_pglnzq_g6rfr0000gp/T/SafariBackups4126064663359463498webdriver/Extensions.plist
(No such file or directory)

After looking a bit closely, its not the code in #38 that is at fault, but in:

            Actions builder = new Actions(driver);
        builder.clickAndHold(l_draggable);
        Thread.sleep(500);
        moveToElement(driver, By.id("droppable")); //Using the code in #38
        builder.release().perform();

Removing builder.release().perform(); solves my problem. (Since my problem has no beareance
on this thread I have removed it)...

Unfortunately I was unable to get the code in #38 to work regardless of my problem.
However the following worked for me:

    public void dragdrop(WebDriver driver, By ByFrom, By ByTo) {
        WebElement LocatorFrom = driver.findElement(ByFrom);
        WebElement LocatorTo = driver.findElement(ByTo);
        String xto=Integer.toString(LocatorTo.getLocation().x);
        String yto=Integer.toString(LocatorTo.getLocation().y);
        ((JavascriptExecutor)driver).executeScript("function simulate(f,c,d,e){var b,a=null;for(b
in eventMatchers)if(eventMatchers[b].test(c)){a=b;break}if(!a)return!1;document.createEvent?(b=document.createEvent(a),a==\"HTMLEvents\"?b.initEvent(c,!0,!0):b.initMouseEvent(c,!0,!0,document.defaultView,0,d,e,d,e,!1,!1,!1,!1,0,null),f.dispatchEvent(b)):(a=document.createEventObject(),a.detail=0,a.screenX=d,a.screenY=e,a.clientX=d,a.clientY=e,a.ctrlKey=!1,a.altKey=!1,a.shiftKey=!1,a.metaKey=!1,a.button=1,f.fireEvent(\"on\"+c,a));return!0}
var eventMatchers={HTMLEvents:/^(?:load|unload|abort|error|select|change|submit|reset|focus|blur|resize|scroll)$/,MouseEvents:/^(?:click|dblclick|mouse(?:down|up|over|move|out))$/};
" +
        "simulate(arguments[0],\"mousedown\",0,0); simulate(arguments[0],\"mousemove\",arguments[1],arguments[2]);
simulate(arguments[0],\"mouseup\",arguments[1],arguments[2]); ",
        LocatorFrom,xto,yto);
    }

//This is based on findings in : http://ynot408.wordpress.com/2011/09/22/drag-and-drop-using-selenium-webdriver/

I am having the following piece of code in my script

Actions action = new Actions(driver);
action.sendKeys(month);
action.perform();

Since the reference is to a method(sendKeys) in Action.class, this execution fails
on safari.
SendKeys in action class is as follows:

public Actions sendKeys(WebElement element, CharSequence... keysToSend) {
    action.addAction(new SendKeysAction(keyboard, mouse, (Locatable) element, keysToSend));
    return this;
 }

Can you let me know what work around can be used.

Appreciate your response.

Thanks

On comment 41, why would you do it this way? What's the requirement?

Because the common approach works:

WebElement.sendKeys("keys");

that would be my workaround.

On Comment 42, We are trying to build script for a web application to be tested on all
browsers and devices. 
When executed on devices following were few issues we faced:
1.When the tests are executed on devices, the native control of the device pops-up
for a drop down etc. 
2. When navigated from one page to another (pages having a scroll bar), the page control
remained at the bottom of the page instead of the top of the page.Hence we have to
do a pageup.

For both the issues faced following were the solutions we are using
1. We are sending keys to the dropdown in few cases, However we could use Select which
is specific to dropdown.
2.For pageup, the only solution we have is to use Actions
Actions action = new Actions(driver);
action.sendKeys(Keys.HOME);
action.perform();

Hence we want to avoid usage of Action in our framework so that its compatible with
all browsers and devices. 

This was one main reason for which I was looking out for a workaround.

Appreciate your response.

Issue 8447 has been merged into this issue.

moveToElement() is not working in any Safari version, not even 8.

The only option is writing a JavaScript function that will hover over the element.
BUT that doesn't cover all situations.
In cases where the mouse hover was implemented in the page using JavaScript, it will
work, but in the cases it was built using CSS pseudo elements, it won't work.
I tried a lot to make this work, and this answer also says it's not a "W3C trusted
event":
http://stackoverflow.com/a/17226753/705147

FYI, you know, when all else fails, while waiting for this feature (or bug fix), the
last resort option can be to use external tools to integrate with Selenium/SafariDriver
to handle the limitations (e.g. Java Robot class, AutoIt, Sikuli). Not clean/pretty,
but at least you're not stuck.

And if you need to figure out how to deploy this integration for Grid, something like
this may work:

https://gist.github.com/daluu/3b4746f6b672c49f7e8f

Manga,

Thanks for the info. I looked up all the code from "PartialSeleniumGridIntegrationWithAutoItExample.java",
but I don't think any of those options will work with BrowserStack nor Saucelabs.

I also looked up your projects, but if I'm not mistaken, all options require some lib
or jar to be deployed and executed in the node machine. Given that my current client
uses BrowserStack, I had to drop support for Safari in a bunch of tests.

When testing javascript heavy sites (GWT, Dojo, AngularJS), the Actions interface allows
automation without fighting the dreaded Selenium stale element exception agony as items
are constantly added and removed from the DOM. 

Not implementing the Actions interface in Safari is a significant shortcoming for my
team and application. 

We're not concerned that it requires actions to be implemented via javascript and that
they aren't native browser events. We fight the same problems in the other browser
implementations as well. It's a necessary evil. 

I encountered the same issue as Issue 6615, which has been merged to this issue, looking
for workaround. Thanks.
https://code.google.com/p/selenium/issues/detail?id=6615

Actions action = new Actions(driver);
action.moveToElement(element);
action.clickAndHold();
action.moveByOffset(100,200).moveByOffset(-10, -20).moveByOffset(-10, -10).moveByOffset(-10,
-20).build().perform();
action.release().build().perform();

can you please provide the work around for the above code.

For comment 51, take a look at the 2nd code snippet for mousemove under: https://ynot408.wordpress.com/2011/09/22/drag-and-drop-using-selenium-webdriver/

that's a starting point for crafting a JS only workaround.