Skip to content

propose: Add visual feedback when the intent input is cleared with Esc…#2

Open
atomeam wants to merge 1 commit into
mainfrom
propose/2026-05-15T10-32-05
Open

propose: Add visual feedback when the intent input is cleared with Esc…#2
atomeam wants to merge 1 commit into
mainfrom
propose/2026-05-15T10-32-05

Conversation

@atomeam

@atomeam atomeam commented May 15, 2026

Copy link
Copy Markdown
Owner

Generated by HomeBase using Mistral.

Summary: Add visual feedback when the intent input is cleared with Escape key

Patches: 1

Review the diff. Merge to deploy.

Notes seen by the model:
(none yet)

Summary by CodeRabbit

  • New Features
    • Pressing Escape now displays a temporary confirmation message when clearing the input field, providing user feedback for the action.

Review Change Stack

@coderabbitai

coderabbitai Bot commented May 15, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

The Escape key handler for the global intent input field now displays a temporary "Intent cleared" info banner when pressed, providing visual user feedback alongside the existing clear-and-blur behavior.

Changes

Intent Input User Feedback

Layer / File(s) Summary
Intent Input Escape Handler Feedback
mini/index.html
Pressing Escape on the intent input now triggers a temporary info banner displaying "Intent cleared" for 1000ms after clearing and blurring the input field.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A press of Escape, the field clears with grace,
A banner appears, a smile on its face—
"Intent cleared!" it chirps with delight,
Feedback so swift, a user's pure light! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding visual feedback when the intent input is cleared with the Escape key, which matches the code modification that adds an info banner.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch propose/2026-05-15T10-32-05

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@mini/index.html`:
- Line 483: The UI now calls showBanner('info', ...) when Escape clears the
intent, but there's no CSS rules for a .banner.info state; add a dedicated style
for .banner.info (similar to existing
.banner.success/.banner.error/.banner.warning) to define background-color,
text-color, and any icon or border styles so the info banner is visually
distinct; update the stylesheet where .banner classes live and ensure the
selector .banner.info is applied when showBanner('info', ...) is invoked.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ce0d84fd-bdae-411e-a50d-0dda11772dd6

📥 Commits

Reviewing files that changed from the base of the PR and between 1d20d38 and 757d2ed.

📒 Files selected for processing (1)
  • mini/index.html

Comment thread mini/index.html
intent.addEventListener('keydown', function(e){
if (e.key === 'Enter') { e.preventDefault(); press(); }
else if (e.key === 'Escape') { intent.value = ''; intent.blur(); }
else if (e.key === 'Escape') { intent.value = ''; intent.blur(); showBanner('info', 'Intent cleared', 1000); }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Add a dedicated style for the new info banner state.

showBanner('info', ...) introduces a new banner kind, but there is no .banner.info style, so the feedback can be visually weak/inconsistent.

🎨 Suggested fix
   .banner.error   { background: `#7f1d1d`; color: `#fecaca`; border-bottom: 2px solid `#ef4444`; }
   .banner.warn    { background: `#78350f`; color: `#fed7aa`; border-bottom: 2px solid `#f59e0b`; }
   .banner.success { background: `#14532d`; color: `#bbf7d0`; border-bottom: 2px solid `#22c55e`; }
+  .banner.info    { background: `#1e3a8a`; color: `#dbeafe`; border-bottom: 2px solid `#60a5fa`; }
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@mini/index.html` at line 483, The UI now calls showBanner('info', ...) when
Escape clears the intent, but there's no CSS rules for a .banner.info state; add
a dedicated style for .banner.info (similar to existing
.banner.success/.banner.error/.banner.warning) to define background-color,
text-color, and any icon or border styles so the info banner is visually
distinct; update the stylesheet where .banner classes live and ensure the
selector .banner.info is applied when showBanner('info', ...) is invoked.

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