1

Regarding the Appium/Selenium 4 issue where complex mouse actions fail with the error: 'Currently only pen and touch pointer input source types are supported.'

Is there any official word, roadmap, or technical insight available on whether the Appium or Selenium teams plan to restore reliable Mouse Input support for desktop drivers (like WinAppDriver) within the W3C protocol, or if this limitation is now a permanent fixture?

using Audiqueen.TestUtilities; using Microsoft.VisualStudio.TestTools.UnitTesting; using OpenQA.Selenium; using OpenQA.Selenium.Appium; using OpenQA.Selenium.Appium.Windows; using OpenQA.Selenium.Interactions; using OpenQA.Selenium.Support.UI; using System; using System.Collections.Generic; using System.Collections.ObjectModel; using System.Diagnostics; using System.Linq; using System.Threading; namespace Audiqueen.AutomatedTest { public class WinAppDriver : WindowsDriver { private readonly AppiumOptions AppiumOptions; public WindowsDriver DesktopApplicationInstance { get; set; } public WinAppDriver(Uri uri, AppiumOptions appiumOptions, TimeSpan timeOut) : base(uri, appiumOptions, timeOut) { AppiumOptions = appiumOptions; FocusOnFirstHandle(); AppiumOptions desktopAppiumOptions = new AppiumOptions() { PlatformName = "Windows", AutomationName = "Windows", App = "Root", }; desktopAppiumOptions.AddAdditionalAppiumOption("appium:newCommandTimeout", 300); DesktopApplicationInstance = new WindowsDriver(new Uri(TestBenchManager.WindowsApplicationDriverUrl), desktopAppiumOptions, TimeSpan.FromMinutes(1)); } public void MouseMove(AppiumElement element, int offsetX = int.MaxValue, int offsetY = int.MaxValue) { if (offsetX == int.MaxValue && offsetY == int.MaxValue) { offsetX = element.Size.Width / 2; offsetY = element.Size.Height / 2; } Actions action = new Actions(this); action.MoveToElement(element).MoveByOffset(offsetX, offsetY).Build().Perform(); } } } 
3
  • 1
    Please provide enough code so others can better understand or reproduce the problem. Commented Nov 5 at 9:36
  • 1
    Thanks for the quick response I added the code, the error shows when running: action.MoveToElement(element).MoveByOffset(offsetX, offsetY).Build().Perform(); Commented Nov 5 at 13:23
  • you might try using TouchAction? See here: github.com/appium/dotnet-client/wiki/Touch-action-samples Commented Nov 5 at 21:04

1 Answer 1

0

This is a limitation of WinAppDriver.

Is there any official word, roadmap, or technical insight available on whether the Appium or Selenium teams plan to restore reliable Mouse Input support for desktop drivers

This would need to be fixed in WinAppDriver, not Selenium or Appium. Since it is not W3C compliant and hasn't had a release in several years, I doubt there are plans for this. You would need to contact the WinAppDriver maintainers (Microsoft) to verify.

Sign up to request clarification or add additional context in comments.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.