Restrict document window drag docking to chrome targets#1066
Merged
wieslawsoltes merged 1 commit intowieslawsoltes:masterfrom Mar 9, 2026
Merged
Conversation
This was referenced Mar 11, 2026
Closed
This was referenced Mar 18, 2026
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
2 participants
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.
This changes floating document window drag behavior so drags started from DocumentTabStrip no longer dock back into background windows over the full dock surface by default. Instead, they only target window chrome surfaces such as tab strips/titlebars, which restores the expected titlebar-to-titlebar docking behavior.
The drag target scope is now configurable through DockSettings.DocumentWindowDragScope, using the new WindowDragDockScope enum. The default is WindowChrome, while FullWindow preserves the broader docking behavior if needed. The host-window drag pipeline was updated to honor that scope, and existing HostWindowState headless tests still pass.