Bug 222466 – WebDriver Click at Offset doesn't work

• Component: WebDriver
• Status: NEW

[Luke Hill]

When using iPhone 8 on iOS12 I am attempting to click on an offset. The actual scenario is

Clicking off a menu will close the menu.

We have tried the following.

In Ruby Capybara -> `element.click(x: 0, y: 400)`
In raw selenium -> `element.click(x: 0, y: 400)`
In ActionBuilder -> `ab.move_to(el, 1, 400).perform`

All three throw errors. Deep-diving into the errors suggests the endpoint doesn't exist.

The lowest level error (ActionBuilder), is below

```
ab.move_to(el, 1, 400).perform
=> An unknown server-side error occurred while processing the command. Original error: Error Domain=com.facebook.WebDriverAgent Code=1 "Unsupported origin type '{
    ELEMENT = 5004;
    "element-6066-11e4-a52e-4f735466cecf" = 5004;
}' is set for '{
    duration = 250;
    origin =     {
        ELEMENT = 5004;
        "element-6066-11e4-a52e-4f735466cecf" = 5004;
    };
    type = pointerMove;
    x = 0;
    y = 0;
}' action item. Supported origin types: (
    pointer,
    viewport
) or an element instance" UserInfo={NSLocalizedDescription=Unsupported origin type '{
    ELEMENT = 5004;
    "element-6066-11e4-a52e-4f735466cecf" = 5004;
}' is set for '{
    duration = 250;
    origin =     {
        ELEMENT = 5004;
        "element-6066-11e4-a52e-4f735466cecf" = 5004;
    };
    type = pointerMove;
    x = 0;
    y = 0;
}' action item. Supported origin types: (
    pointer,
    viewport
) or an element instance}
```

[Luke Hill]

It seems as though maybe the co-ordinates aren't being passed through as the y value seems to be 0.

[Alexey Proskuryakov]

iOS 12 is several years old. Does this affect the latest shipping release? Could you please provide a functional repro case if so?

[Luke Hill]

Given Safari 13 is buggy as hell. Safari 12 was the best testable browser. I appreciate it's old, but it's still supported and a very common browser.

Furthermore, I'm not sure how easily / readily available testing on Big Sur is / iOS14.

Could you try see if you can reproduce this please.

[Luke Hill]

Failing that. If this is something which "isn't an issue" in iOS13+, then we can amend our test matrix to just skip these tests on ios12 and below. But some clarity would help us make the best decision for what to do.

[Alexey Proskuryakov]

WebKit Bugzilla is a place to track issues that occur in current WebKit code base. As we cannot go back in time and fix issues in releases that happened years ago, it doesn't make sense to track them here.

Perhaps people working on WebDriver will happen to know about this issue and help anyway, but that cannot be the expectation.

[Luke Hill]

I have just re-tested on 3 devices on iOS13. All throw the same error.

[Luke Hill]

Re-testing on one device using iOS 14.0 also throws the same error.

[Alexey Proskuryakov]

Thank you for testing!

[Radar WebKit Bug Importer]

<rdar://problem/74995314>

[Luke Hill]

Any updates on this (Been a couple of months)

Also what is the policy on bugfixes. Are they only made available for the latest driver?