Skip to content

Mobile: Disable auto correct, auto complete and auto capitalize for setting search field - #14810

Merged
laurent22 merged 1 commit into
laurent22:devfrom
mrjo118:no-autocorrect-setting-search
Mar 20, 2026
Merged

Mobile: Disable auto correct, auto complete and auto capitalize for setting search field#14810
laurent22 merged 1 commit into
laurent22:devfrom
mrjo118:no-autocorrect-setting-search

Conversation

@mrjo118

@mrjo118 mrjo118 commented Mar 17, 2026

Copy link
Copy Markdown
Collaborator

This is an addition to #14759

The setting search input uses auto correction / auto complete / auto capitalize when enabled on the input method. Logically a search input should not use those behaviours, as the input allows incomplete words or phrases by design, so should be excluded from those functions of the input method.

This PR disables auto correct, auto complete and auto capitalize for the setting search input in the app.

Testing

Behaviour before the change:

bu4Y0H8Ror.mp4

Behaviour after the change:

studio64_tZDrEAbo2W.mp4

@coderabbitai

coderabbitai Bot commented Mar 17, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c9690829-ccb3-4746-825d-204f0bd48848

📥 Commits

Reviewing files that changed from the base of the PR and between ea4efa6 and 9de6dab.

📒 Files selected for processing (1)
  • packages/app-mobile/components/screens/ConfigScreen/ConfigScreen.tsx

📝 Walkthrough

Walkthrough

Adds three TextInput properties (autoCapitalize, autoComplete, autoCorrect) to the search input in ConfigScreen to disable auto-correction behaviour. The properties are applied to both instances where the search input is defined and rendered.

Changes

Cohort / File(s) Summary
Search input autocorrection
packages/app-mobile/components/screens/ConfigScreen/ConfigScreen.tsx
Disables auto-capitalization, auto-complete, and auto-correct on the search TextInput component by adding three props in both input instances.

Possibly related PRs

  • #14759: Adds identical TextInput props to disable autocorrect/autocomplete/capitalization on search inputs across the codebase.
  • #14611: Modifies TextInput props (autoCapitalize, autoCorrect) to prevent unintended capitalisation and autocorrection on mobile inputs.

Suggested labels

mobile, search

Suggested reviewers

  • Kaushalendra-Marcus
🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: disabling auto-correct, auto-complete, and auto-capitalize for the mobile settings search field.
Description check ✅ Passed The description is directly related to the changeset, explaining the rationale for disabling input-method behaviours on the search field and providing testing evidence.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Pr Description Must Follow Guidelines ✅ Passed The pull request description includes all three required sections: problem statement, high-level solution, and test plan with before-and-after video examples.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot added mobile All mobile platforms search labels Mar 17, 2026
@laurent22
laurent22 merged commit 088d8eb into laurent22:dev Mar 20, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mobile All mobile platforms search

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants