Closed rgrajivchn closed 8 months ago
Hi @rgrajivchn - The environment details you provided are a bit confusing, especially when compared to the issue you're facing on the web page. Could you please provide additional details to help us better understand the issue?
environment in flutterflow?. If you can be specific please.
Can you please respond
I’d like to bring to your attention that the WebView feature in Flutterflow has several issues. Even if we disregard our project for a moment and focus solely on creating a browser application using Flutterflow, we encounter numerous compatibility problems.
For instance, many websites, when opened in Flutterflow’s WebView, do not trigger the keyboard. Additionally, pressing the back button often leads back to the activity screen, instead of navigating to the previous webpage within Flutterflow. This is despite these websites functioning perfectly in mobile browsers like Chrome and Edge.
Now, turning our attention back to our project, we encounter another issue with WebView. I experimented with a simple Bing search page and found that every time I clicked on the search area, the page reloaded and failed to open the keyboard in the mobile web version.
Similarly, with another website, I noticed that tapping the back button in the web version did not navigate to the previous webpage. Instead, after tapping the back button 2-3 times, it navigated to the Activity page from the WebView. In contrast, in the app, tapping back for the first time navigates back to the Activity Page, rather than navigating back within the WebView page.
These issues highlight the need for improvements in Flutterflow’s WebView functionality.
PFA Reference Video: https://drive.google.com/file/d/1AuaqX6DUMn3mD6ecWTIKEDpzHep-C6OH/view?usp=drivesdk
I’d like to bring to your attention that the WebView feature in Flutterflow has several issues. Even if we disregard our project for a moment and focus solely on creating a browser application using Flutterflow, we encounter numerous compatibility problems.
For instance, many websites, when opened in Flutterflow’s WebView, do not trigger the keyboard. Additionally, pressing the back button often leads back to the activity screen, instead of navigating to the previous webpage within Flutterflow. This is despite these websites functioning perfectly in mobile browsers like Chrome and Edge.
Now, turning our attention back to our project, we encounter another issue with WebView. I experimented with a simple Bing search page and found that every time I clicked on the search area, the page reloaded and failed to open the keyboard in the mobile web version.
Similarly, with another website, I noticed that tapping the back button in the web version did not navigate to the previous webpage. Instead, after tapping the back button 2-3 times, it navigated to the Activity page from the WebView. In contrast, in the app, tapping back for the first time navigates back to the Activity Page, rather than navigating back within the WebView page.
These issues highlight the need for improvements in Flutterflow’s WebView functionality.
PFA Reference Video: https://drive.google.com/file/d/1AuaqX6DUMn3mD6ecWTIKEDpzHep-C6OH/view?usp=drivesdk
OK, looks like webview has lot of limitations
Hi @crossxsecure, @rgrajivchn. We are using Flutter's built in webview on the web, which could have some issues, especially on iOS/iPadOS web. The current version is a bit outdated, which we will definitely update soon.
In the meantime, I just want to point out that it is not the best practice to place a webview inside of a Flutter web app, especially on mobile. Does launching the web page on a new tab work for your use case?
Hi @wenkaifan0720, that's correct upon validating it appears that newer versions of the webview plugins are available compared to what’s currently in the FF pubsec.yaml file especially for webview_flutter_android. I realize that using the standard version may have its drawbacks. Therefore, could you kindly update the relevant webview plugins? This will allow us to retest the functionalities we’re interested in.
Thanks for all the updates
Hi @wenkaifan0720, could you please include the updated versions in the upcoming FF release?
Hi @wenkaifan0720 @kevintonb @FlutterFlowEng, this ticket is aging since last month and it is just about updating the WebView respective plugins to the most recent stable versions. Hence, could you please address the same?
Hi @crossxsecure. Unfortunately updating the webview package requires updating other packages as a whole, so I can't do it right away. We do have regular package updates every few months. I'll speed up the process but it could take a while.
The webviewx_plus package will be updated in our next release!
Thanks @wenkaifan0720 for providing an update, I believe it would also include the similar WebView plugins update as well?
Yes.
Hey @wenkaifan0720 has WebView been updated? I'm facing similar issues with it.
Has your issue been reported?
Current Behavior
Web view URL getting cached and not showing the latest page - Please see page - Events in App - GospelinChennai - https://app.flutterflow.io/project/gospelin-chennai-7xv73z.
There is no setting done for any caching. And see the behaviour working fine on iPhone, Android Phone. BUT, on iPad, even after 3 days, it is still showing the earlier version of the webpage. Even after killing the app several times, it still shows the older version of web page.
Expected Behavior
The latest version of the webpage should be shown, when the page is launched in the app
Steps to Reproduce
Launch App - GospelinChennai, Go to Events - page
Reproducible from Blank
Bug Report Code (Required)
IT4CkcmBx4h2ofVA1pSJc8JFmiUXHEw/RYEZ1utDQgIcJ5PMC+wIZ/f7XFRuTde0TwlEM02J/X8K0P/emvL2Gu0oGEydbtlCycxQVgvLUk+RWpClDqmSOG5/DcBUFWqz4bW3uyNQB/pvSXwb1zqAJtm/bDfsGL7NNm0CDc6lNZCK2SrDX1iXc2URm05KZDPz
Context
Create a new page - web view and use URL - https://www.gospelinchennai.info/mv/
Visual documentation
Create a new page - web view and use URL - https://www.gospelinchennai.info/mv/
Additional Info
No response
Environment