Api for read-only TextField [171040474]

Fixed

Bug

Status Update

No update yet.

Description

dm...@gmail.com

created issue #1

Oct 16, 2020 04:57PM

Jetpack Compose release version: 1.0.0-alpha05

OutlinedTextField and other text fields should have API to mark them as read-only/noneditable/disabled.

Noneditable field should follow material design guidlines [1] and shouldn't show keyboard when focused.

[1] https://material.io/components/text-fields#input-types

Comments

so...@google.com <so...@google.com> Oct 23, 2020 08:24AM

Status: Duplicate of

166478534

so...@google.com <so...@google.com> #2Nov 5, 2020 05:51PM

Status: Assigned (reopened)

There is a report about it in kotlinlang Slack: https://kotlinlang.slack.com/archives/C01D6HTPATV/p1706005056105739

so...@google.com <so...@google.com> #3Nov 5, 2020 06:00PM

Thanks for the report!

si...@google.com <si...@google.com> #4Nov 5, 2020 06:13PM

The release notes documentation has been edited to clarify this change in behavior for line height.

To support non-standard text sizes, we encourage users to follow the Material design system and use a different type scale rather than changing the font size directly. Alternatively, users can overwrite the line height like so: style = LocalTextStyle.current.copy(lineHeight = TextUnit.Unspecified), or create a custom Typography entirely.

si...@google.com <si...@google.com> #5Nov 5, 2020 06:30PM

deleted

ap...@google.com <ap...@google.com> #6Dec 24, 2020 07:47PM

In my case, I have multiple font sizes in the same Text (using SpanStyle in AnnotatedString). There are legitimate reasons for this. For example, when combining Chinese and English (phonetic) together (for language-learning purposes).

so...@google.com <so...@google.com> #7Dec 24, 2020 07:48PM

aosp/1534463 submitted.

Keeping this bug open to follow-up on scrolling behaviour in read-only text fields.

al...@gmail.com <al...@gmail.com> #8Dec 24, 2020 07:59PM

Amazing thank you for fixing!

so...@google.com <so...@google.com> #9Jan 27, 2021 09:14PM

Marked as fixed.

Marking this as fixed, there is internal bug to track the read-only scrolling behaviour.