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: undefined details.requestingUrl from session.setPermissionCheckHandler #35281
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.
I think the WebFrameMain::ExecuteJavaScript
change should be a separate PR
06f1491
to
a8f0c4a
Compare
a8f0c4a
to
b63dc8e
Compare
Release Notes Persisted
|
I have automatically backported this PR to "19-x-y", please check out #35407 |
I have automatically backported this PR to "20-x-y", please check out #35408 |
I have automatically backported this PR to "21-x-y", please check out #35409 |
…andler (electron#35281) fix: undefined details.requestingUrl from setPermissionCheckHandler
Description of Change
With 7e59d78, https://chromium-review.googlesource.com/c/chromium/src/+/3495142 deprecates
GetPermissionStatusForFrame
in favor ofGetPermissionStatusForCurrentDocument
and the latter always called intoGetPermissionStatus
which does not have a frame context leading to emptyRenderFrameHost
causing the above issue.Depends on #35292
Checklist
npm test
passesRelease Notes
Notes: fix undefined details.requestingUrl from session.setPermissionCheckHandler