Re: [w3c/gamepad] Integrate with WebDriver and WebDriver BiDi for automation (PR #224)

@sadym-chromium commented on this pull request.



> +        A [=gamepad=] may have [=touch surfaces=]. A <dfn>touch surface</dfn>
+        is an input control that provides 2D position data representing points
+        of contact. A [=gamepad=] has a <dfn>touch surface list</dfn> which is
+        a [=list=] containing the [=touch surfaces=] for the [=gamepad=]. The
+        list is ordered such that [=touch surfaces=] closer to the left side of
+        the [=gamepad=] appear closer to the start of the list.
+      </p>
+      <p>
+        A [=touch surface=] has an <dfn>active touch point list</dfn> [=input
+        value=], a [=list=] of zero or more [=touch points=] representing the
+        points of contact currently detected by the sensor. A <dfn>touch
+        point</dfn> represents a single point of contact at a single point in
+        time. A [=touch point=] has a <dfn>touch x coordinate</dfn>
+        and a <dfn>touch y coordinate</dfn> representing the position in the [=touch surface=]'s coordinate system.
+        If a [=touch surface=] is on the top, bottom, front, or back side of the [=gamepad=] then the [=touch x coordinate=] is measured along the left-right axis, otherwise it is measured along the top-bottom axis.
+        The [=touch y coordinate=] is measured along the perpendicular axis.

NIT: should we define the specific orientation of the the perpendicular axis?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/pull/224#pullrequestreview-3252032271
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/pull/224/review/3252032271@github.com>