Overview
Automating user interactions, such as a mouse hover, on elements outside of the main web page's Document Object Model (DOM) can be challenging. A common example is triggering an event by hovering over a browser tab's close icon. Standard element selectors cannot target these browser-level UI components. However, this can be achieved using a specialized mouse movement feature in Architect.
How It Works
The Mouse Move functionality allows you to simulate precise cursor movements, enabling interactions with elements outside the web page's viewport. The feature uses coordinates to define the cursor's path:
- Mouse Start X/Y: The initial coordinates of the cursor.
- Mouse X/Y: The final coordinates of the cursor.
These values are measured in pixels from the top and left edges. For example, a movement from (Start X: 200, Start Y: 200) to (X: 300, Y: 200) will shift the cursor 100 pixels to the right while maintaining its vertical position.
There are two primary movement types:
- Screen Absolute: Coordinates are relative to the entire window. This setting is necessary for interacting with browser UI elements like tabs.
- Viewport Absolute: Coordinates are relative to the web page itself.
Limitations
This method requires you to determine the exact pixel coordinates for the target UI element. These coordinates may vary depending on screen resolution, window size, and browser version, which can make the test less stable if not managed carefully.
Related Information
If you encounter difficulties implementing the Mouse Move feature, it is helpful to provide the support team with the specific use case and a detailed test workflow. This information will allow for a more thorough investigation and a precise resolution.