-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[BREAKING] (all platforms): remove "window.open" overwrite #600
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.
This looks like a major, breaking change. I just added [MAJOR]
prefix to the title to make this extra clear. I also added this PR to the 4.0.0 milestone, for the next major release of this plugin.
I would definitely favor this kind of an update, unfortunately not confident enough with this plugin to formally approve this proposal.
Yes this is a breaking change intended for the next major release. I raised #599 to discuss this and make a decision when time has come for a major release. If this is released we could check and possibly close the issues around |
Thanks. I think I cannot stress enough how important it is to make it absolutely clear if a PR contains a breaking change. While we should expect current InAppBrowser maintainers to pick this up, we have seen maintainers come and go due to external factors. (I can only imagine if another maintainer would just do LGTM, merge and release without realizing that this is a breaking change ... kaboom!) It was certainly not clear to me from first glance in this PR and #599 that you wanted to discuss the next major release in #599. That said, I just sent a proposal to the mailing list to do a version bump and get this PR reviewed & potentially merged. Thanks for your quick work on this. |
I agree with @NiklasMerz, this change will fix many issues related to window.open overwrite side effects. I'm looking forward to seeing this PR merged in order to remove the hack I have in my application. Thanks. |
Maintainers are a bit overloaded. I would highly recommend that you follow up with us on the mailing list or on Slack, please follow the links in the footer of cordova.io or cordova.apache.org. |
Next major version is work in progress right now. We can merge this once we get some review for this. We should not forget to mention this in the changelog and release blog post, since this is a breaking change. I changed the title to make that the visible in the commit message. |
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.
LGTM. I always felt that a core plugin shouldn’t overwrite a function such as window.open
.
@erisu Does this cover electron, too? Does electron use browser? |
What's the status on this, Niklas? Could you solve the electron question? Given the fact that the master already contains breaking changes, we could merge this. |
I think it's good to merge. As far as I can remember this should not affect electron since it has not implementation for IAB. |
It is OK in regards to Electron. |
Closes #599
Platforms affected
All
Motivation and Context
See #599
Testing
Tested shortly with https://github.com/dpa99c/cordova-plugin-inappbrowser-test
Checklist
(platform)
if this change only applies to one platform (e.g.(android)
)