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
For a quite a while now, I've been dealing with apps that show content on multiple displays.
E.g., a POS app that apart from the main screen, has a secondary screen for the customer to see the transaction.
Currently three's no way to switch the driver's focus between displays, interact with the those elements and do assertions.
Hmmmm, aren't those settings only settable/available when setting up/creating the driver?
Not sure how I'd use that to change the driver screen focus on the fly.
Settings are not the same as capabilities, and can be changed at any time during a session. For more information, check the Settings API documentation.
Settings are not the same as capabilities, and can be changed at any time during a session. For more information, check the Settings API documentation.
Understood. I'll give a try then👌
Thanks, guys.
Note: I'll keep the discussion open, it'd be cool to have the implementation abstracted in Appium.
Is your feature request related to a problem?
For a quite a while now, I've been dealing with apps that show content on multiple displays.
E.g., a POS app that apart from the main screen, has a secondary screen for the customer to see the transaction.
Currently three's no way to switch the driver's focus between displays, interact with the those elements and do assertions.
UiAutomator just added support for multiple displays on version 2.3.0 as we can read here: https://developer.android.com/jetpack/androidx/releases/test-uiautomator#2.3.0
Would it be possible to implement that in the upcoming version(s) of Appium?
Describe the solution you'd like.
Being able to switch the driver's focus between displays.
Describe alternatives you've considered.
No response
Additional context
Someone already mentioned this here #18787 (comment), and here appium/appium-inspector#1294 (comment)
The text was updated successfully, but these errors were encountered: