Verified
Status Update
Comments
si...@google.com <si...@google.com> #2
bulk comment, fyi: we have added icebox to all the tickets because it was suggested by blintz in order to prevent auto-close tickets. we want to keep our Compose tickets to remain opened.
see b/123001228#comment6
see
si...@google.com <si...@google.com>
si...@google.com <si...@google.com>
ha...@google.com <ha...@google.com>
ap...@google.com <ap...@google.com> #3
ha...@google.com <ha...@google.com>
ap...@google.com <ap...@google.com> #4
redacted
ex...@gmail.com <ex...@gmail.com> #5
Nevermind. Sorry about my last comment. Thanks for making me realize the bug is public. I'll share it with partners to gauge their interest through their +1s.
ha...@google.com <ha...@google.com> #6
Is there any progress on this issue?
ex...@gmail.com <ex...@gmail.com> #7
According to [¡a conversation from the Compose slack channel on May 2021(see
Now that the support for downloadable fonts in Compose is fixed (April 2022), what is the state of the Emoji compatibility in Compose?
ex...@gmail.com <ex...@gmail.com> #8
Yep, static text integration is unblocked.
Editable text will take more work.
ha...@google.com <ha...@google.com> #9
Doing planning now, will take comment as a vote for priority :)
Description
AS Canary 13, beta04
There are some inconsistencies when
Text
parameters are combined with anAnnotatedString
input. In the example below (see screenshot as well) thefontSize
,textDecoration
,color
, andletterSpacing
parameters ofText
are applied to the whole annotated text, but thefontStyle
andfontFamily
parameters are not. I expected "World" to display as bold, italic and monospace.Note also how
textDecoration = TextDecoration.LineThrough
from the annotated string andTextDecoration.Underline
on theText
combine, which seems reasonable, until you consider attributes likecolor
, which override:color
specified in annotated text overrides the parametercolor
inText
for the annotated portion, as expected (not shown in example).