fix: resizing borders in nondraggable regions #37016
Merged
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.
Description of Change
Closes #37008.
Refs #36230.
The above refactor improved draggable regions by typing them most closely to WebContents, but introduced an issue whereby draggable regions could take precedence over resizing borders on Windows. This was happening as a result of
NativeWindow::NonClientHitTest
, which returned the first non-HTNOWHERE value it found. This meant that the window's border coordinates would not take appropriate precedence, and instead ofHTBOTTOM
,HTLEFT
, etc being returned for the window edge coordinates,HTCAPTION
would instead be returned and the window bordered rendered useless. We fix this by first checkingResizingBorderHitTest
results inNativeWindow::NonClientHitTest
and proceeding to draggable region calculations if we are not on a resizing window border.Tested with https://gist.github.com/takumus/9054bde77c8206143232fed2659bf108
Checklist
npm test
passesRelease Notes
Notes: Fixes an issue where some frameless windows with draggable regions were not resizable on Windows.