New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: default offset when no BrowserView drag regions #27147
Conversation
Failure:
is not germane, merging. |
Release Notes Persisted
|
I have automatically backported this PR to "11-x-y", please check out #27183 |
I have automatically backported this PR to "12-x-y", please check out #27184 |
I have automatically backported this PR to "10-x-y", please check out #27185 |
Description of Change
Closes #27112.
Fixes an issue where non-draggable regions on
BrowserView
s would have an incorrectly assumed(x,y)
origin of(0,0)
which is an assumption that can be made forBrowserWindow
s but not forBrowserView
s. In the latter case, we should calculate and pass the origin point of the BrowserView and pass it instead.Checklist
npm test
passesRelease Notes
Notes: Fixes an issue where non-draggable regions on BrowserViews could have incorrectly calculated bounds.