Fix interop initial z-order placement on Windows #1774
Merged
Conversation
This file contains 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.
Fix counting of non-interop components for initial interop placement on Windows. It was a regression after #1340: it subtracts
root.componentCountbefore change andinteropComponents.sizeafter a change that results in an incorrect value during initial placement. Any further invalidations like window resizing corrected the problem.Fixes https://youtrack.jetbrains.com/issue/CMP-7375
Testing
Manually - screenshot testing in this case requires DX rendering, so our CI won't handle that.
Release Notes
Fixes - Desktop
compose.interop.blendingflag (1.7.0 regression)