fix: correct the clientX and clientY of touch sensor events

[zjffun]

This will bring a breaking change! Because it will change the clientX and clientY of each SensorEvent triggered by touchs.

This PR fixes the clientX and clientY of the touch sensor events.

This PR closes the following issues... (if applicable)

No

Does this PR require the Docs to be updated?

No

Does this PR require new tests?

Yes

This branch been tested on... (click all that apply / add new items)

Browsers:

• Chrome version
• Firefox version
• Safari version
• IE / Edge version
• iOS Browser version
• Android Browser version

[zjffun]

It was written this way from the beginning. Is there any compatibility reason to use page instead of client? @tsov

[bahung1221]

Hi @zjffun , @tsov .
How about this PR? I tried it and it seems everything worked fine.

In my opinion, page and client coordinate only used to calculate internal state of draggable instance and some internal plugins. So for users, I think it won't create a breaking change 😄 Of course, we must test it carefully.

And based on zjffun PR, we can see that change from Page to Client will remove some redundant calculation (Mirror Plugin, Scrollable Plugin).

If we don't have any compatibility reason to use page instead of client, I think we should consider this PR 🤔

[zjffun]

@bahung1221

Thanks for your review.

It seems that touchEvent.clientX/clientY does have some bugs like https://bugs.webkit.org/show_bug.cgi?id=181954 , I will try when I have time.

---

A very old bug of touchEvent.clientX/clientY

• https://stackoverflow.com/questions/5885808/includes-touch-events-clientx-y-scrolling-or-not
• https://stackoverflow.com/questions/13710610/whats-a-workaround-for-chrome-for-androids-incorrect-clientx-and-clienty-behav
• https://gist.github.com/gregersrygg/3828586

seems fixed

• https://bugs.webkit.org/show_bug.cgi?id=101800

[zjffun]

It seems that using client and page - scroll has the same effect. https://codepen.io/1010543618/pen/bGpqwqm

Both of them have the little bug that should fix by webkit when dragging and scrolling.