<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - TouchEvent objects shouldn't contain co-ordinates"
href="https://bugs.webkit.org/show_bug.cgi?id=157269#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - TouchEvent objects shouldn't contain co-ordinates"
href="https://bugs.webkit.org/show_bug.cgi?id=157269">bug 157269</a>
from <span class="vcard"><a class="email" href="mailto:rbyers@chromium.org" title="Rick Byers <rbyers@chromium.org>"> <span class="fn">Rick Byers</span></a>
</span></b>
<pre>I assume this is because pageX, pageY, layerX, layerY are on UIEvent.idl in WebKit (<a href="https://github.com/WebKit/webkit/blob/66e68cd8d7bf4ea1cf52f31ed9cb242f83ea5b57/Source/WebCore/dom/UIEvent.idl">https://github.com/WebKit/webkit/blob/66e68cd8d7bf4ea1cf52f31ed9cb242f83ea5b57/Source/WebCore/dom/UIEvent.idl</a>).
Chromium has never (AFAIK) reported non-zero values for TouchEvent.pageX/pageY/layerX/layerY, and we removed those properties from TouchEvent completely about a year ago (<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=50327">https://bugs.chromium.org/p/chromium/issues/detail?id=50327</a>).
We're not aware of a single website which is depending on seeing these properties on TouchEvents, so it's likely highly web compatible to move them from UIEvent to MouseEvent as we did in blink.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>