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: falsy transparent shouldn't affect webContents background #36914
Conversation
d20e160
to
257490e
Compare
Release Notes Persisted
|
I was unable to backport this PR to "24-x-y" cleanly; |
I was unable to backport this PR to "23-x-y" cleanly; |
/trop run backport-to 25-x-y |
The backport process for this PR has been manually initiated - sending your PR to |
I was unable to backport this PR to "25-x-y" cleanly; |
@dsanders11 has manually backported this PR to "25-x-y", please check out #38157 |
@dsanders11 has manually backported this PR to "24-x-y", please check out #38158 |
@dsanders11 has manually backported this PR to "23-x-y", please check out #38159 |
fix: falsy transparent shouldn't affect webContents background (#36914)
Description of Change
Fixes #37737.
Fixes #36538.
Falsy values for
transparent
were incorrectly setting thewebContents
background to be transparent. This was only noticeable in certain situations, since setting a background color for the page would override the transparency. It would affect child windows without any explicit setting oftransparent
due to the usage of an empty object for browser window options in those cases which led to thetransparent
key being set with a value ofundefined
, triggering the bug.Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where default background color for windows might be incorrect