PageZoomInput keeps its own currentZoom string state and only commits to the persisted pageZoom setting on Enter (handleZoomEnter) or reverts it on Escape; there is no onBlur handler. If the user types a new percentage and then clicks elsewhere on the settings page — a very natural interaction, e.g. to look at another setting — instead of pressing Enter, the typed value is silently dropped with no save and no visible warning beyond a subtle Secondary/Success input-color cue that most users won't parse as "you must press Enter."
How to trigger
Settings → Appearance → Page Zoom → type a new value → click anywhere else on the page (don't press Enter) → the change never applied, and there's no indication why.
Suggested fix
Commit on blur as well as Enter, or add an explicit Save/Apply affordance next to the field.
Filed from the September 2026 client audit (branch lotus @ 4bea4895).
**Severity:** low · **Type:** ux · **Confidence:** high
**Location:** `src/app/features/settings/general/General.tsx:389-432`
### Problem
`PageZoomInput` keeps its own `currentZoom` string state and only commits to the persisted `pageZoom` setting on `Enter` (`handleZoomEnter`) or reverts it on `Escape`; there is no `onBlur` handler. If the user types a new percentage and then clicks elsewhere on the settings page — a very natural interaction, e.g. to look at another setting — instead of pressing Enter, the typed value is silently dropped with no save and no visible warning beyond a subtle Secondary/Success input-color cue that most users won't parse as "you must press Enter."
### How to trigger
Settings → Appearance → Page Zoom → type a new value → click anywhere else on the page (don't press Enter) → the change never applied, and there's no indication why.
### Suggested fix
Commit on blur as well as Enter, or add an explicit Save/Apply affordance next to the field.
---
_Filed from the September 2026 client audit (branch `lotus` @ 4bea4895)._
jared
added this to the Audit 2026-09 · Medium & Low milestone 2026-09-12 01:51:28 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: low · Type: ux · Confidence: high
Location:
src/app/features/settings/general/General.tsx:389-432Problem
PageZoomInputkeeps its owncurrentZoomstring state and only commits to the persistedpageZoomsetting onEnter(handleZoomEnter) or reverts it onEscape; there is noonBlurhandler. If the user types a new percentage and then clicks elsewhere on the settings page — a very natural interaction, e.g. to look at another setting — instead of pressing Enter, the typed value is silently dropped with no save and no visible warning beyond a subtle Secondary/Success input-color cue that most users won't parse as "you must press Enter."How to trigger
Settings → Appearance → Page Zoom → type a new value → click anywhere else on the page (don't press Enter) → the change never applied, and there's no indication why.
Suggested fix
Commit on blur as well as Enter, or add an explicit Save/Apply affordance next to the field.
Filed from the September 2026 client audit (branch
lotus@4bea4895).