Pointer Events Pen support broken in Fall Creators Update

By design Issue #15008486


Geoff A.
Dec 7, 2017
This issue is public.
Found in
  • Microsoft Edge
Standard affected
Pointer Events

Found in build #
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

Using a Windows 10 Surface Pro (pre-fall update) vs a post-fall update Surface Pro, go to this page: https://codepen.io/girliemac/pen/inuxr

In the post-fall update device, Pointer Down and Pointer Up events aren’t fired at the appropriate times (i.e. when the pen touches the screen and leaves the screen).

It’s easy to write “Hello” on the image of the cat on the pre-fall update Surface Pro, and it’s quite difficult on the post-update machine. This is just an example scenario; I have a much more complex web app that previously worked with pen input, but it no longer works as I intended with pointer events.

Is this a bug or a "feature"? I’m asking because it’s a pretty significant QA miss for a bug. If it’s a "feature", could you point me to code examples for how I’m expected to interact with pen input going forward?


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “wptsixtri@microsoft.com”

      Changed Assigned To from “wptsixtri@microsoft.com” to “Andrew B.”

      Changed Assigned To to “Fei S.”

      Changed Assigned To from “Fei S.” to “Ryan B.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed”

      Changed Assigned To to “Sha V.”

      Changed Assigned To from “Sha V.” to “Leo B.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “By design”

    • Hi, thank you for reporting this issue!  In the Fall update the default action for pen was changed to scroll rather than fire pointer events, similar to the behavior for touch.


      I see on your Codepen that you’ve included the -ms-touch-action CSS property to control the default scrolling behavior, but not the unprefixed touch-action CSS property.  Including the unprefixed property should get the behavior you expect (both for touch and for pen).  The unprefixed property is supported in all versions of Edge as well as Chrome, Firefox, and IE11:



      In this Codepen it looks like you are expecting the same behavior for both touch and pen, so the touch-action property should be sufficient.  However, if you would like to have distinct behaviors for touch vs. pen (e.g. allow touch to scroll natively while pen draws with Pointer events) then “pen-action: none” can be used to request pointer events for pen input while leaving touch scrolling unaffected.

    • Hi Matt,

      Thanks for the suggestion - after adding pen-action: none to the element of my app, all is well again in Edge on the latest version of Windows 10.

      Is “pen-action” part of the Pointer Events standard? I’m having trouble finding documentation for it, and other browsers don’t seem to be aware of it.

    • I would also like to see documentation on pen-action. I’ve found nothing. We have clients wanting to use our web based drawing application on a Surface, and this new behavior is counter to all other comparable stylus inputs.

      How about an option to choose the desired behavior (scroll, or pointer events) for the end user?

    You need to sign in to your Microsoft account to add a comment.

    Sign in