[TextareaAutosize] Deprecate TextareaAutosize

[oliviertassinari]

What's the problem? 🤔

Today's implementation of TextareaAutosize depends, more or less, on option 1 of https://stackoverflow.com/questions/454202/creating-a-textarea-with-auto-resize, it's more complex because it also supports maxRows and minRows.

Looking at https://github.com/tkent-google/explainers/blob/main/form-sizing.md, it looks like a native solution for this component is coming to the platform. Also see https://twitter.com/jh3yy/status/1710398436917321799.

It looks like we will no longer need this component in a year or two. Time to think of its deprecation path?

Search keywords:

Search keywords:

[colmtuite]

Auto-sizing is fine these days with field-sizing, but we discussed potentially recreating this component with <div contenteditable="true"> to support custom scrollbars. However, we can instead put the custom scrollbar on a parent and use :focus-within.

Demo: https://jsfiddle.net/as0r6evg

We can now deprecate this component.

[waigel]

I have concerns about backwards compatibility. The CSS property mentioned here is currently only available in a new chrome browser version. I don't think it's the right time to deprecate this now. Here is an overview of the support

https://caniuse.com/mdn-css_properties_field-sizing

[colmtuite]

Support is poor currently yes, but I was told by someone close with CSS that it's expected to be well-supported in the next few months, before our new Textarea component (following our new API design plans) would be roadmapped. So in terms of planning our v1 in late Q3 this year, it makes sense to think about the native implementation.

[oliviertassinari]

👍

• I added the deprecation label to be ready for the future.
• I have added the on hold label as we need to be compatible with the browser list we document. I guess we should have a single set of browsers we support. We are refreshing this list in [core] Update browser support versions #41568. I think we can use on hold label removal to signal when we are ready to implement the deprecation. I suspect that Safari will constrain us the most. From [material-ui] Update browser supports in v6 #40958 (comment), there seems to be a 24 months delay between a feature available in Safari and being able to use it broadly.

[oliviertassinari]

One thing I'm missing with the CSS only implementation: how's do we do max line count? Using max-height: px makes it hard to match line count, especially with different theme density. The results isn't that great.
I guess max-height: 10lh; this unit.

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.