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: don't warn about enableRemoteModule when it's undefined #29023
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.
Tests are failing:
2 tests failed
out of 1723
security warnings without sandbox should warn about enabled remote module with remote content
security warnings with sandbox should warn about enabled remote module with remote content
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.
@nornagon this should target master unless i'm mistaken?
@codebytere the remote module is gone in master |
Release Notes Persisted
|
/trop run backport-to 12-x-y |
The backport process for this PR has been manually initiated - sending your PR to |
I have automatically backported this PR to "12-x-y", please check out #29701 |
Description of Change
Closes #29020.
Checklist
npm test
passesRelease Notes
Notes: Fixed an incorrect warning about enableRemoteModule being issued when the option was undefined (and thus defaulting to false).