Repository navigation
fix(web): quick message composer is opaque again - #501
Merged
Merged
Conversation
The upstream move of appearance setup into startAppServices runs it in the quick message window too. Its inline --glass-opacity beat the panel's opaque override, and the window started the main window's background services. The quick message window now applies only fonts and document attributes, and skips glass, contrast and the remaining app services. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Since the upstream sync in aa4cf00, the desktop quick message composer and its menus are see-through, showing the apps behind the window.
Upstream PR pingdotgg#25004 moved appearance setup from the root route into
startAppServices(), which runs in every window. In the quick message window it writes the glass opacity setting (80% by default) inline on<html>. That beats thehtml[data-quick-message] { --glass-opacity: 100% }override inindex.css. The window was also starting all of the main window's background services: notifications, toasts, migrations, default-theme adoption and agent-opened previews. Before the sync, the root route ran only its appearance and font sync there.Fix
In
apps/web/src/appInit.tsx:startAppServices()returns right afterstartClientAppearance(), so the panel runs what it ran before the sync.startClientAppearance()doesn't write glass opacity or contrast in that window. The CSS keeps the panel opaque, anduseThemealready applies the panel's own contrast.Verification
Format, lint and the
apps/webtypecheck pass.vp run check:changeddidn't run because it failed to load the task config forapps/desktop.Not yet checked in the desktop app, so there are no before/after captures. The before state is in the bug report screenshot.
Done by Claude Opus 5.5 in Claude Code (T3 Code).
🤖 Generated with Claude Code