[CP-stable]Refactor route focus node creation#149378
Conversation
## Description This fixes an issue in the creation of the `FocusScope` in a route: the route should be creating the `FocusScope` widget it has with `withExternalFocusNode`, since it is modifying the node attributes in a builder. Also modified some `AnimatedBuilder`s to be `ListenableBuilder`s, since they're not using animations (no functionality change there, since the implementation of the two is identical). ## Related Issues - flutter#147256 - Fixes flutter#146844 ## Tests - Updated example test.
|
@jmagman please fill out the PR description above, afterwards the release team will review this request. |
|
@chunhtai or @gspencergoog can you fill out this cherry-pick PR description? There didn't seem to be any follow-up to #149178 (comment). For future reference, the cherry-pick automated process with labels is at: |
|
@itsjustkevin heads up this was merged instead of going through the release team process. |
|
@jmagman @itsjustkevin should #149178 now get closed? |
|
|
Hi flutter team, what's required next? how long does it usually take after the merge of CP-stable to release a stable hotfix version of Flutter? (3.22.2?) |
Stable 3.22.2 is now out |
| AnimatedBuilder( | ||
| animation: widget.route.navigator?.userGestureInProgressNotifier ?? ValueNotifier<bool>(false), | ||
| ListenableBuilder( | ||
| listenable: widget.route.navigator?.userGestureInProgressNotifier ?? ValueNotifier<bool>(false), |
There was a problem hiding this comment.
Hi, do we need to dispose ValueNotifier<bool>(false),?
|
Hi @quyenlv-unicloud, if you are running into problems, please create a new issue referencing this PR over commenting. |

Issue Link:
#148867
Cherry-picking #147390
Changelog Description:
Fixes a focus issue that causes TextFields to not function after cupertino back swipes
Impact Description:
iOS, macos, iOS web, macos web app that uses TextField
Workaround:
disable cupertino back swipe
Risk:
What is the risk level of this cherry-pick?
Test Coverage:
Are you confident that your fix is well-tested by automated tests?
Validation Steps:
What are the steps to validate that this fix works?
TextField should not be broken after a cupertino back swipe