Skip to content

Key panel: path, text and copy buttons stay inside the card - #14

Merged
engagepy merged 1 commit into
mainfrom
key-hint-layout
Sep 30, 2026
Merged

engagepy merged 1 commit into
mainfrom
key-hint-layout

Conversation

@engagepy

Copy link
Copy Markdown
Owner

On a copy installed from PyPI, the "Tuner needs OPENAI_API_KEY · where?" panel spilled its long path, its text and its copy buttons outside the card.

Cause: the panel's content asked for 26rem, but Popover is fixed at 18rem (w-72), so the content overflowed the card. The installed path, ~/Library/Application Support/SLM Forge/.env, is long enough to make it obvious.

Fix:

  • Popover gets a wide size (26rem), used by this panel.
  • CodeBlock gets a wrap option, so a long path or command wraps inside its block instead of scrolling sideways. The copy button stays in view.
  • The panel opens towards the side with room, so it stays on screen when the window is narrow.

Verified in Chrome at 1440, 1280, 1100 and 900 px against a scratch server using the real installed-app path. The card stays on screen, all text and both copy buttons sit inside it, and nothing scrolls sideways. Other code blocks are unchanged. The web build is clean and 211 tests pass.

PyPI users get this in the next release.

🤖 Generated with Claude Code

The "where?" panel asked for 26rem inside a Popover fixed at 18rem, so on an installed copy
(where the path is long: ~/Library/Application Support/SLM Forge/.env) the text and copy buttons
spilled past the card. Popover gets a `wide` size, CodeBlock can wrap long values in place of
scrolling them sideways, and the panel opens towards the side with room on narrow windows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: engagepy <42845567+engagepy@users.noreply.github.com>
@engagepy
engagepy merged commit 3438cdc into main Sep 30, 2026
2 checks passed
@engagepy
engagepy deleted the key-hint-layout branch September 30, 2026 08:56
@engagepy engagepy mentioned this pull request Oct 1, 2026
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