Skip to content

fix(android): keep Window view chrome on the picture while it eases - #289

Merged
raiseCatError merged 1 commit into
devfrom
fix/92-android-chrome-follows-picture
Nov 16, 2026
Merged

raiseCatError merged 1 commit into
devfrom
fix/92-android-chrome-follows-picture

Conversation

@raiseCatError

Copy link
Copy Markdown
Owner

Summary

Android part of #92. Android's Window view chrome already follows the keyboard viewport (it reads the same transform the touches use), so the iOS #152 desync doesn't happen there. One gap remained: while the picture eases to follow the Mac's text caret (220 ms), the video and cursor sprite draw from the animated frame (shown), but WorkspaceChrome got the end-state transform. Outlines, title pills and dividers ran ahead of the picture for that moment. This passes shown, as iOS does since #161.

Related issue: #92 (stays open for device checks).

Scope and compatibility

  • Platforms/components affected: Android receiver, ReceiverScreen.kt (one argument).
  • User-visible behavior: Window view chrome moves with the picture during caret-follow.
  • Compatibility considerations: none (no protocol, settings or permission change).

Verification

Check Result and evidence
Automated tests / lint / build :app:compileDebugKotlin passes locally (JDK 17). No unit test: Compose layout only.
Physical devices tested (models and OS versions) None.
Simulator or emulator (if used) None.
Not tested / known limitations Touch mapping during the 220 ms ease still uses the end state (the other half of iOS #161, not ported). Device check with the keyboard and Zoom While Typing.

Safety and review checklist

  • This is a focused change with no unrelated refactors.
  • Relevant automated checks ran; failures or skipped tests are documented.
  • I distinguished real-device verification from simulator/emulator or unit tests.
  • Existing pairing, security and consent behavior is preserved, or changes are explained.
  • Public screenshots, logs and test data contain no personal data, private endpoints, identifiers, secrets or pairing codes.
  • Documentation, user-facing terminology and accessibility were updated if relevant.
  • No signing material, credentials, provisioning profiles or local build artifacts are included.
  • This PR does not tag, release, publish, or alter protected release workflows without explicit maintainer coordination.

)

While the picture eases to follow the Mac's text caret (220 ms), the video and
the cursor sprite drew from the animated frame, but the Window view chrome
(pane outlines, title pills, dividers, input prompt) used the end-state
transform, so it ran ahead of the picture. Pass the drawn transform instead,
as iOS does since #161.

Touch mapping during the ease still uses the end state; that part of #161 is
not ported.
@raiseCatError
raiseCatError marked this pull request as ready for review November 16, 2026 07:05
@raiseCatError
raiseCatError merged commit d37722c into dev Nov 16, 2026
9 checks passed
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