Fix: SfNumericEntry substring issue in iOS and MacCatalyst with VoiceOver and AllowNull#354
Merged
Merged
Conversation
…Over and AllowNull
Chozarajan-P
approved these changes
May 6, 2026
Collaborator
Chozarajan-P
left a comment
There was a problem hiding this comment.
The changes are fine
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
This PR introduces a check on the validity of a SubString range before returning, fixing an ArgumentOutOfRangeException where these values do not correctly reflect the situation.
Root Cause of the Issue
In VoiceOver the text gets automatically deselected shortly after activating. The corresponding SelectionLength is not updated correctly. When this value is then used for a substring a crash occurs, as it becomes out-of-bound.
Description of Change
A check to ensure the substring value is within range. If not an empty string is returned, which is then handled by existing logic.
Issues Fixed
Fixes #324