A lot of my users on http://www.anondraw.com seem to have this issue as well.
After a little bit of drawing, it stops working. I'm not sure how to trigger it from working to non-working though.

Disabling Windows Ink fixes it for my use case.

This is connected to the PointerEvent API implementation if I'm not mistaken. Any input device that declares pen pressure causes Chrome to emit a PointerEvent instead of a MouseEvent, thus any page interaction using the pen doesn't work at all (mouse interaction with buttons, page scrolling, drag/drop behaviour etc)

This is why on a Wacom, when you disable Windows Ink it works. Because Chrome no longer sees this as a pointerType === 'pen' but as a pointerType === 'mouse' causing to behave like a mouse and thus able to interact with the GUI like a mouse can.

A reliable repro case:

- Make sure Windows Ink is turned on
- Make sure you DO NOT move your mouse (not pen, your mouse)
- Go on this app (simple canvas drawing app)
- Draw with pen
- Move your mouse a little bit
- Try to draw again with pen

Result: Pen stops drawing once mouse is moved. 

Notes: It doesn't work on the Chrome level. I can't interact with ANY page, not just this app when the above scenario takes place.

Setup: Windows 10 Home v1607, Chrome v59.0.3071.115 (64bit), Wacom Intuos Tablet on driver version 6.3.22-6, Windows Ink setting turned on

Lan, do you have a wacom tablet for testing?

Yes, I can give to you anytime.

In case if it's of any help to other people, this is a terrible hack I've used to ameliorate a part of the problem: https://jsfiddle.net/ss0zshhr/. Of course for any non-trivial GUI interaction, this won't work (scrolling, HTML5 drag/drop etc)

Same issue with the Surface Pro using a Surface Pen obviously from the issue itself. Turning off Windows Ink isn't an option as it renders the Surface Pen useless. I tested this issue with 59 and realize the issue is gone in 61 (Dev and Canary), but is still present in 60 (Beta).

Use the same steps as the original poster to reproduce.

However, the issue for selecting text is still broken as of 59. I can confirm that install 58.x solves both selection and freezing problems.

Chrome 61 (Dev/Canary) only partly works. I agree that mousedown, mousemove, mouseup equivalent events work but at least text selection and HTML5 drag/drop still don't work.

Same here. Chrome freezes when I use the pen on my Surface Pro 4.

Same issues here for at least 2 weeks.

Same here since #59

Having the same problems here
-freezing pen on long clicks.
-can't drag or move items in google drive
-can't select text

Same issue here.
Surface Pro 2, Windows 8.1, Chrome Version 59.0.3071.115 (Official Build) (64-bit)
Was working fine in the past with the old stable versions of Chrome.
Please fix.

Surface Pen (Latest version) not working correctly on New Surface Pro using Chrome, which I just purchased for use by doctor in our office.  Problem occurred from start of using them in Windows 10.  Also same problem started happening all of a sudden on previous Samsung Tablet using Windows 8.1, after working for at least 6 months.

Same problem. Windows 10, Chrome Version 59.0.3071.115 (Official Build) (64-bit).
I use Wacom Bamboo and Graphire 3 tablets for disability/accessibility reasons, and I am a web developer. I can not use Chrome at all now. This is a major issue for me.

Same issue with Wacom Intuos 4 (PTK-640 A4 size) on macOS Sierra 10.12.6, Chrome Version 60.0.3112.78 (Official Build) (64-bit).

On macOS it started with Chrome 60. Some buttons like the Gmail buttons on mail.google.com (archive, delete, …) don't receive a click event. The button gets the blue highlight around it but never receives a click event.

Same thing happens with the tabs in the Chrome developer tools (Network, Performance, …).

Just tried the Chrome for macOS Beta Build Version 60.0.3112.78 (Official Build) beta (64-bit). This build seems to be working again.

It's not really working as expected.

The issue is a bit more complicated. To have Wacom Intuos Pen clicks registered by Google Chrome, the first click in a browser tab has to come from a second device like the magic mouse or a trackpad. After the first click, the Wacom tablet clicks are also registered. This is true for each separate browser tab. Very odd.

I'm on Mac OSX (Sierra - 10.12.6) and having Chrome 60.0.3112.90 (Official Build) (64-bit)

I notice I have this issue with my Wacom pen when I have my Developerstools panel open. When I hover over the elements, it's all working correctly. But when I adjust a value in the styles tab, the highlighting and clicking doesn't work anymore.

The only solution is pressing the touchpad on my Macbook and then the highlighting and such works again :(

Mac OSX (Yosemite 10.10.5)
WACOM Bamboo CRH-670, touch disabled

First noticed on Aug 15, 2017 with Chrome update 60.0.3112.90 (Official Build) (64-bit), did not have any issue before then.

There is no option to disable/adjust pressure, options are limited to: 
'Eraser Feer' (set to middle)
'Tip Feel' (set to middle)
'Pen Buttons' (set to 'switch application', and 'right click')
'Tracking' (mapping is set to a portion of the tablet)
'Double Click Distance' (set in the middle)

All standard links seem to work fine, but anything displayed as a button is driving me bonkers (very noticeable in Gmail and Basecamp)
 

I've opened  issue 757069  to track the issue observed in comments 22, 24, 25, 26 - I think they all report the same issue.

Exact the same problems.

"...when I have my Developerstools panel open..."
"... but anything displayed as a button is driving me..."

Hope this will be fixed.

Having issues as well with Drag and drop, Gmail, Docs, Invision

Developers are aiming to get the same experience on all devices Chromium is used. Is it so hard to undestand that I dont want to my PC acts and feels as a fracking mobile phone or tablet? Same stupiditi as in Unity and Gnome 3...

+1 having this issue using a bambooCTH-460 on Version 60.0.3112.113 (Official Build) (64-bit)OSX 10.11.16

Big deal for me as I have RSI / Mobility issues, so use a pen and tablet in preference to a mouse (which cause me significant physical pain)

Guys look at comment 27 in this thread, it's been fixed in  issue 757069  already. The fix will be released with Chrome 61 which is in beta right now.
https://bugs.chromium.org/p/chromium/issues/detail?id=757069

Middle click behavior is still broken, but there's also a fix already available. https://bugs.chromium.org/p/chromium/issues/detail?id=762095

Issue still persists in Chrome 62.0.3202.38 beta, cannot middle click with Surface Pro 2 (Wacom-based) stylus barrel button. Will register one out of a dozen times. I need to use a hacky and unreliable AutoHotkey script that captures and resends middle click to even be able to get any work done. :(