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: ensure BrowserView
bounds are always relative to window
#39605
Conversation
fd8cf86
to
be77505
Compare
Release Notes Persisted
|
I was unable to backport this PR to "25-x-y" cleanly; |
I was unable to backport this PR to "26-x-y" cleanly; |
I have automatically backported this PR to "27-x-y", please check out #39627 |
@codebytere has manually backported this PR to "26-x-y", please check out #39850 |
@codebytere has manually backported this PR to "25-x-y", please check out #39851 |
…ron#39605) fix: ensure BrowserView bounds are always relative to window
Description of Change
Closes #39257
Fixes an issue where
BrowserViews
that have their bounds set prior to being added to aBrowserWindow
have unexpected incorrect offsets after being added. This was happening becauseBrowserView
bounds are intended to be relative to the containing window, and were not updated relative to the window once they were added to one. We fix this by checking whether or not theBrowserView
had its bounds previously set and ensure they're reset relative to the window on addition.Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where
BrowserViews
that had their bounds set prior to being added to aBrowserWindow
could have unexpected incorrect offsets.