"Unable to test this issue on 62.0.3202.94 using Surface pro.

As TE-Hyd team doesn't have Two pens to check, could someone form MTV take a look into this issue.

Thanks!"

Lan was working on this at the time. If I recall correctly we were not able to correctly distinguish between two pens regarding the proximity event or something related. We had a heuristic in place but it caused the single pen scenario to fail in some cases. So we decided to let the multiple pen scenario slip as it is not going to be very popular anyway and instead have a better support for single pen for now until we get a better API from the platform.

s.ste...@weframe.com, do yo have a particular usecase in mind for multiple pen at the same time? Does that work on Edge?

Yes, we actually need this pretty badly. We have multiple sketching views, where we want to sketch at the same time and right now, as some pointer events are stuck because the pointerup event is not called, it really messes up our application. 
If I remember correctly this was working on Edge. 

Any chance, that this will be fixed in the next version?

Now would be a good timing as this issue https://bugs.chromium.org/p/chromium/issues/detail?id=851457&can=1&q=pointerup&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified is currently in progress ;-)

Lan would you be able to look at this one sometime?

I will work on it this week.

s.steinbach@weframe.com Could you please clarify that if you are using a surface book, and the two surface pens? Thank you.

I checked on Edge, it is same as Chrome. Both do not support two pens. It is not we do not fire a second pointerup. We cannot support two pens, and we do not even fire pointerdown for the second pen.

reporter, it seems that there are missing pieces in the platform API. On Windows none of the browsers would support such a thing and it seems that Windows APIs don't give us all the information. On Mac we also see the same issues with some information missing that we are not able to distinguish the two pen very well.

What app are you using that works with multiple pen?
I put as P3 as there are missing platform APIs for this feature. Maybe when the use case of multiple pen becomes more popular Mac and Windows also fix their APIs for that.

Actually I've just tested it again and on Windows even in Internet Explorer when I do the following:

1. open codepen example https://codepen.io/ssteinbach/pen/BmELZK
2. use two pens and put one pen on the first div and the second one on the second div (hold both pens)
3. release the first one : you can see that pointer up is fired
4. release the second one: you can see, that pointer up event is fired

So at step 4 the pointer event in internet explorer will be fired but in chrome not. 
Please check again!

Hey there, any update on this? It's really a big issue for us: if two persons are interacting at the same time with a pen and run into this issue suddenly no pointerup event is fired anymore. That makes our application unusable until we reload the whole page, which is not even possible for the user as we run our application in kiosk mode.
Would be really great if you had any idea.
Thanks!

I've just tested, that this behavior is not just on our application. I can reproduce the same error behavior on a normal page like google if I'm using two pens at the same time at any point on the site. If I for example search for youtube on google and then press two pens down, release the first one first and after that the second one, I can't open any search result until I press the two pens down again, release the second one first this time. Maybe this makes the issue a little more interesting for you ;-)
Thanks again.

We really want to fix this issue, but what we saw is that when we press the first pen, we cannot even use the second pen, so there is no pointdown for the second pen, of course no pointerup.

If you can provide what machine you are using, like surface book, what pen you are using, two surface pens? Also if you can record the page you are testing, that will be very helpful, thank you.

Sure! We use a PC with Microsoft Windows 10 Enterprise 2016 LTSB and FlatFrog Touch 'P-Series'. Currently you can find the FlatFrog Touch in the following products:

https://www.dell.com/en-us/work/shop/accessories/apd/210-alwv
http://www.newline-interactive.com/en/product-199148/TRUTOUCH-X-series.html
https://home.smarttech.com/interactive-displays-for-business/7000-pro-series
https://www.prometheanworld.com/products/interactive-flat-panels/activpanel

The FlatFrog Touch works with a simple wooden pen.
Thank you!

I see, we thought you are using stylus, but apparently you are using touch screen. could you please try to use your fingers, does it work the same as when you use two pens?

So can you also interact with your page with fingers? Do they work fine? or is it only happening with you use a pen? I assume when you are saying a wooden pen that means it has no electronic functionality. Right? Like a pencil?

It's just happening on the pointer events which are only fired by the pen, which has no electronic functionality. With fingers and therefore normal touch events we don't have any issues. You can also interact perfectly with the pen but not with two pens at the same time in the wrong order. 

We do not have the device you are using to test. Could you provide more information, like printing the pointer events' pointerType to see if they are pen or touch. We normally set pointertype to pen it is a digital stylus.

It's pen. And it's just happening if it's a pen, with touch we have no problems no matter how many fingers we use :-)

Hey guys! Any update on this? Please let me know, if you need any more information.

We do not have the device at the moment. We are in the process of getting one. But there is no ETA yet. 
Do you mind checking with Edge again and see if that works for you on their browser. Just trying to find a workaround for you until we get this issue resolved.

At least on Internet Explorer it worked perfectly. Two pointerEvents down, two pointerEvents up.

Could you please print out the id for the two pointer down events to help us debug, thank you.

You mean the pointerId? I'm not sure, how this will help, but in the test case now the pointer Id was 2 and from the second one 3. I've also attached the output to help debugging.

Deleted: pen_1.png 75.3 KB

	pen_1.png 75.3 KB View Download

Deleted: pen_2.png 81.7 KB

	pen_2.png 81.7 KB View Download

hey guys! any progress?

Our smartboard does not have pens, we have ordered two. Once we have everything ready, we will test it and update the result we find.