Comments (1)
Turns out that Frame
passed to AutomationServer.Instance.InitializeAndStart
not actual a root elements as whole application is wrapped into ScrollViewer
that allows system to scroll application top to make place for on-screen keyborad, etc. This was causing the incorrect location being returned in case of on-screen keyboard or other system windows scrolling application view to top.
This can be fixed by something like
public Automator(UIElement visualRoot)
{
var root = visualRoot;
while (true)
{
var parent = VisualTreeHelper.GetParent(root) as UIElement;
if (parent == null)
{
break;
}
root = parent;
}
this.VisualRoot = root;
this.WebElements = new AutomatorElements();
}
This will get rid of need to use GetClickablePoint
and Actions
to click to suggests.
Still needs research on possibility of replcaing custom location getter with GetClickablePoint
.
from winium.mobile.
Related Issues (20)
- How to handle Windows MobileOS popups HOT 2
- Could not connect to the InnerServer issue in Windows10 application on Windows 10 host system HOT 14
- Could not clear data in Edit control HOT 10
- Implement Element Clear command HOT 1
- How to use Xname Stratergy to find elements? HOT 10
- Can this be used to test apps on actual devices HOT 1
- XdeVirtualMachineException - "Emulator 8.1 WVGA 4 inch 512MB.username not found" HOT 5
- Not able to scroll using TouchScroll HOT 23
- Research Windows device portal
- Any CodeCverage Tool which i can use with my automation to get coverage ? HOT 2
- Make `could not connect to inner server` message more helpful
- Implement ExecuteScript command with automation: ScrollPattern.Scroll for Windows Silverlight apps.
- Use .NET Standard Library to merge most of common InnerServer functionality
- Add support for app close and app restart functionality HOT 1
- Handling system dialog HOT 2
- InnerServer loses stacktrace of exceptions, making it harder to debug issues
- Winium Mobile driver is not working on my Windows 10 system HOT 7
- Cannot deploy WP10 appxbundle HOT 4
- System.IO.FileNotFoundException when launching Winium Mobile Driver in Windows 10 HOT 1
- Not able to automate windows application when display resolution is set at 3840*2160
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from winium.mobile.