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
Describe the bug
The discussion note feature on patient dashboard has a field at the bottom to input text. This is where the user will be typing in relevant content to post of discussion notes.
When I type in the content, the text input field only shows a maximum of two lines of text due to limited height of the field. As I type in larger text content, only the last two lines are visible to me at any point.
However, if I copy paste large text content into the text field, the text field height is increased to allow me to view the content better
This dynamic adjustment of height must happen even when a user types in content.
You will see that the height of the text field does not increase.
Expected behavior
Height of text input field in discussion note must increase as the size of the content therein increases. the height may be capped at 7 lines as seen in the second screenshot above.
The text was updated successfully, but these errors were encountered:
Describe the bug
The discussion note feature on patient dashboard has a field at the bottom to input text. This is where the user will be typing in relevant content to post of discussion notes.
When I type in the content, the text input field only shows a maximum of two lines of text due to limited height of the field. As I type in larger text content, only the last two lines are visible to me at any point.
However, if I copy paste large text content into the text field, the text field height is increased to allow me to view the content better
This dynamic adjustment of height must happen even when a user types in content.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Height of text input field in discussion note must increase as the size of the content therein increases. the height may be capped at 7 lines as seen in the second screenshot above.
The text was updated successfully, but these errors were encountered: