Jonathan Lipps

There's an element with AXDescription of "main display" -- it's the part where the calc output is displayed.

The AXPath I get in scientific mode (`"/AXApplication[@AXTitle='Calculator']/AXWindow[@AXIdentifier='_NS:477' and @AXSubrole='AXStandardWindow']/AXGroup[@AXIdentifier='_NS:9']"`) is also not findable from my test, either in scientific or regular mode. ``` [HTTP] --> POST /wd/hub/session/cd0128db-e2c2-44ce-8a2f-2dd17879066d/elements {"using":"xpath","value":"/AXApplication[@AXTitle='Calculator']/AXWindow[@AXIdentifier='_NS:477' and...

I don't think informing them is enough. We might need some error handling if we don't want the app to be unusable. In the meantime I'm not sure whether it...

This would probably be a pretty simple PR that just adds the necessary boilerplate for JUnit 5 (with potentially some other refactoring to make sure all Java code is shared,...

If you're talking about a long touch press (not a long key press), then the only way you'll be able to solve this now is to use the Actions API...

No, no other workaround is available in the inspector at this time.

it's already released

@Dcode78 Appium Desktop no longer bundles the inspector, and hasn't in a very long time. there will be no updates to the old inspector that was bundled with the Appium...

seems like this is including a lot of irrelevant commits and should be rebased on master. also i'm not entirely sure of the purpose of this change. can't the inspector...

hi @allen-fang can you share any more information about what the error is? I do see that caps are set to null in this case but I don't see an...