-
Notifications
You must be signed in to change notification settings - Fork 28.6k
Move updateSemantics from PlatformDispatcher to FlutterView #112221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@goderbauer what do you think the tests should look like for this? |
Do we have any tests covering PlatformDispatcher.updateSemantics? Those could be re-purposed, but with calling FlutterView.updateSemantics instead. I think ultimately, you want a test to ensure that any information passed to FlutterView.updateSemantics is forwarded properly to the embedder API and invokes the expected callbacks there, e.g. https://github.com/flutter/engine/blob/966f249fb132df0f91d326c022adaa0f8d52dd77/shell/platform/embedder/embedder.h#L1740 |
Reopening as flutter/engine#37388 reverted the issue that closed this. |
Fixed forward by #114857. Can close now that change is landed. |
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 |
In a multi view world we will be creating separate semantics trees for each view. For this, the
updateSemantics
should move from the singletonPlatformDispatcher
to the individualFlutterView
s.Once the framework has been moved over, the old
updateSemantics
on the PlatfromDispatcher can be removed.The text was updated successfully, but these errors were encountered: