[Webkit-unassigned] [Bug 139681] New: [GTK] Touch support is reported even when the device don't has a touch screen.

[bugzilla-daemon at webkit.org]

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

            Bug ID: 139681
           Summary: [GTK] Touch support is reported even when the device
                    don't has a touch screen.
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: Unspecified
               URL: http://people.igalia.com/clopez/checktouch.html
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: clopez at igalia.com
                CC: cgarcia at igalia.com, zandobersek at gmail.com

Hi,

WebKitGTK+ reports that it has touch capabilities support even when the device where it's running don't has such capabilities. My laptop don't has any touch support and on the following test I get reported that my device has a touch screen. http://people.igalia.com/clopez/checktouch.html

Both with Firefox=34 and Chromium=38 (Xorg) on the same device (my laptop) and on the same test I get reported that I have a normal screen device without touch support.

Ideally, WebKitGTK+ should check if the device where it runs has a touch screen device (not sure how to do this) and then report touch capabilities based on that.

This has caused for example that click events don't work on the JS plot library (Flotr2) <https://github.com/HumbleSoftware/Flotr2/pull/295>. This is a bug on that library since the user can still use a mouse even if her device has touch capabilities.

But I think that we should not report touch capabilities when the device where we run don't has that, otherwise from time to time some pages that assume that we are touch capable are going to break.

More info: https://hacks.mozilla.org/2013/04/detecting-touch-its-the-why-not-the-how/

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20141216/ef61d496/attachment-0002.html>