[Webkit-unassigned] [Bug 35691] [Chromium] Adding new platform types for touch events and touch points.

[bugzilla-daemon at webkit.org]

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


Darin Fisher (:fishd, Google) <fishd at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
         AssignedTo|webkit-unassigned at lists.web |gdk at chromium.org
                   |kit.org                     |
     Ever Confirmed|0                           |1




--- Comment #6 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2010-03-03 15:34:21 PST ---
What it the use case for StateUndefined if not to terminate the array?  Can you
have a WebTouchPoint that is undefined and have the other fields contain
meaningful data?  It is OK to have the terminator be optional.  All fields
could contain data, or some of them could contain StateUndefined to indicate
that they are unused.  Maybe that is less clear though.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.