fix: draggable regions updating on bounds change #34582
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 #34552.
Fixes an issue where draggable regions were not recalculated when BrowserView bounds changed. This was happening because we didn't issue a call to
UpdateDraggableRegions
after bounds changed on Windows, as we do on macOS:electron/shell/browser/native_browser_view_mac.mm
Line 270 in abf6f1c
Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where draggable regions were not recalculated when BrowserView bounds changed on Windows.