So leaning to yes for your question :)

# compose

[Siyamed]

So leaning to yes for your question :)

[matvei]

Converting this to a thread 🙂

Yeah, what Siyamed said basically

[matvei]

But if people will find usefull to have separate Core and Base textfield apis -- we can leave them.

But for now my desire is to merge Base and Core testfields and make CoreTextfield offer custom cursor drawing with some reasonable default from BaseTextField

[matvei]

Because now BaseTextField = CoreTextField + private cursorModifier

[matvei]

And it's not a big reason to keep one separate APIs, imo 🙂

[Siyamed]

(maybe + some theming, not sure about it right now)

[matvei]

Oh right, thanks Siyamed. Also BaseTextField sets text color to contentColor, if provided by the parent

[Zach Klippenstein (he/him) [MOD]]

So if one were building custom components for a custom design system, they would probably still use BaseTextField? Unless the design system required something extreme like non-standard cursors, which is probably unlikely.

[Siyamed]

Yes

[matvei]

I have WIP CL where I was experimenting with this idea: https://android-review.googlesource.com/c/platform/frameworks/support/+/1372123

It's waaay far off from landing, if at all