Mobile: keyboard snaps to upper-case after each letter on multiplayer name entry (LOW nit) #108

New issue

Closed

opened 2026-06-22 21:10:18 +02:00 by bosun · 1 comment

bosun commented 2026-06-22 21:10:18 +02:00

Owner

Copy link

Behavior (operator iPhone playtest 2026-06-22, deployed round-18)

On the multiplayer name entry screen, mobile keyboard auto-capitalizes after each entered letter — the keyboard layout snaps back to upper-case after every keystroke.

Severity: LOW (operator-named nit)

The name is uppercased server-side / for display anyway, so functionally the entered name ends up correct regardless. Issue is purely the mobile-keyboard-UX flicker.

Fix-direction (Shipwright lane)

HTML input attributes that control this on mobile:

• autocapitalize="none" — disables auto-capitalize entirely (probably right call since field is uppercased anyway)
• autocapitalize="characters" — sticks at upper-case (doesn't fix flicker; same as default)
• inputmode="text" — also worth checking

The DOM input added for #66 multiplayer name entry is the target element.

Acceptance criteria

1. Mobile keyboard does NOT snap to upper-case after each keystroke during name entry
2. Functional behavior preserved (name still ends up correct, server-uppercased)
3. Desktop behavior unaffected
4. Verify on iPhone-13 emulation + real device if possible

Anchor

2026-06-22 operator iPhone playtest of round-18 deployed substrate. Operator explicitly framed as "only a nit — the name is uppercased after the entry anyway."

## Behavior (operator iPhone playtest 2026-06-22, deployed round-18) On the multiplayer name entry screen, mobile keyboard auto-capitalizes after each entered letter — the keyboard layout snaps back to upper-case after every keystroke. ## Severity: LOW (operator-named nit) The name is uppercased server-side / for display anyway, so functionally the entered name ends up correct regardless. Issue is purely the mobile-keyboard-UX flicker. ## Fix-direction (Shipwright lane) HTML input attributes that control this on mobile: - `autocapitalize="none"` — disables auto-capitalize entirely (probably right call since field is uppercased anyway) - `autocapitalize="characters"` — sticks at upper-case (doesn't fix flicker; same as default) - `inputmode="text"` — also worth checking The DOM input added for #66 multiplayer name entry is the target element. ## Acceptance criteria 1. Mobile keyboard does NOT snap to upper-case after each keystroke during name entry 2. Functional behavior preserved (name still ends up correct, server-uppercased) 3. Desktop behavior unaffected 4. Verify on iPhone-13 emulation + real device if possible ## Anchor 2026-06-22 operator iPhone playtest of round-18 deployed substrate. Operator explicitly framed as "only a nit — the name is uppercased after the entry anyway."

shipwright self-assigned this 2026-06-23 19:26:39 +02:00

shipwright referenced this issue from a commit 2026-06-23 19:26:44 +02:00

fix(client): mobile-portrait polish — autocap, lobby name-plate width, touch-control fold (#108, #120, #104)

shipwright referenced this issue from a pull request that will close it, 2026-06-23 19:27:16 +02:00

fix(client): mobile-portrait polish — autocap, lobby name-plate width, touch-control fold (#108, #120, #104) #133

bosun closed this issue 2026-06-23 19:33:22 +02:00

bosun referenced this issue from a commit 2026-06-23 19:33:24 +02:00

fix(client): mobile-portrait polish — autocap + touch-fold + lobby plate (#108, #104, #120)

shipwright referenced this issue from a commit 2026-06-23 19:37:11 +02:00

test(client): pin touch-control fold-fit invariant on portrait mobile (#104 follow-up)

shipwright referenced this issue 2026-06-23 19:37:21 +02:00

test(client): pin touch-control fold-fit invariant on portrait mobile (#104 follow-up) #134

bosun referenced this issue from a commit 2026-06-23 19:40:08 +02:00

test(client): fold-fit invariant pin for mobile touch controls (#104 follow-up)

bosun referenced this issue from a commit 2026-06-23 21:02:29 +02:00

test(client): migrate net-stub seam tests to WS-mock substrate (#113) — sprint 16/16

bosun commented 2026-06-24 01:03:10 +02:00

Author

Owner

Copy link

Substrate-of-record clarification (post-fix operator playtest 2026-06-24)

Operator clarification on the actual previous behavior:

"The letters were previously locked in upper case / caps, but I could disable the caps manually by pressing the shift key. I came to the idea to try this out because I saw that on Desktop the player name was not all-caps when entering, while on mobile it was always all-caps. So it was not even an issue before, depending on the definition."

Actual previous behavior: mobile defaulted to caps-LOCK (shift-overridable); desktop did not. Mobile-vs-desktop asymmetry on input-case. The original tracker description "upper-case flicker" was imprecise — actual symptom was caps-LOCK not flicker.

Why the fix still works: removing autocapitalize="characters" symmetrizes mobile to match desktop. Both now default to not-caps; shift-key still works on both. Behavior consistent across devices.

Substrate-discipline note: this is a worked-instance of filed-rootcause-is-hypothesis at substrate-of-record-layer. Original tracker characterization ("flicker") was hypothesis-form; empirical playtest revealed actual mechanism (caps-LOCK shift-overridable + cross-device asymmetry). Same intervention (remove autocapitalize) closes both interpretations because the substrate-mechanism is the same — the description-imprecision didn't affect fix correctness.

Substrate-of-record updated honest.

## Substrate-of-record clarification (post-fix operator playtest 2026-06-24) Operator clarification on the actual previous behavior: > "The letters were previously locked in upper case / caps, but I could disable the caps manually by pressing the shift key. I came to the idea to try this out because I saw that on Desktop the player name was not all-caps when entering, while on mobile it was always all-caps. So it was not even an issue before, depending on the definition." **Actual previous behavior**: mobile defaulted to caps-LOCK (shift-overridable); desktop did not. Mobile-vs-desktop asymmetry on input-case. The original tracker description "upper-case flicker" was imprecise — actual symptom was caps-LOCK not flicker. **Why the fix still works**: removing `autocapitalize="characters"` symmetrizes mobile to match desktop. Both now default to not-caps; shift-key still works on both. Behavior consistent across devices. **Substrate-discipline note**: this is a worked-instance of filed-rootcause-is-hypothesis at substrate-of-record-layer. Original tracker characterization ("flicker") was hypothesis-form; empirical playtest revealed actual mechanism (caps-LOCK shift-overridable + cross-device asymmetry). Same intervention (remove autocapitalize) closes both interpretations because the substrate-mechanism is the same — the description-imprecision didn't affect fix correctness. Substrate-of-record updated honest.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

release-prep/rolling

i/rt806-secrets-inherit

i/repin-release-toolkit-v0.42.0

i/280-fragment-check-wiring

i/release-toolkit-v0.18.0-bump

i/cellblock-release-toolkit-adoption-v0.10.1

i/162-release-toolkit-substrate-prep

i/145-boot-auto-resume

i/149-force-take-resume

i/142-cellmate-found-back-cancel

i/151-cancel-protocol

i/160-nav-arrange-await

i/155-disconnect-overlay-debounce

i/146-lobby-nameplate-margin

i/147-version-display

i/139-survivor-overlay

i/139-reconnecting-overlay

i/144-history-trap-depth

i/141-highscores-clickthrough

i/130-live-stats-wire

i/113-netstub-migration

i/115-reconnect-via-resume

i/88-checkin-touch-back

i/104-fold-invariant-test

i/104-108-120-mobile-portrait-polish

i/101-cabinet-bezel

i/123-localstorage-resume-token

i/103-121-input-label-polish

i/102-cue-logic-test

i/102-celebration-cue

i/122-keepalive-tightening

i/111-server-gravity-hold

i/100-tagline-contrast

i/99-mobile-versus-layout

i/cellblock-83-video-on-failure

i/109-back-button-trap

i/93-ws-onclose-handler

i/92-ws-mock-harness

i/110-countdown-input-lock

i/97-initials-focus-capture

i/98-eligibility-deconflation

i/87-abort-forfeit

i/87-server-forfeit

i/91-solo-playagain-mode

i/85-lobby-esc-back

i/86-durationms-int

i/81-keyboard-nav-harness

i/73-landscape-initials

i/76-admin-redact-endpoint

i/66-checkin-name-input

i/59-initials-scroller

i/54-leaderboard-metrics

i/51-remove-dead-attachinput

i/69-block-pinch-zoom

i/62-portrait-gameover

i/57-portrait-solo-layout

i/64-rapid-tap-zoom

i/60-canvas-text-selection

i/56-ios-audio-unlock

i/53-next-queue

i/capture-bg-harness

i/49-animated-bg

i/28-leaderboard-wire

i/26-validation-harnesses

i/28-leaderboard-store

i/31-soft-drop-tick

i/28-leaderboard-ui-shell

i/39-nextqueue-contract

i/39-nextqueue

i/33-bgm-gain

i/16-solo-mode

i/35-keyboard-parity

i/32-spectate-exit

i/15-bgm

i/16-solo-server-endpoint

i/21-ci-race-guard

i/8-smooth-fall

i/16-solo-sfx-best

i/16-solo-hide

i/9-dissolve

v1.2.0

v1.1.0

v1.0.0

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

shipwright

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

frankenbit/cellblock#108

No description provided.