Skip to content

Fix desktop launch motion and reaction spacing#1717

Open
klopez4212 wants to merge 2 commits into
mainfrom
kennylopez-titlebar-reaction-spacing
Open

Fix desktop launch motion and reaction spacing#1717
klopez4212 wants to merge 2 commits into
mainfrom
kennylopez-titlebar-reaction-spacing

Conversation

@klopez4212

Copy link
Copy Markdown
Contributor

Summary

  • Reveal the macOS window only after restored geometry and the startup UI are ready, with a temporary native backing to prevent the previous app showing through.
  • Use the native traffic-light position and keep the adjacent chrome aligned.
  • Reduce the message-body-to-reaction gap to 6px and cover it in the reaction E2E spec.

The launch movement came from asynchronous window restoration plus the transparent first webview frames exposing the previous app's controls.

Testing

  • pnpm --dir desktop check
  • cargo check --manifest-path desktop/src-tauri/Cargo.toml --no-default-features --features system-keyring
  • pnpm exec playwright test --project=smoke tests/e2e/reaction-order.spec.ts (2 passed)
  • Verified cold launch in staging with a 30 fps capture

@klopez4212 klopez4212 marked this pull request as ready for review July 10, 2026 16:55
@klopez4212 klopez4212 requested a review from a team as a code owner July 10, 2026 16:55

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 420bd8d952

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread desktop/src-tauri/src/lib.rs Outdated
wait_for_stable_initial_window_geometry only accepted bounds when
is_maximized() returned Ok(true). When the window-state plugin restores a
normal (non-maximized) saved window, is_maximized() is false, so bounds
stayed None forever, no stable state was detected, and the reveal waited
the full poll budget (~1.9s) before timing out on every launch.

Sample outer position/size regardless of maximized state and rely on
consecutive identical bounds to detect that the async restore settled.

Signed-off-by: klopez4212 <klopez4212@gmail.com>

Co-authored-by: Fizz <8a675edd33677aa0389f6650d467b2041fb0df4ca820eacb009babb95e3715d4@sprout-oss.stage.blox.sqprod.co>
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