-
Notifications
You must be signed in to change notification settings - Fork 50
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
Brakes scroll of parent, only ios #155
Comments
@AttilaBarany The issue is related to nested scrolling and is not a problem with this library. You can refer to this reply and try to implement |
@KevinnZou Thanks for the fast reply. The problem is just the opposite. Yes, nestedscroll did have problems in compose with Androidview, where parent steels the scroll event, we can read a lot about it on stackoverflow too. But here, the child (webview) steels all the events from the parent on ios. I tried to add ondrag, customnestedscroll etc... to the webview directly, and does not trigger anything on ios. I could not get a single println of them. The event stucks somewhere inside the lib. So actually this looks a library problem on ios platform. This is a big limitation that on iOS you can not use it, just with full screen, where no other components needed to display. |
@AttilaBarany Thanks for your information! I do not have time to check it deeply currently. But I think |
@KevinnZou Thanks, but I was digging deeper, and found out, the problem happens with every UIKitView (I beleive you use that one too for ios wkwebview), even with just a single UIView(). So I filed a ticket at compose multiplatform. It is such a basic functionality, and I think the whole UIKitView thing worth nothing without having them in scrollable views. Btw Flutter was suffering from the same thing before, I dont know if still do. |
Hello Senior Developer, I found this project because I need WebView and Adjust, and I read through various issues here. I noticed that you are using WebView and Adjust on iOS. I have been having configuration issues with this part myself. This is my project: https://github.com/cybernhl/webapp Could you please guide me on how to configure it? Thank you. |
There is no multiplatform solution for this yet. It is waiting for compose multiplatform to handle UIKitviews properly in scrollables. This issue is flagged to be "waiting external solution". Only workaround is to build your screen or page entirely in SwiftUI/UIKit, and make an if in compose. If the platform is iOS then load the whole page in UIKitView, so you can have native iOS scrollview embedding WKWebview. |
Hi. Any chance to fix this issue? Some webviews needed to be displayed in a regular scrollable column in my project. Or do I miss maybe a setting which can fix this issue?
On Android I can scroll down the column easily even if I drag the webview, but not on iOS. It scrolls only if I drag outside the webview. Which is not possible eg if the webview is higher than the screen height. Then every other content of the column after the webview will be unreachable:(. I also tried overflow hidden on the webpage, did not help. Also set webViewState.webSettings.iOSWebSettings.scrollEnabled = false for a try, but it just changed the scrollablity of the html content inside the webview. In normal case in swiftui and wkwebview works together smoothly.
To reproduce:
![Screenshot 2024-05-15 at 12 21 31](https://private-user-images.githubusercontent.com/40792011/330764020-2d95b84e-e181-4e16-b1d4-34406ff13e51.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ1OTU0ODgsIm5iZiI6MTcyNDU5NTE4OCwicGF0aCI6Ii80MDc5MjAxMS8zMzA3NjQwMjAtMmQ5NWI4NGUtZTE4MS00ZTE2LWIxZDQtMzQ0MDZmZjEzZTUxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI1VDE0MTMwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJhMWIxNjI2ODBjOGI1Y2U0ZjQzNzE3ZTI0ZTQ0MjVmOWI0ZmYwNDk2ODA4MWNmODczMWIwZjVlZDk0MDM1ZmImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Tcxx8S83y2lioSDQO-kxWVFgtDcyIIQSpMt7cz-V2BA)
The text was updated successfully, but these errors were encountered: