Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Link: Allow explicit rel="opener" #1428
necolas left a comment
It's not done "blindly", and if you have use cases you should explain them.
OK, sorry. What I meant by "blindly" was without letting the user opt-out. I might have used a poor word choice.
A simple use case would be opening a tab on the same domain that we would need to communicate back to the original tab.
Another case might be an oAuth flow where you open a tab to ask the user to go login using Google/GH/etc then that tab lands back on a same-origin page that sends a postMessage to
I think noopener is a super wise default but we should probably be able to opt out because this essentially introduced a breaking change when I upgraded RNW and one that seems not to be able to be worked around.