Maximum Width should be applied to the Text Area in the Report Section
See original GitHub issueDescribe the bug On expanding the Text Area in the report section , there should be certain maximum limit .
To Reproduce
- Go to https://voice.mozilla.org/en/speak
- Click the report button in the bottom
- Check the
Other
checkbox - Expand the Text Area
** Expected behavior** There should be a certain maximum width to write the report .
Additional Behaviour @phirework @MichaelKohler Let me know, I would like to work on it.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Maximum Width should be applied to the Text Area in ... - GitHub
Go to https://voice.mozilla.org/en/speak · Click the report button in the bottom · Check the Other checkbox · Expand the Text Area.
Read more >max-width - CSS: Cascading Style Sheets - MDN Web Docs
The max-width CSS property sets the maximum width of an element. It prevents the used value of the width property from becoming larger...
Read more >Rich Text Area Field Limitations - Salesforce Help
The maximum character limit for long text area and rich text area fields is 131,072 (128 KB). The minimum character limit is 256....
Read more >javascript - Text from textarea to div with limited width and height
For example: I have a div width 100px and max height 100px. I need to enter text in textarea and this text will...
Read more >CSS max-width property - W3Schools
The max-width property defines the maximum width of an element. If the content is larger than the maximum width, it will automatically change...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’d say so. There is a small chance there is a reason not to do that, but in the end I’d say this makes sense. However, please don’t be mad at me if this ends up not being wanted 😃
Solved in #2604