Skip to content

Conversation

@nondebug
Copy link
Collaborator

@nondebug nondebug commented Mar 19, 2025

Closes #???

The following tasks have been completed:

  • Modified Web platform tests (link to pull request)

Implementation commitment:


Preview | Diff

@gabrielsanbrito gabrielsanbrito self-requested a review April 10, 2025 23:45
Copy link
Collaborator

@gabrielsanbrito gabrielsanbrito left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nondebug left a couple of comments. I think that the model section looks good!

Copy link
Collaborator

@gabrielsanbrito gabrielsanbrito left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the long delay. I gave it a last pass and I think that the model section looks good. Just added 2 comments, which are basically questions. Thanks for making it so detailed!

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we mention anything about the orientation of the y-axis?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should, since the current spec is ambiguous about which way is +Y. For other axes we define this in the normalization steps, let's do the same for touch coordinates.

@nondebug nondebug merged commit 2dcc97c into gh-pages Jun 12, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants