-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confirm commands for W3C actions #733
Comments
|
UIA2Easy action. Just tapping a particular element.
|
UIA2And I also can do the following command:
Documentation:
For client, we can call previous touchactions. |
WDA
I could do with
|
@mykola-mokhnach To set
|
@KazuCocoa It's by design. W3C spec makes a clear distinction between different pointer types (currently 3 types are defined: mouse, pen and touch). Only touch pointers are supported on iOS and Android has support of all types. That is why you see the error below. We could think about additional wrappers/helpers on appium Ruby client side to make the creation on Actions object with touch pointer type easier |
https://github.com/jlipps/simple-wd-spec#location-strategies
Ruby client converts some elements to css celector like: def convert_locators(how, what)
case how
when 'class name'
how = 'css selector'
what = ".#{escape_css(what)}"
when 'id'
how = 'css selector'
what = "##{escape_css(what)}"
when 'name'
how = 'css selector'
what = "*[name='#{escape_css(what)}']"
when 'tag name'
how = 'css selector'
end
[how, what]
end Don't convert to Appium, so far. |
📝
|
📝 |
This is a
Summary
W3CActionBuilder: https://seleniumhq.github.io/selenium/docs/api/rb/Selenium/WebDriver/W3CActionBuilder.html
Environment
ruby_lib
version:Actual behaviour and steps to reproduce
Expected behaviour
Link to Appium/Ruby logs
Create a GIST which is a paste of your full Appium logs, and link them here.
Any additional comments
The text was updated successfully, but these errors were encountered: