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: Inspector method overrides when contextIsolation enabled #29841
Conversation
cbb0552
to
6c2fd7d
Compare
6c2fd7d
to
110d033
Compare
110d033
to
e84b922
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.
would also be good to check if we can remove the conditional in window.onload
as well, to reduce the number of codepaths.
Failure not germane - merging. |
Release Notes Persisted
|
I have automatically backported this PR to "13-x-y", please check out #29885 |
I have automatically backported this PR to "14-x-y", please check out #29886 |
Description of Change
Closes #29543.
Introduced with the default change from
contextIsolation: false
tocontextIsolation: true
. WhencontextIsolation
is enabled,window.InspectorFrontendHost
,window.Persistence
, andwindow.UI
are all undefined in the isolated world. We therefore need to set them with thecontextBridge
so that we can override them correctly.Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where dropdown menus did not work in DevTools when
contextIsolation
was enabled.