Bug 218232 - [iOS 14][iPhone] safaridriver returning 501 "not implemented" on w3c-Action pointer-type "touch" and "mouse"
Summary: [iOS 14][iPhone] safaridriver returning 501 "not implemented" on w3c-Action p...
Status: RESOLVED DUPLICATE of bug 216937
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: Safari 14
Hardware: iPhone / iPad Other
: P2 Critical
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-27 07:35 PDT by bugzilla
Modified: 2020-10-27 08:07 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugzilla 2020-10-27 07:35:22 PDT
Hi there, 

We implemented our own ActionChain that works in Safari 13. In Safari 14 it's not working anymore.

we use a POST-Request to the safaridriver binary (we tested technology preview and the standard one) to the session url "session/{{sessionId}}/actions" with JSON

{
    "actions": [
        {
            "type": "pointer",
            "id": "touch",
            "parameters": {
                "pointerType": "touch"
            },
            "actions": [
                {
                    "type": "pointerMove",
                    "duration": 0,
                    "origin": "viewport",
                    "x": 10,
                    "y": 20
                },
                {
                    "type": "pointerDown",
                    "button": 0
                },
                {
                    "type": "pointerUp",
                    "button": 0
                }
            ]
        }
    ]
}

this request returns a 501-error:

{
    "value": {
        "error": "not implemented",
        "message": "",
        "stacktrace": ""
    }
}

in Safari 14.

In Safari 13 the action performs and the request succeeds with the return

{
    "value": null
}

I think that this bug came with Safari 109 because it's the only one that does something with WebDriver.
Comment 1 BJ Burg 2020-10-27 08:07:31 PDT
Thanks for reporting. I believe this has been fixed already in trunk, please verify that it is fixed in STP 115 or later.

*** This bug has been marked as a duplicate of bug 216937 ***