Trigger pointer leave when active controller switched #36662
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
facebook-github-bot
added
CLA Signed
|
This pull request was exported from Phabricator. Differential Revision: D44377324 |
genkikondo
added a commit
to genkikondo/react-native
that referenced
this pull request
Mar 27, 2023
Summary: Pull Request resolved: facebook#36662 For VR, JSPointerDispatcher skips calculating the delta of hit targets (which happens in onMove) on the frame in which the active controller is switched because the motion event is a DOWN event, not a MOVE event in that specific frame. This diff fixes the issue by just calling onMove in addition to onDown for DOWN motion events. Unfortunately we do not have separate pointer IDs for each controller. This won't change the behavior for non-hoverable pointers. For hoverable pointers, it will dispatch an extra pointer_enter if the hit path has changed between the last move event and the down event. Changelog: [Internal][Fixed] - Trigger pointer leave when active controller switched Reviewed By: lunaleaps, javache Differential Revision: D44377324 fbshipit-source-id: 305ba766d5b8324b312a6607086dbfb7b0d6622b
genkikondo
force-pushed
the
export-D44377324
branch
from
e7f0967
to
a83a2b6
Compare
|
This pull request was exported from Phabricator. Differential Revision: D44377324 |
1 similar comment
|
This pull request was exported from Phabricator. Differential Revision: D44377324 |
genkikondo
added a commit
to genkikondo/react-native
that referenced
this pull request
Mar 27, 2023
Summary: Pull Request resolved: facebook#36662 For VR, JSPointerDispatcher skips calculating the delta of hit targets (which happens in onMove) on the frame in which the active controller is switched because the motion event is a DOWN event, not a MOVE event in that specific frame. This diff fixes the issue by just calling onMove in addition to onDown for DOWN motion events. Unfortunately we do not have separate pointer IDs for each controller. This won't change the behavior for non-hoverable pointers. For hoverable pointers, it will dispatch an extra pointer_enter if the hit path has changed between the last move event and the down event. Changelog: [Internal][Fixed] - Trigger pointer leave when active controller switched Reviewed By: lunaleaps, javache Differential Revision: D44377324 fbshipit-source-id: 948fb862075ab24f078e5cb2a0e7a8de1641ae13
genkikondo
force-pushed
the
export-D44377324
branch
from
a83a2b6
to
7edd22f
Compare
Summary: Pull Request resolved: facebook#36662 For VR, JSPointerDispatcher skips calculating the delta of hit targets (which happens in onMove) on the frame in which the active controller is switched because the motion event is a DOWN event, not a MOVE event in that specific frame. This diff fixes the issue by just calling onMove in addition to onDown for DOWN motion events. Unfortunately we do not have separate pointer IDs for each controller. This won't change the behavior for non-hoverable pointers. For hoverable pointers, it will dispatch an extra pointer_enter if the hit path has changed between the last move event and the down event. Changelog: [Internal][Fixed] - Trigger pointer leave when active controller switched Reviewed By: lunaleaps, javache Differential Revision: D44377324 fbshipit-source-id: 001ba36cce7b545643b700e0ad89075e05288619
|
This pull request was exported from Phabricator. Differential Revision: D44377324 |
genkikondo
force-pushed
the
export-D44377324
branch
from
7edd22f
to
d6cc198
Compare
Base commit: 406f9fc |
|
This pull request has been merged in 3361290. |
jeongshin
pushed a commit
to jeongshin/react-native
that referenced
this pull request
May 7, 2023
Summary: Pull Request resolved: facebook#36662 For VR, JSPointerDispatcher skips calculating the delta of hit targets (which happens in onMove) on the frame in which the active controller is switched because the motion event is a DOWN event, not a MOVE event in that specific frame. This diff fixes the issue by just calling onMove in addition to onDown for DOWN motion events. Unfortunately we do not have separate pointer IDs for each controller. This won't change the behavior for non-hoverable pointers. For hoverable pointers, it will dispatch an extra pointer_enter if the hit path has changed between the last move event and the down event. Changelog: [Internal][Fixed] - Trigger pointer leave when active controller switched Reviewed By: lunaleaps, javache Differential Revision: D44377324 fbshipit-source-id: 9f668e64f486b9a12ab36563ec2b7cf93f208a54
OlimpiaZurek
pushed a commit
to OlimpiaZurek/react-native
that referenced
this pull request
May 22, 2023
Summary: Pull Request resolved: facebook#36662 For VR, JSPointerDispatcher skips calculating the delta of hit targets (which happens in onMove) on the frame in which the active controller is switched because the motion event is a DOWN event, not a MOVE event in that specific frame. This diff fixes the issue by just calling onMove in addition to onDown for DOWN motion events. Unfortunately we do not have separate pointer IDs for each controller. This won't change the behavior for non-hoverable pointers. For hoverable pointers, it will dispatch an extra pointer_enter if the hit path has changed between the last move event and the down event. Changelog: [Internal][Fixed] - Trigger pointer leave when active controller switched Reviewed By: lunaleaps, javache Differential Revision: D44377324 fbshipit-source-id: 9f668e64f486b9a12ab36563ec2b7cf93f208a54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
For VR, JSPointerDispatcher skips calculating the delta of hit targets (which happens in onMove) on the frame in which the active controller is switched because the motion event is a DOWN event, not a MOVE event in that specific frame.
This diff fixes the issue by just calling onMove in addition to onDown for DOWN motion events. Unfortunately we do not have separate pointer IDs for each controller.
This won't change the behavior for non-hoverable pointers. For hoverable pointers, it will dispatch an extra pointer_enter if the hit path has changed between the last move event and the down event.
Changelog:
[Internal][Fixed] - Trigger pointer leave when active controller switched
Reviewed By: lunaleaps, javache
Differential Revision: D44377324