-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix: do nothing for an empty array in w3c actions #919
Conversation
Please update the |
Please also port the fix to mac2 driver when you have time |
it is very good at the moment. However, in the long term, it would be appreciated if the following actions could be supported with the xcuitest driver. (not frequently needed, but...)
|
Perhaps... such action can done via bluetooth keyboard usage only on a mobile device...? I haven't used but I guess... |
It's just that according to the specifications, such a combination should be possible, but I haven't seen it either. Hahaha. |
hm, failed tests ( |
## [8.7.8](v8.7.7...v8.7.8) (2024-07-18) ### Bug Fixes * do nothing for an empty array in w3c actions ([#919](#919)) ([9e70ec1](9e70ec1))
🎉 This issue has been resolved in version 8.7.8 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Unfortunately this is not possible with iOS XCTest APIs. They simply ignore modifier keys on input. |
Although the example was a modifier key, empty pauses can also be included on one side when using two or more pointer actions without a key action to satisfy the concept of "Tick". |
Instead of appium/appium-xcuitest-driver#2431
According to https://www.w3.org/TR/webdriver1/#input-source-state
So, I think an empty array should not return an error...? instead, it could just skip the actions.
With this change, vanilla selenium's send_keys w3c actions via xcuitest driver logic will be:
For now, the command raises: