You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With iOS10, Apple defaulted WKWebViewallowLinksPreview property to true.
This means that in a WKWebView, force touch on a link will first open a preview, and then with more force, will open the link.
However (at least in Rhodes) this opens in Safari browser rather than in the app. At least for the case of ios_direct_local_requests = 0. (I have not tried, but guess that if 1, it would try to open and get a 404 error in Safari, since no real server.)
For almost all cases, it is probably not desirable for this to be true in Rhodes. Opening in Safari will expose the server port, and invite examination and hacking. Even if it were to open within the Rhodes app WKWebView, it will often lead to unintended consequences, because in order to get the preview, then the request is made and the server calls the controller.
There might be cases where a developer wants to take advantage of this behavior, but it would almost certainly have to be enabled on a case-by-case basis for each link, and in any case would normally need to open within the app WkWebView, not in Safari. Developer would have to be aware of the consequences of the controller method call needed to fetch the preview and take it into account to insure no unintended side-effects.
The text was updated successfully, but these errors were encountered:
With iOS10, Apple defaulted WKWebView
allowLinksPreview
property totrue
.This means that in a WKWebView, force touch on a link will first open a preview, and then with more force, will open the link.
However (at least in Rhodes) this opens in Safari browser rather than in the app. At least for the case of
ios_direct_local_requests = 0
. (I have not tried, but guess that if 1, it would try to open and get a 404 error in Safari, since no real server.)For almost all cases, it is probably not desirable for this to be
true
in Rhodes. Opening in Safari will expose the server port, and invite examination and hacking. Even if it were to open within the Rhodes app WKWebView, it will often lead to unintended consequences, because in order to get the preview, then the request is made and the server calls the controller.There might be cases where a developer wants to take advantage of this behavior, but it would almost certainly have to be enabled on a case-by-case basis for each link, and in any case would normally need to open within the app WkWebView, not in Safari. Developer would have to be aware of the consequences of the controller method call needed to fetch the preview and take it into account to insure no unintended side-effects.
The text was updated successfully, but these errors were encountered: