Skip to content

Conversation

@khaykov
Copy link
Contributor

@khaykov khaykov commented Feb 17, 2025

Not sure how to reproduce the issue, but sometimes spans that we reset might return -1 for start and end position. I suspect that service spans (like selection, etc) might be causing this.

This PR protects against this case.

We do not have a test case for copying texts in the demo app, so please test this with the client version that is utilizing it.

  • If there are new strings that have to be translated, I have added them to the client's strings.xml as a part of the integration PR.

@khaykov khaykov requested review from danilo04 and zwarm February 17, 2025 21:45
@khaykov khaykov added the bug label Feb 17, 2025
@zwarm zwarm self-assigned this Feb 18, 2025
Copy link
Contributor

@zwarm zwarm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@khaykov - Nice solution. LGTM :shipit:

@zwarm zwarm merged commit fc32c7f into trunk Feb 18, 2025
14 checks passed
@zwarm zwarm deleted the issue/ensure-valid-spans-when-getting-text-copy branch February 18, 2025 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants