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: send NSView* as the response to getNativeWindowHandle() instead of a null handle #15521
Conversation
Can you add a TODO to restore the old implementation once https://chromium-review.googlesource.com/c/chromium/src/+/1253094/ lands
and respective view can be extracted with |
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.
Current implementation looks good, naming could beGetNativeWindowHandlePointer
=> GetHandle
?
@deepak1556 Initially had it as |
fe2a6b0
to
8bdea21
Compare
If you changed Also can you fix the lint failures ? Thanks! |
@deepak1556 Linting is fixed, let's get this one through 😄 |
8bdea21
to
c6608f9
Compare
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.
The implementation will be changed again in C71, so I am good with current naming convention.
Release Notes Persisted
|
I was unable to backport this PR to "3-0-x" cleanly; |
I have automatically backported this PR to "4-0-x", please check out #15644 |
Any chance of this being backported to 3.X? 🙏 |
Fixes #15489
Notes: Fixed issue where
getNativeWindowHandle()
would return an empty buffer on macOSOriginally caused by 4068a62 which was caused by https://chromium-review.googlesource.com/c/chromium/src/+/792295
This re-implements the API on macOS without using
gfx::AcceleratedWidget
cc @deepak1556