[iOS] Fixed Entry with IsPassword toggling loses previously entered text #30572
+18
−1
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.
Note
Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!
Root Cause:
When toggling the IsPassword property, the UpdateIsPassword method does not properly preserve and restore the current text after toggling.
Description of Change
Modified the UpdateIsPassword method in TextFieldExtensions to temporarily suppress the TextPropertySet event while clearing and reinserting the text for password fields. This ensures the text update does not trigger unintended side effects.
Issues Fixed
Fixes #30085
Tested the behaviour in the following platforms
Screen.Recording.2025-07-11.at.5.11.32.PM.mov
Screen.Recording.2025-07-11.at.5.09.20.PM.mov