You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
e.sender object received from an extension background page should have webPreferences and session initialized. It looks like options in api::WebContents constructor don't get initialized properly for an extension background page.
Actual Behavior
e.sender object doesn't have session and e.sender.getWebPreferences() returns null.
Preflight Checklist
Ref #19447
Issue Details
Expected Behavior
e.sender
object received from an extension background page should havewebPreferences
andsession
initialized. It looks likeoptions
inapi::WebContents
constructor don't get initialized properly for an extension background page.Actual Behavior
e.sender
object doesn't havesession
ande.sender.getWebPreferences()
returnsnull
.To Reproduce
https://github.com/sentialx/electron-quick-start/tree/extensions/no-session
Just run it and you will see something like this:
Additional Information
This is a real blocker for anyone who would want to provide own
chrome
APIs in background pages initialized from different sessions.The text was updated successfully, but these errors were encountered: