[CP-stable] Remove TextEditingController private member access (#149042)
#149208
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.
Manual request (merge conflicts in the test file) for cherry-picking #149042 to stable
Issue Link:
What is the link to the issue this cherry-pick is addressing?
#148692
Changelog Description:
Explain this cherry pick in one line that is accessible to most Flutter developers. See best practices for examples
Fixes an
EditableTextcrash that happens with a customTextEditingControllerwhich onlyimplementstheTextEditingControllerinterface.Impact Description:
What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping production app (the app crashes on launch)
Production apps crash if the user gives an
EditableTexta customTextEditingControllorclass thatimplements TextEditingControllor.Workaround:
Is there a workaround for this issue?
The crash does not happen if the user
extends TextEditingControllor, but it's not always desirable / feasible. The class could be already extending a different base class.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?
Run the test in the PR, or follow the repro steps in #148692