Skip to content
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

[Feat]: alternate sendkey strategy/ies for iOS web #20004

Closed
jlipps opened this issue Apr 16, 2024 · 1 comment · Fixed by appium/appium-xcuitest-driver#2386
Closed

[Feat]: alternate sendkey strategy/ies for iOS web #20004

jlipps opened this issue Apr 16, 2024 · 1 comment · Fixed by appium/appium-xcuitest-driver#2386
Labels

Comments

@jlipps
Copy link
Member

jlipps commented Apr 16, 2024

iOS web automation relies on injecting JS. Different web app frameworks respond to this in different ways. Sometimes setting a field's value directly as full strings as the atoms do doesn't trigger input events. But sending them one key at a time does. Here's a proposal for a capability like appium:sendKeyStrategy, with values like default (just do what the atoms do) or oneByOne, which iteratively calls send keys internally for each character in the string.

@KazuCocoa
Copy link
Member

KazuCocoa commented Apr 16, 2024

We had sendKeyStrategy as oneByOne and grouped before for ios driver (not xcuitest driver). Possibly we could follow the naming...?

Then, appium/appium-remote-debugger#376 can be closed with this idea. The PR was ordinally brought react js workaround into Appium Atoms again. For this caps's description could address "react" framework to help the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants