You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I have a textarea with "mdTextareaAutosize" and a bound "ngModel", the textarea doesn't seem to size to the initial data. Once you change anything inside the textarea, it will start autosizing.
What is the expected behavior?
When page loads, textarea should be sized appropriate to data.
What is the use-case or motivation for changing an existing behavior?
Applications that have dynamic data in text areas that needs to be autosized on load.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
I have only tested in Chromium 58 on Linux. For Angular, it looks like your plunker template uses 4.1.3, but in the application I discovered it, we're using 4.0.0. Typescript is 2.2.1. Material is 2.0.0-beta.2 (although your plunker uses 2.0.0-beta.5).
The text was updated successfully, but these errors were encountered:
Bug, feature request, or proposal:
When I have a textarea with "mdTextareaAutosize" and a bound "ngModel", the textarea doesn't seem to size to the initial data. Once you change anything inside the textarea, it will start autosizing.
What is the expected behavior?
When page loads, textarea should be sized appropriate to data.
What is the current behavior?
When page loads, textarea is not sized.
What are the steps to reproduce?
http://plnkr.co/edit/D9ZmsmhRMNc2rjXkmVXv?p=preview
What is the use-case or motivation for changing an existing behavior?
Applications that have dynamic data in text areas that needs to be autosized on load.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
I have only tested in Chromium 58 on Linux. For Angular, it looks like your plunker template uses 4.1.3, but in the application I discovered it, we're using 4.0.0. Typescript is 2.2.1. Material is 2.0.0-beta.2 (although your plunker uses 2.0.0-beta.5).
The text was updated successfully, but these errors were encountered: