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: set nativeWindowOpen when sandboxed #18273
Conversation
cc @chrismohr |
0f4150d
to
c52b22e
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.
Tentative approve, but concerned with the backports (although this is a fix, it is a change in user-facing JS behavior). I'd fell more comfortable not backporting this beyond 6
@MarshallOfSound removed backport labels for 4 and 5. It can be discussed separately whether backporting this fix into older version is safe |
c52b22e
to
870ebb0
Compare
@nornagon, @zcbenz do you agree with @MarshallOfSound that backporting to 4/5 is risky, even though it's a fix? |
I'm neutral on this, backporting it doesn't seem very risky to me though. |
A maintainer has manually backported this PR to "4-2-x", please check out #18797 |
A maintainer has manually backported this PR to "5-0-x", please check out #18798 |
A maintainer has manually backported this PR to "3-1-x", please check out #18799 |
Description of Change
Fixes #17132.
Checklist
npm test
passesRelease Notes
Notes:
<webview>
:target="_blank"
not emitting'new-window'
event.window.open()
not returningnull
whenallowpopups
is not set.