-
Notifications
You must be signed in to change notification settings - Fork 16.9k
feat: add BrowserWindow.isOccluded()
#38982
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
Conversation
9745609 to
75bbfb1
Compare
75bbfb1 to
b7a56ee
Compare
BrowserWindow.isVisible() with occlusion on macOSBrowserWindow.isOccluded()
b7a56ee to
5a29680
Compare
5a29680 to
759f1e8
Compare
jkleinsc
left a comment
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.
API LGTM
|
Release Notes Persisted
|
|
I was unable to backport this PR to "26-x-y" cleanly; |
|
I was unable to backport this PR to "25-x-y" cleanly; |
|
I was unable to backport this PR to "27-x-y" cleanly; |
|
I was unable to backport this PR to "28-x-y" cleanly; |
|
I have automatically backported this PR to "29-x-y", please check out #41249 |
Description of Change
Closes #38955.
We've historically not been consistent in our implementations of
BrowserWindow.isVisible()and similar methods how occlusion affects return values. I believe instead it might be more effective to add in a separate method for apps to check occlusion status.This also removes the occlusion check from the macOS implementation of
BrowserWindow.isVisible(), which was broken and not being properly accounted for.Checklist
npm testpassesRelease Notes
Notes: Added a new method
BrowserWindow.isOccluded()to allow apps to check occlusion status.