Skip to content

home: fix VM details screenshot hidden by background extension effect - #7979

Open
osy wants to merge 1 commit into
mainfrom
fix/home-screenshot-background-extension
Open

osy wants to merge 1 commit into
mainfrom
fix/home-screenshot-background-extension

Conversation

@osy

@osy osy commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

On iOS/macOS/visionOS 26+, .backgroundExtensionEffect() was chained directly onto the
tint overlay Rectangle that blends with the screenshot Image beneath it in the VM
details view. The effect snapshots only that one layer to extend it, which discards the
blend and leaves a flat tint-colored box in place of the screenshot.

This groups the image and tint into their own layer and flattens it with
.compositingGroup() before the effect runs, so it operates on the already-composited
result instead of the tint alone.

Testing: Tested by a human on iPad Pro 13" (iPadOS 27.0 simulator), Apple Vision Pro
(visionOS 27.0 simulator), iPad Pro 12.9" 6th gen (iPadOS 18.0 and 17.0 simulators, to
confirm no regression on pre-26 OS where the effect is a no-op), and macOS 27 (native
Debug build, light and dark mode). The author acknowledges that this change has been
tested and/or reviewed by a human in accordance with UTM's AI contribution guidelines.

On iOS/macOS/visionOS 26+, .backgroundExtensionEffect() was chained
directly onto the tint overlay Rectangle that blends with the screenshot
Image beneath it. The effect snapshots only that one layer to extend it,
which discards the blend and leaves a flat tint-colored box in place of
the screenshot.

Group the image and tint into their own layer and flatten it with
.compositingGroup() before the effect runs, so it operates on the
already-composited result instead of the tint alone.

Assisted-by: Claude:claude-sonnet-5
@osy osy added this to the v5.1 milestone Oct 17, 2026
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