You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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 likedefault
(just do what the atoms do) oroneByOne
, which iteratively calls send keys internally for each character in the string.The text was updated successfully, but these errors were encountered: