Synthesize gesture events in hybrid mode on Android #58837
Assignees
Labels
a: platform-views
Embedding Android/iOS views in Flutter apps
customer: product
engine
flutter/engine repository. See also e: labels.
P0
Critical issues such as a build break or regression
platform-android
Android applications specifically
Milestone
Comments
zanderso
added
a: platform-views
|
@iskakaushik has context on the relevant subsystem and has agreed to investigate but will have limited availability this week. |
|
I believe flutter/engine#19484 is related to this effort. @iskakaushik Is that correct? |
|
@chinmaygarde yup. I've landed flutter/engine#19427 and flutter/engine#19482 which lay the ground work. flutter/engine#19484 and adding tests should help us close this issue. |
This was referenced Jul 6, 2020
iskakaushik
pushed a commit
to iskakaushik/engine
that referenced
this issue
Jul 6, 2020
This change makes it so that we track all the motion events encountered by `FlutterView` and all of its subviews in the `MotionEventTracker` class, indexed by a unique `MotionEventId`. This identifier is then passed to the Flutter framework as seen in flutter/flutter#60930. Once the gestures take part in gesture disambiguation and are sent back to the engine, we look-up the original motion event using the `MotionEventId` and dispatch it to the platform. Bug: flutter/flutter#58837
iskakaushik
pushed a commit
to iskakaushik/engine
that referenced
this issue
Jul 7, 2020
This change makes it so that we track all the motion events encountered by `FlutterView` and all of its subviews in the `MotionEventTracker` class, indexed by a unique `MotionEventId`. This identifier is then passed to the Flutter framework as seen in flutter/flutter#60930. Once the gestures take part in gesture disambiguation and are sent back to the engine, we look-up the original motion event using the `MotionEventId` and dispatch it to the platform. Bug: flutter/flutter#58837
iskakaushik
added a commit
to flutter/engine
that referenced
this issue
Jul 7, 2020
This change makes it so that we track all the motion events encountered by `FlutterView` and all of its subviews in the `MotionEventTracker` class, indexed by a unique `MotionEventId`. This identifier is then passed to the Flutter framework as seen in flutter/flutter#60930. Once the gestures take part in gesture disambiguation and are sent back to the engine, we look-up the original motion event using the `MotionEventId` and dispatch it to the platform. Bug: flutter/flutter#58837
|
fixed in #60930 |
justinmc
pushed a commit
to justinmc/engine
that referenced
this issue
Jul 7, 2020
) This change makes it so that we track all the motion events encountered by `FlutterView` and all of its subviews in the `MotionEventTracker` class, indexed by a unique `MotionEventId`. This identifier is then passed to the Flutter framework as seen in flutter/flutter#60930. Once the gestures take part in gesture disambiguation and are sent back to the engine, we look-up the original motion event using the `MotionEventId` and dispatch it to the platform. Bug: flutter/flutter#58837
|
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
flutter-triage-bot
bot
added
the
P0
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is required to forward events to an
android.view.Viewafter the framework has decided that the platform view owns the events.The logic used in virtual displays can be reused to achieve this behavior in hybrid mode. Currently, this involves sending a message over a platform channel to the framework with the event metadata, then the framework forwards the event back to the platform. Finally, the embedding replays the event in the target Android view.
The text was updated successfully, but these errors were encountered: