-
Notifications
You must be signed in to change notification settings - Fork 16.2k
fix: will-attach-webview
handler modifying params.instanceId
does not break <webview>
#32386
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
Conversation
a5040cc
to
150ca6b
Compare
b783197
to
201d30a
Compare
201d30a
to
07fa484
Compare
Release Notes Persisted
|
I was unable to backport this PR to "14-x-y" cleanly; |
I was unable to backport this PR to "15-x-y" cleanly; |
I have automatically backported this PR to "16-x-y", please check out #32429 |
I have automatically backported this PR to "17-x-y", please check out #32430 |
Description of Change
Don't break when internal undocumented
params.instanceId
is modified by application code.Keep passing it to
will-attach-webview
in case an app reads the value.Also remove unused
userAgentOverride
param.Checklist
npm test
passesRelease Notes
Notes: The
<webview>
implementation was made more robust, it no longer breaks whenwill-attach-webview
handler modifies the internalparams.instanceId
.