-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
p-textarea resize bug when used in an overlay + tabs #7000
Labels
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
Milestone
Comments
stevenvanryckeghem
changed the title
p-textarea resize bug when used in an overlay
p-textarea resize bug when used in an overlay + tabs
Dec 14, 2018
+1 |
2 similar comments
+1 |
+1 |
cagataycivici
added
the
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
label
Jan 7, 2019
I'm seeing this exact problem. I am using primeng11.0.0-rc.1 and angular 11. Has this bug been reintroduced or am I doing something stupid? I have a textarea with autoResize="autoResize" in a tab. When the tab is opened, it has height: 0px. When I click into the field, it resizes correctly. This code demonstrates my problem...
|
Not fixed yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
I'm submitting a ... (check one with "x")
Plunkr Case (Bug Reports)
https://stackblitz.com/edit/primeng-autoresize-textarea-bug
Current behavior
The textarea gets "height: 0px"
If you remove the "autoResize" attribute, the bug doesn't manifest.
The same bug appears when the textarea is in a tab (and you switch tabs)
Expected behavior
The textarea doesn't resize to 0px height...
What is the motivation / use case for changing the behavior?
To have a bugfree PrimeNG :)
Please tell us about your environment:
Angular version: 7.X
PrimeNG version: 7.X
Browser:
Latest Chrome + Firefox
The text was updated successfully, but these errors were encountered: