-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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: BrowserWindow transparency not working #30136
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to break fairly frequently... is there some way we could test this? With desktopCapturer
perhaps? 😬
103ca40
to
6a67c62
Compare
Failure not germane. |
Release Notes Persisted
|
I have automatically backported this PR to "14-x-y", please check out #30159 |
This appears to still be broken in latest v14 beta and v15 alpha versions :( Works on current v13 stable though. |
Description of Change
Closes #30082.
Fixes an issue where BrowserWindows would not properly honor
transparency: true
or abackgroundColor
being set in their constructor options. This happened as a result of this CL rolled into Electron via #29751. The new methodSetPageBaseBackgroundColor
set the default content background color - i.e, the color that would appear behind the content unless the content overrode it. What then happened was that when we changed our logic to call this method, it was eventually overridden by Blink, and so would show as transparent or with the supplied color for a flash and then revert to white. We fix this by directly calling the background color method inRenderWidgetHostViewBase
.Tested with https://gist.github.com/b52f026c763057f97f745fade82758fd.
Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where BrowserWindows would not properly honor
transparency: true
or abackgroundColor
being set in their constructor options.