Skip to content

fix(web): remove glass chrome strip below chat composer#3706

Open
maria-rcks wants to merge 1 commit into
pingdotgg:t3code/codex-turn-mappingfrom
maria-rcks:fix/remove-composer-lower-glass
Open

fix(web): remove glass chrome strip below chat composer#3706
maria-rcks wants to merge 1 commit into
pingdotgg:t3code/codex-turn-mappingfrom
maria-rcks:fix/remove-composer-lower-glass

Conversation

@maria-rcks

@maria-rcks maria-rcks commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator

What Changed

Removed the glass chrome strip that rendered below the chat composer: the empty chat-composer-lower-chrome div and the chat-composer-shared-blur backdrop layer, plus their now-dead CSS rules. The composer overlay keeps the same bottom spacing via its own padding, and the composer's floating-glass-surface is unchanged.

Why

The strip appeared as a second glass box leaking out under the input, instead of the composer floating on its own. Deleting the two decorative elements and folding their shared background values into the surviving .floating-glass-surface selectors fixes it with a net −29 line diff and no behavior change to the input itself.

UI Changes

Before After
image image

Checklist

  • This PR is small and focused
  • I explained what changed and why
  • I included before/after screenshots for any UI changes
  • I included a video for animation/interaction changes (n/a — no motion changes)

Note

Low Risk
Visual/layout-only chat composer chrome cleanup with no logic or API changes; minor risk of bottom spacing differences on devices with safe-area insets.

Overview
Fixes a second glass panel appearing under the chat input by removing the decorative backdrop layer (chat-composer-shared-blur) and the empty chat-composer-lower-chrome spacer from ChatView.

Bottom safe-area padding now lives on the composer overlay wrapper instead of the removed lower chrome, so timeline inset / composerOverlayHeight behavior should stay aligned. floating-glass-surface on ChatComposer is unchanged; related CSS is trimmed so glass styles apply only to that class (no shared rules with the deleted chrome).

Reviewed by Cursor Bugbot for commit 4a342fb. Bugbot is set up for automated code reviews on this repo. Configure here.

Note

Remove glass chrome strip below chat composer

Removes the lower chrome divider and shared blur wrapper elements from the chat composer in ChatView.tsx. Safe-area bottom padding is now applied directly on the composer overlay wrapper. Corresponding CSS classes chat-composer-lower-chrome and chat-composer-shared-blur are deleted from index.css, with glass styling consolidated onto .floating-glass-surface only.

Macroscope summarized 4a342fb.

@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 69125ea5-4a8d-450c-8db4-bb0a8d2a5fa5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Jul 5, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4a342fb. Configure here.

ref={setComposerOverlayElement}
data-chat-composer-overlay="true"
className="pointer-events-none absolute inset-x-0 bottom-0 z-20 pt-1.5 sm:pt-2"
className="pointer-events-none absolute inset-x-0 bottom-0 z-20 pt-1.5 pb-[calc(env(safe-area-inset-bottom)+0.75rem)] sm:pt-2 sm:pb-[calc(env(safe-area-inset-bottom)+1rem)]"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Bottom safe-area taps hit timeline

Medium Severity

Bottom spacing moved onto the pointer-events-none composer overlay, but the removed chat-composer-lower-chrome sibling was the only in-flow layer in that band with default pointer hit-testing. Taps in the safe-area and extra bottom padding can reach the scrolling timeline underneath instead of being absorbed above it.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 4a342fb. Configure here.

@macroscopeapp

macroscopeapp Bot commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Needs human review

This UI cleanup removes a glass effect below the chat composer. However, an unresolved review comment flags a potential pointer-events issue where taps in the bottom safe-area may now pass through to the timeline underneath, which warrants human verification.

You can customize Macroscope's approvability policy. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M 30-99 changed lines (additions + deletions). vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant