Skip to content

fix: keep fitting input values visible and record bare Delete/Backspace hotkeys - #121

Merged
kirillDevPro merged 4 commits into
masterfrom
fix/input-visible-and-bare-delete
Oct 14, 2026
Merged

kirillDevPro merged 4 commits into
masterfrom
fix/input-visible-and-bare-delete

Conversation

@kirillDevPro

Copy link
Copy Markdown
Collaborator

What & why

  • Input values. A single-line input whose value fits the field could scroll it out of view and render blank. The field now keeps a fitting value visible; a regression test uses the platform caret width. Mirror metadata for input/text_area refreshed in the same PR.
  • Hotkey capture. The hotkey recorder ignored a bare Delete or Backspace, so those keys could not be bound (needed by MoonTerminal's Delete-removes-figure action). They are now recorded as bindings.

How to verify

Local, all guardrail steps: cargo fmt --all -- --check, cargo check -p moon-ui-gallery, cargo test -p moon-ui-components, cargo test -p moon-ui-gallery, cargo xtask component-audit --check-baseline, cargo xtask component-api --check-baseline, cargo xtask component-mirror --donor-root vendor/longbridge-gpui-component-ui-src --check-baseline all green.

Regenerate only the input and text_area mirror entries for the input fix and regression tests. The new sibling test module adds one donor-different file, so raise only those two reviewed drift budgets from 19 to 20 as authorized by the coordinator.
@kirillDevPro
kirillDevPro merged commit 3a5b34a into master Oct 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant