Fix linkification not working for Spanned
strings in text messages
#3233
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.
Content
Make
CharSequence.withFixedURLSpans()
handle any type of CharSequence, not onlySpannable
. If the text wasn'tSpannable
, a new one will be created from it.Motivation and context
Previously, the RTE would always return a
SpannableString
as a result, and as the code checked forthis is Spannable
it worked fine.Now a
SpannedString
is returned instead (the result of abuildSpannedString { ... }
block), so the code was skipped.This issue was found as a regression after upgrading the RTE version to
2.37.7
in #3218.Tests
formatted_body
.Tested devices
Checklist