Also it prevents to interact with HammerJS when using ChromeDriver. HammerJS only listen to PointerEvents when the browser support them.

DOM PointerEvents should be generated when you send it MouseEvents or TouchEvents.

You can think of MouseEvents/TouchEvents as the raw native event indicating what event is to be sent.

Do you have an example where this isn't working?

Over to Navid to triage appropriately.

Yeah. I was also under the impression that it worked.

Jonathon, can you take a look at this? Where does the input from ChromeDriver exactly get injected?

After a quick test using selenium and Chromedriver 2.34, I saw that no PointerEvents are produced during touch actions. I tested with Flick action on a web element listening to "touchstart" and "pointerdown" event.

The callback on "touchstart" event is called, but it is never called for "pointerdown" using Chromedriver 2.34. However both events are called when performing touch manually.

Function responsible for emitting the TouchEvent is : "dispatchTouchEvent(x, y, type)" from "/chromium/chrome/test/chromedriver/js/dispatch_touch_event.js", but do not seem to emit PointerEvent.

Don't know how to provide you with a quick working example on this since I use Selenium to use Chromedriver.

Thanks.

Hello!

As far as pointer events go, there is a CL for having this functionality in ChromeDriver right now, trying to land it soon.

https://chromium-review.googlesource.com/c/chromium/src/+/650369

Thank you for that, really appreciate it.

Lan is looking in this issue. We need to change the path that the events are injected via ChromeDriver.

Do you know in when this issue will be fixed ?

We are making changes in window_commands.cc now, I will work on element_commands.cc this month.

Ok thanks, I will be the happiest developer alive when this will be delivered. ;)