You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Move updateSemantics from PlatformDispatcher to FlutterView #112221
In a multi view world we will be creating separate semantics trees for each view. For this, the updateSemantics should move from the singleton PlatformDispatcher to the individual FlutterViews.
Once the framework has been moved over, the old updateSemantics on the PlatfromDispatcher can be removed.
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 doctor -v and a minimal reproduction of the issue.
Activity
a-wallen commentedon Oct 6, 2022
@goderbauer what do you think the tests should look like for this?
goderbauer commentedon Oct 6, 2022
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
a-wallen commentedon Nov 7, 2022
Reopening as flutter-team-archive/engine#37388 reverted the issue that closed this.
a-wallen commentedon Nov 18, 2022
Fixed forward by #114857. Can close now that change is landed.
github-actions commentedon Dec 2, 2022
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 doctor -vand a minimal reproduction of the issue.