-
Notifications
You must be signed in to change notification settings - Fork 85
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
Webview fixes #73
Webview fixes #73
Conversation
UINavigationController does not correctly locate the webview's ScrollView if the WebView is not the ViewController's lowest view
If a view `allowsPullToRefresh` in a turbo-ios native app with `viewport-fit=cover`, | ||
the UIRefreshControl will not be positioned as expected. | ||
|
||
You can fix this by conditionally removing `viewport-fit=cover` when loading in a native app. |
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.
Do you have a screenshot for this issue?
We set the viewport to width=device-width,initial-scale=1,maximum-scale=1,viewport-fit=cover
and haven't noticed this issue.
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.
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.
Ahh you're right ours does that too, now I look at it. I was always like 🤷 that's high up but whatever.
This fixed my issue with content showing in the nav bar and status bar. 👍 |
This fixed the same translucency issue around nav, status and tab bars but broke the pull down to dismiss modal interaction because the refresh control took over. Ended up creating a fork and creating a branch with just the change to insert the webview fixing the translucency issue. |
Nice, thanks for that!
Good call. @jayohms, is there any history as to why this wasn't done to begin with? We aren't introducing any weird edge cases?
Confirmed that this fixes a lot of issues I've seen folks mention. In the second screenshot I'm pulling down to refresh and the spinner is in the correct position.
|
How are you people handling the |
This has been fixed in #123. |
PathConfigurationDelegate
being aclass
by making itAnyObject
UINavigationController
locates its scrollview and correctly handles scrolling related behavior (ex: navigation bar translucency).refreshControl
property of the web view's scroll viewviewport-fit=cover
affecting the position of the UIRefreshControl