<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Touch support is reported even when the device doesn't have a touch screen"
href="https://bugs.webkit.org/show_bug.cgi?id=139681#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Touch support is reported even when the device doesn't have a touch screen"
href="https://bugs.webkit.org/show_bug.cgi?id=139681">bug 139681</a>
from <span class="vcard"><a class="email" href="mailto:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>It's sad but I'm afraid the touch events support is breaking more sites than what it fixes. I've found today some jquery elements that use "ontouchstart" in document.documentElement to decide whether to add listeners for mouse events or not. I agree that's wrong, because it's also assuming that if you have a touch input device you can't use any other non touch devices (like having a laptop with a touch screen and a usb mouse, which is my case). But unfortunately this wrong way is more and more common, so the only thing I can think of is disabling touch events support by default. People building for an embedded device with touch capabilities could enable it. My main concern is that we won't test it anymore. Another option could be making it a runtime feature that WTR can enable, like my patch tried to do but without enabling/disabling it automatically.</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>