W3C home > Mailing lists > Public > public-pointer-events@w3.org > October to December 2012

[Bug 20281] New: Contact geometry should be in CSS pixels not device pixels

From: <bugzilla@jessica.w3.org>
Date: Fri, 07 Dec 2012 02:53:48 +0000
To: public-pointer-events@w3.org
Message-ID: <bug-20281-5978@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20281

            Bug ID: 20281
           Summary: Contact geometry should be in CSS pixels not device
                    pixels
    Classification: Unclassified
           Product: PointerEventsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Pointer Events specification
          Assignee: jrossi@microsoft.com
          Reporter: jrossi@microsoft.com
        QA Contact: public-pointer-events-bugzilla@w3.org
                CC: public-pointer-events@w3.org

Issue 1

Physical screen pixels may be ineffective. For example, the physical size of
the contact cannot be surmised due to varying pixel densities of devices (which
are not always reported by the user agent). Further, it is generally impossible
or difficult to correlate this back to CSS pixels in the document (which often
are not at a fixed ratio to screen pixels due to zoom).

I think the starting point should be that you can use the API to infer whether
a contact overlaps a particular element's bounding box. With device pixels,
this is difficult or impossible.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 7 December 2012 02:53:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:24 UTC