Skip to content

fix(textarea): bind value property to native textarea to normalize caret behavior - #31592

Open
rudrakshagarwal4200-ai wants to merge 1 commit into
ionic-team:mainfrom
rudrakshagarwal4200-ai:fix/textarea-caret-initial-value-31579
Open

rudrakshagarwal4200-ai wants to merge 1 commit into
ionic-team:mainfrom
rudrakshagarwal4200-ai:fix/textarea-caret-initial-value-31579

Conversation

@rudrakshagarwal4200-ai

Copy link
Copy Markdown

Summary

Fixes #31579.

In core/src/components/textarea/textarea.tsx, the native <textarea> rendered {value} as child text content rather than binding the value property directly. On initial user focus, this caused WebKit and Chromium browsers to leave the caret positioned at the beginning (index 0) instead of at the end of the text string, diverging from ion-input.

Fix

Explicitly bind value={value} on the <textarea> JSX element and remove child text node rendering, normalizing initial caret placement with ion-input.

…ret behavior (ionic-team#31579)

Bind value={value} directly on native textarea instead of rendering child text node to ensure initial caret positioning matches ion-input.
@vercel

vercel Bot commented Oct 17, 2026

Copy link
Copy Markdown

@rudrakshagarwal4200-ai is attempting to deploy a commit to the Ionic Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added the package: core @ionic/core package label Oct 17, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

package: core @ionic/core package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: (textarea) initial value leaves caret at start unlike ion-input

1 participant