Skip to content
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

When displayed on the screen using WebView, it is cut off at WebView #124

Closed
asa08 opened this issue Oct 10, 2021 · 7 comments
Closed

When displayed on the screen using WebView, it is cut off at WebView #124

asa08 opened this issue Oct 10, 2021 · 7 comments

Comments

@asa08
Copy link

asa08 commented Oct 10, 2021

Describe the bug
When displayed on the screen using WebView, it is cut off at WebView.
Only the part that overlaps the AppBar is displayed.

To Reproduce
Steps to reproduce the behavior:

  1. displayed toast on the screen using WebView

Screenshots

  • Using WebView

  • Toast that should be displayed

Version (please complete the following information):

  • Flutter Version: 1.22.6
  • OS: iOS
  • BotToast Version : 3.0.5
@MMMzq
Copy link
Owner

MMMzq commented Oct 11, 2021

Can you provide a minimal demo to reproduce this problem?

@asa08
Copy link
Author

asa08 commented Oct 11, 2021

ok, Create and send samples in a few days.

@asa08
Copy link
Author

asa08 commented Oct 11, 2021

@MMMzq Hello. I created a Demo. Please check it.
https://github.com/asa08/bot_toast_on_webview

Thank you.

@MMMzq
Copy link
Owner

MMMzq commented Oct 13, 2021

Hello, after investigation, this seems to be a problem caused by flutter_webview_plugin.
I haven't thought of any way to solve this problem at the moment.

@asa08
Copy link
Author

asa08 commented Oct 13, 2021

Did you confirm that there is no problem when using other packages?
I try to it.

@asa08
Copy link
Author

asa08 commented Oct 13, 2021

Changing the packages to webview_flutter solved the problem!!
Thank you.

@no-response
Copy link

no-response bot commented Oct 21, 2021

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!

@no-response no-response bot closed this as completed Oct 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants