PR #74369: fix(control-ui): preserve numeric chat input in composer

• Repository: openclaw/openclaw
• Author: dwc1997
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/74369

Description (problem / solution / changelog)

Summary

• Problem: In Control UI chat composer, pure numeric input could be auto-formatted by browser/OS input behaviors (for example 123456789 becoming grouped with separators), and then sent as modified text.
• Why it matters: Numeric-only identifiers/arguments must be transmitted exactly; formatting changes can break IDs, URLs, and downstream commands.
• What changed: Added explicit plain-text input attributes on the chat textarea (autocomplete="off", autocorrect="off", autocapitalize="off", spellcheck="false", inputmode="text"), plus regression tests for composer attributes and numeric payload preservation.
• What did NOT change (scope boundary): No gateway sanitization changes, no message normalization logic changes, no slash-command/send pipeline refactor.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #74354
• Related #74354
• This PR fixes a bug or regression

Root Cause (if applicable)

• Root cause: Composer textarea lacked explicit plain-text/autocorrect suppression attributes, so browser/OS input behavior could rewrite numeric-only drafts before chat.send.
• Missing detection / guardrail: No regression test asserted composer input attributes or numeric-only payload pass-through.
• Contributing context (if known): Current send path forwards draft as typed; once browser-level formatting occurs in textarea value, the modified value is sent.

Regression Test Plan (if applicable)

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
• Target test or file:
  • ui/src/ui/views/chat.test.ts
  • ui/src/ui/app-chat.test.ts
• Scenario the test should lock in:
  • Composer renders with plain-text input attributes that discourage auto-formatting.
  • Numeric-only draft (123456789) is sent unchanged to chat.send.
• Why this is the smallest reliable guardrail:
  • Bug trigger is at UI input/composer layer; unit tests at view + send boundary validate exact behavior without broader E2E cost.
• Existing test that already covers this (if any):
  • None.
• If no new test is added, why not:
  • N/A (new tests added).

User-visible / Behavior Changes

• Control UI chat input now explicitly behaves as plain text to reduce browser/OS auto-formatting of numeric-only drafts.
• Numeric-only messages are more reliably preserved as typed when sent.

Diagram (if applicable)

Before:
[user types 123456789] -> [browser/OS may auto-format draft] -> [chat.send sends modified value]

After:
[user types 123456789] -> [textarea plain-text attributes suppress auto-formatting] -> [chat.send sends original value]

## Changed files

- `ui/src/ui/app-chat.test.ts` (modified, +24/-0)
- `ui/src/ui/views/chat.test.ts` (modified, +14/-0)
- `ui/src/ui/views/chat.ts` (modified, +5/-0)