Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

textarea does not honour autosize when initial value is set via ngModel #4657

Closed
ghost opened this issue May 18, 2017 · 2 comments
Closed

textarea does not honour autosize when initial value is set via ngModel #4657

ghost opened this issue May 18, 2017 · 2 comments
Assignees
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@ghost
Copy link

ghost commented May 18, 2017

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).

@jelbourn jelbourn self-assigned this May 18, 2017
@jelbourn jelbourn added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label May 18, 2017
@StevenRasmussen
Copy link

Just ran into this. Any thoughts on a workaround?

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

2 participants