<textarea> and <pre> are not aligned when a width is set
See original GitHub issueTestcase: http://codepen.io/fcicileo/pen/LWrGwE
It appears that when the container has a specific width set via CSS, the code in the <textarea>
and the <pre>
is not aligned anymore.
Issue Analytics
- State:
- Created 6 years ago
- Comments:19 (7 by maintainers)
Top Results From Across the Web
Textarea width does not align with the containing div
The problem with this is that when you set the width property on an element, you're only setting the content width, not the...
Read more >The Textarea element - HTML: HyperText Markup Language
The visible width of the text control, in average character widths. If it is specified, it must be a positive integer. If it...
Read more >Element: <oj-text-area> - Oracle
Autofocus is a Boolean that reflects the autofocus attribute, If it is set to true then the associated component will get input focus...
Read more >CSS · Bootstrap
Bootstrap sets basic global display, typography, and link styles. ... (fixed-width) or .container-fluid (full-width) for proper alignment and padding.
Read more >TextArea QML Type | Qt Quick Controls 1 5.15.12
Sets the alignment of the text within the TextArea item's width. ... Qt.ImhSensitiveData - Typed text should not be stored by the active...
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 Free
Top 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
Thanks very much for your persistence. With new code and one more fiddle to css (background was same colour as text caret), I now have the caret and everything looking nice. I salute your efforts to make life easier for the rest of us.
@scaddenp You’re right. There was an error with the release on npm.
It is now fixed and the version
1.0.5
now usesposition: absolute
as it should.