It is not very clear what should be the region field for pointer events in some cases.
For touch events since the region is calculated on touchpressed there is a real node and we can figure out what the related region is if the node happens to be a canvas. After the the touch is captured to that node.

For pointer events there is another api to set the capture of the pointer event to a particular node that is not necessary in hit-testing of that pointer event. So I'm not sure what should be the region in that case. Any idea?

Rick, do you know what happened about the region field? Is that finalized? Should we try to incorporate that in the pointer events as well?

I'm not sure the current status - it's a canvas feature, so junov@ is the lead.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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

zino@ would you be able to add this feature for pointerevents as well?

nzolghadr@, Hi, unfortunately, I'm on a trip until this week. If this is an urgent issue(but its priority seems 3), it will be better for other people to follow-up. Otherwise, I'll check it after May 18. Thank you.