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
opens in browser when originWhitelist contains a path #1133
Comments
|
I got the same problem too. It opens the browser to this link https://staticxx.facebook.com/connect/xd_arbiter.php?version=45# |
|
I have the same problem. The behavior I want to achieve is only allowing to render a specific page. Redirecting to any other page on the same domain should open it in the browser. I know that the documentation about originWhitelist states that: The strings allow wildcards and get matched against just the origin (not the full URL). But is there an actual reason why full urls cannot be whitelisted? |
|
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically |
|
I can confirm this is reproducible in version 11.13.0 But I need it to parse special intent links... |
|
I would like the ability to only load a specific matched path on the whitelisted origin into the WebView, but have links that are tapped in the loaded document (which do match the whitelisted origin but not the whitelisted path), be opened in the browser. |
Bug description:
If you specify
originWhitelist={['https://domain.com/']}, the link opens in the browser instead of inside the app.If you remove the trailing '/', it works fine.
(My use case is to specify an originWhitelist equal to source.uri so users can't navigate outside the domain of the link.)
To Reproduce:
on iOS (not tested on android)
Expected behavior:
The link should open in the app (as a webview) instead of opening the navigator and the domain user should be unable to navigate outside the domain.
Screenshots/Videos:
N/A
Environment:
The text was updated successfully, but these errors were encountered: