sorry a typo in title, I mean if "tapped" very quickly

Tested the issue using #66.0.3359.158 on Android Micromax, 5.0.0 as per the steps mentioned below and could not reproduce the issue.

Steps:
1. Launched Browser
2. Navigated to https://codepen.io/anon/pen/mLZXvz
3. Clicked the green region quickly for several times
4. Observed pointerup results for all the clicks.

@kailali: Please find the observations and help us with the details of your device for further triaging of the issue?

Thanks!!

Hi there,

thanks for the reply.

I just tried it on two other android phones:

 - Samsung Galaxy S5, with chrome 66.0.3359.158, android 5.0.0; SM-G900F Build/LRX21T
 - motorola, with chrome 66.0.3359.158, android 5.1.0; XT1039 Build/LPBS23.13-17.3-1

in both cases I was able to reproduce the issue.
Please see also the screenshot attached.

I think you have to really tap it fast (like < 200ms interval).
Also would you please try it on other android devices (tablets/phones)? Since I tried it on 3 of my android devices and it's 100% reproducible.

Thanks and best regards,
Kailai

Deleted: Screenshot_2018-05-28-14-57-11.png 244 KB

	Screenshot_2018-05-28-14-57-11.png 244 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested the issue using #66.0.3359.156 on Samsung J7; 7.0.0 and reproduce the issue as per the steps mentioned below.

Steps:
1. Launched Browser
2. Navigated to https://codepen.io/anon/pen/mLZXvz
3. Clicked the green region quickly for several times
4. Observed pointerup results are dropping for clicks.

Observing the same behavior since M68. Untriaged for further inputs

Please navigate to below link for log's and screen cast and screenshot of the error --
go/chrome-androidlogs/846649 

Issue is seen in M69 as well

Thanks!!

I don't think your page is printing that "another pointerdown" with checking a correct condition.
Anyhow, I created another simpler page here:
https://output.jsbin.com/wekoyecexo

Pretty much just logs pointerdown and ups and delays in down handler.

Can you try this and see whether at all you see more than one pointerdown for the same id being printed when tapping with fingers?

Hi,

thanks for the reply.Sorry I didn't find a way to quote, so I'd just write it here.

"I don't think your page is printing that "another pointerdown" with checking a correct condition."

Would you please explain a bit further why that page doesn't achieve the testing purpose?
As I understand, there's just one more level of mapping: pointerID -> timerID, which is set in the pointerdown handler and then removed in the pointerup handler.

"Can you try this and see whether at all you see more than one pointerdown for the same id being printed when tapping with fingers?"

The answer would be yes: I still see multiple consecutive pointerdown events for the same IDs, see attached. Tested on:

Samsung Galaxy S5, with chrome 67.0.3396.68, android 5.0.0; SM-G900F Build/LRX21T

Deleted: Screenshot_2018-06-04-14-00-56.png 177 KB

	Screenshot_2018-06-04-14-00-56.png 177 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

btw I'm seeing similar behavior in the windows-chrome using devtool-touch-emulator. For example, in device mode, just with a fast double click I see:

pointerdown 2
pointerup 2
pointerdown 3

No pointerup for 3.
By the next click it shows:

pointerdown 3
pointerup 3

I'm not sure if this refers to the same problem as in android though.

Best Regards,
Kailai

Looks like a codePen problem to me.

#c8 above couldn't repro in jsbin.
I couldn't repro with this simpler version:
- Go to example.com.
- Run this code in console:
  function wasteTime(ms) {
    let d = new Date();
    while (((new Date()) - d) < ms) {}
  }
  ['pointerdown', 'pointerup', 'pointercancel'].forEach(e => {
    document.body.firstElementChild.addEventListener(e, evt => {
      console.log(evt.type, evt.pointerId);
      if (evt.type == "pointerdown") wasteTime(400);
    })
  });


On the other hand, editing the codepen to leave only the console logs reproduces the bug.

 kailai.wang@hotmail.com: please confirm if you can repro outside codepen.io.

Closing this for now as there wasn't any feedback from the reporter. Reporter if you happen to have feedback or further instructions feel free to come back here and comment or file a new bug.