Repository navigation
fix: avoid unsafe iOS keyboard dismissal - #957
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Closes #952.
The dismiss-control search intentionally checks matching buttons beyond
app.toolbars.buttonsbecause iOS 26 may expose keyboard-accessoryDonecontrols outside aUIToolbar. It remains bounded by exact safe labels and keyboard-accessory geometry, so it can tap a nearby dismiss control without falling back to input-mutating gestures or raw coordinates.Touched files: 8. Scope stayed within iOS runner keyboard behavior plus related help/docs/tests.
Validation